Claude Glovo connectorWhat Claude can look up on Glovo.
The Claude Glovo connector exposes 2 tools. 1 searches products in local stores, 0 change anything, 1 is undocumented. Below: what Claude can find for you, why your Glovo account never enters the picture, and where the order really happens.
Verified Trustpilot reviews · AI, automation & growth agency
Why plug Glovo into Claude
You need a birthday gift tonight, or a keyboard under a set budget, and you do not want to scroll through ten store pages. With this connector you describe what you want in plain words, and Claude searches products sold by stores near you on Glovo. When something fits, Claude sends you to the Glovo app or website to buy it. The shopping list starts in the chat; the purchase never does.
A precise item, found locally. You name a product and a city, and search_products looks through the local stores and supermarkets Glovo lists, so Claude can answer with what is actually on offer.
A budget that holds. Glovo says results can be narrowed by price, brand, features, ratings or favourite stores, and that the connector shows live availability, prices and store details. Claude can then line options up before you pick one.
A last-minute idea. Skincare, a video game, pet supplies, flowers: you explore a category from the conversation instead of the app's menus, then open the chosen product in Glovo.
Now the part the directory listing does not spell out. Claude does not place the order, does not pay, does not see your Glovo account and cannot follow a delivery already under way. Everything after the choice happens in Glovo. Nothing runs by itself either: no search starts unless you ask. The site has no n8n, Make or Zapier page for Glovo; the Integrations hub lists the apps that have one.
Four words to know before you start
The vocabulary you will meet once Glovo is connected to Claude.
- Connector
- The link you set up once between Claude and a service, so Claude can use it while it answers you.
- Tool
- One named job a connector gives Claude. Claude picks the ones it needs by itself, and the directory lists them by name.
- Approval
- The confirmation Claude waits for before going ahead with an action on your behalf, shown in the conversation itself.
- MCP
- The common standard behind connectors: it is what lets an assistant like Claude talk to an outside service.
Connect Glovo to Claude in three steps
- 01
Find Glovo in the connector list
Open Claude's settings, go to Customize, then Connectors, and look for Glovo. On a Team or Enterprise workspace, an Owner or Primary Owner must enable it before members can connect.
- 02
Start the connection
Click Connect on Glovo's row and follow the steps Claude shows. Glovo says no authentication is needed to search products, so you are not signing in to a Glovo account at this point.
- 03
Read the screen, then ask
If an authorization screen appears, read it before you accept: it belongs to the service, not to Claude. Then start a new chat and ask for something you want delivered. To stop, use Disconnect from the same menu.
The 2 Glovo tools, and what is known about each
Glovo gives Claude 2 tools: 1 that read your account, 0 that change something in it, and 1 no official source describes.
One tool is described by Glovo, the other appears only by name in the directory. Tool names stay in English, exactly as Claude shows them.
- 1 read
- 1 not documented
What Claude looks up (1)
1 toolOne tool that searches the Glovo catalogue without touching any account.
search_products
Looks for a product across the local stores and supermarkets listed on Glovo, from a description in your own words. Claude comes back with options you can actually order nearby.
Undocumented (1)
1 toolThe directory lists this name and nothing else. No official text says what it does, and this page will not guess from the name.
render_products_carousel
This name sits in the directory's tool list, and that is all anyone outside Glovo knows about it. Glovo's connector page never mentions it and no Claude page covers it, so nothing more is said here.
What Claude asks before it acts
By default, Claude stops and asks you before each action it carries out on a service in your place. The request appears in the conversation.
With Glovo, the listing shows no tool that changes anything: one search, one undocumented name. The order itself always happens in the Glovo app or website, where Glovo may ask you to sign in. On Team and Enterprise, workspace owners decide whether members can let some actions through without being asked, and they can restrict what a connector may do for the whole organization. Claude also works only with the access of the person who connected it.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. That answer, connector by connector, is not published anywhere.
The general rule is public: remote connectors are open to every user on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization first. For the current status, open the Glovo sheet in the official directory from your own account.
Where the Glovo connector stops
A connector is not an automation. Claude runs these tools while it answers you; nothing starts by itself when a price drops or a store opens.
Everything known here comes from Glovo itself: neither Claude's help center nor Anthropic's developer docs have a page on this connector. By default the listing exposes only a search; that is an observed floor, not a promise about what a publisher may add. The directory badge is not a security audit, and Anthropic writes on every sheet that it does not control which tools a publisher exposes, nor that they behave as announced.
Need help connecting Glovo to Claude?
A person reads every message.
