Glovo
by Glovo
Search products across local stores on Glovo's delivery marketplace from an AI agent. Two tools, both discovery — Glovo states plainly that placing orders, payments, account access and order tracking are not supported. No sign-in to search.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Glovo via MCP
https://api.glovoapp.com/discovery-mcp/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Glovo Tools & Capabilities (2)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Glovo publishes no tool list for this server. The two names come from Anthropic's directory. We could not diff them against a vendor enumeration because none exists — the documentation describes capabilities in prose only. Diffed the other direction, every capability Glovo's prose describes maps onto one of the two names, so nothing in the docs is missing from the listing.
- We could not read tool schemas or safety annotations. The endpoint returned 403 to an anonymous request, so no parameter-level detail is published here, and the read-only classification is ours rather than the server's declaration.
- The auth posture is undetermined, not confirmed open. Anthropic's directory records the endpoint as authless and Glovo's docs say no authentication is needed to search, but our own probe never got far enough to observe the posture. Both are evidence *about* the auth mode; neither is our observation of it, so
authVerifiedstays false. - No RFC 9728 descriptor exists. All four probed well-known paths returned the same origin 404 body on 2026-08-22, so there is no
scopes_supporteddocument and no OAuth authorization server to name. Nothing narrows what the connector may do, because nothing is granted in the first place. - Coverage is Glovo's footprint, not global. Glovo's own troubleshooting assumes a user may be outside a served city. Ask outside one and the connector has nothing to return.
- The hand-off is the real boundary, and it is one click wide. Everything the connector does is safe by construction; everything after the link it hands you is an ordinary Glovo purchase. The connector's read-only nature does not make the destination read-only.
- The docs live under a
/legal/path but are not terms of service. The URL Anthropic publishes sits atglovoapp.com/docs/en/legal/mcp/, alongside Glovo's terms and privacy documents, yet the page itself is ordinary technical documentation with setup steps and troubleshooting. Glovo's actual consumer terms are a separate 17,000-word document that never mentions the connector, MCP or AI agents, so no term there governs this integration specifically. - Rate limits are not documented. Glovo publishes no rate limit, quota or fair-use figure for the connector anywhere we could find.
Frequently asked questions
No. Glovo's connector documentation carries a table of what the connector does not support, and the first row is placing orders, with the note that ordering happens on the Glovo app and not inside Claude. Separate rows rule out payments and account access. When you decide, the connector hands you off to Glovo's own app or website.
Anthropic's directory lists two, search_products and render_products_carousel. Glovo's documentation describes the connector's abilities in prose and never prints a machine tool name, so there is no vendor enumeration to check the two against. The endpoint returned 403 to our anonymous request, so we could not read the live list either.
Not to search. Glovo's documentation states no authentication is required to search for products, and that your Glovo account is neither required nor accessible. It adds that Glovo may ask you to sign in on the Glovo app if you open a product there to place an order. Anthropic's directory also records this endpoint as authless.
In this case the narrowed name matches the documented surface. The endpoint path says discovery, both tool names are discovery verbs, and Glovo publishes an explicit non-support table covering orders, payments, account access and tracking. A scoped-down name is normally just a claim, but here the vendor wrote the boundary down rather than implying it.
It draws results, it does not act on them. Anthropic's directory records this connector as shipping an MCP app, which is an interactive widget rendered inside the conversation, and the tool name matches that pattern. Glovo's docs describe comparing options side by side, which is what a carousel of products is for. We could not read its schema.
No. Glovo's documentation lists order tracking in its unsupported table, stating that managing or tracking existing orders is not supported. Since the connector also has no access to your Glovo account, it has no way to see your order history. Track deliveries in the Glovo app, which is where the order was created in the first place.
Because an edge layer blocks unrecognised clients, not because it demands a token. A nonsense sibling path under the same prefix returned a clean origin 404 on 2026-08-22 while the real path returned a nine-byte Forbidden from CloudFront, with no www-authenticate header. The route exists and is gated at the edge rather than by authentication.
Wherever Glovo itself operates, which is its marketplace footprint across Europe, Central Asia and Africa. Glovo's troubleshooting section tells anyone seeing no nearby results to confirm Glovo operates in their city and that a valid delivery address was shared. Its support contact and privacy policy are both Spanish-language endpoints, reflecting a Barcelona base.
Sources
- Glovo connector for Claude documentation (retrieved 2026-08-22). This is the URL Anthropic's directory nominates, and it carries the capability list, setup steps, troubleshooting and the unsupported-capability table. · retrieved 2026-08-22
- Glovo Terms and Conditions (retrieved 2026-08-22). Checked for AI or agent clauses; contains none. Its courier-as-agent ordering model is described there. · retrieved 2026-08-22
- Glovo
robots.txt(retrieved 2026-08-22). Allows the docs path; disallows only embedded web views, order-tracking share links and password recovery. NoContent-Signalline is present. · retrieved 2026-08-22 - Live endpoint probe, anonymous initialize against
https://api.glovoapp.com/discovery-mcp/mcp, with a nonsense-sibling control athttps://api.glovoapp.com/discovery-mcp/nonsense-zzz(2026-08-22) · retrieved 2026-08-22 - RFC 9728 probes at
https://api.glovoapp.com/.well-known/oauth-protected-resource/discovery-mcp/mcp,https://api.glovoapp.com/discovery-mcp/.well-known/oauth-protected-resource,https://api.glovoapp.com/.well-known/oauth-protected-resourceandhttps://api.glovoapp.com/.well-known/oauth-authorization-server— all four returned an identical 404 body (2026-08-22) · retrieved 2026-08-22 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Glovo support — <mailto:customer.es@glovoapp.com> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Glovo
- Tools
- 2
- Domain
- api.glovoapp.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.