Claude Uber Eats connectorSearch delivery restaurants from Claude, minus the checkout.
The Claude Uber Eats connector exposes 2 tools. 1 reads the restaurant catalog, 1 sends audience-measurement data, and 0 lack a description. Here is how the search works, what is missing to place an order, and who controls access.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when you're hungry
Tell Claude what you feel like eating and it asks for your delivery address, then queries Uber Eats and comes back with the places that deliver to you. You can search by restaurant name, by cuisine or by a specific dish, and the results land right in the chat.
Cut the list down by rating. The search tool takes one threshold out of three: 3.5, 4 or 4.5 stars and up; Uber rejects any other value.
Stay inside a price band. The same tool takes an optional price-range filter, so the list stays within the band you name in your request.
Keep only the quick ones. One switch limits results to places that can deliver in 30 minutes or less. It is off by default.
Let Claude ask the right question. Uber tells Claude to get your delivery address explicitly before searching, so the results match the place where the food will actually arrive.
Where the connector ends: no source describes a tool that fills a cart, pays or tracks a courier. Claude helps you pick; it does not place the order. Nothing runs in the background either, so no alert when a favorite spot runs a deal. Watching for that is a job for an automation tool, a different trade; Integrations covers that side.
Words worth knowing first
Five terms, explained once.
- Connector
- A bridge you install once between Claude and an outside service, which Claude then uses while it writes its answers.
- Tool
- A specific capability, identified by name, that the connector makes available. Claude decides on its own when to use it.
- Authorization
- The service's own access page, where you grant Claude the right to act. Given once, and you can withdraw it later.
- Approval
- The green light Claude asks for in the chat before it runs an operation that would modify an account.
- MCP
- The common standard all connectors are built on: it is how an assistant like Claude exchanges with third-party services.
Turn on the Claude Uber Eats connector in three steps
- 01
Open the connector list
Head to Claude's settings, pick Customize then Connectors, and search for Uber Eats. In a Team or Enterprise organization, an Owner or Primary Owner needs to have enabled it before you can.
- 02
Connect from its row
Hit Connect next to Uber Eats and let the service's window walk you through it. If the link stops working, Disconnect followed by a fresh connection puts things right.
- 03
Check the service's screen
If Uber Eats shows an authorization screen, read all of it before you accept. The service, not Claude, defines the scope of the access you grant, and you can take it back later from your account.
Both connector tools, in detail
Uber Eats gives Claude 2 tools: 1 that read your account, 1 that change something in it.
A search that Uber describes, and a technical tool Uber keeps for its own card. Names stay in English, as Claude shows them.
- 1 read
- 1 write
What Claude reads (1)
1 toolsearch
Queries Uber Eats for a restaurant, a cuisine or a dish and returns the places that deliver within your radius. Results can be narrowed to a price band or a minimum rating.
What goes out to Uber (1)
1 toolOne tool that passes data to Uber, reserved for the interactive card according to the publisher.
publish_analytics
Approval: see the ruleUber describes it as reserved for its interactive card's telemetry. Its description says Claude must not call it under any circumstances.
Before it acts, what Claude asks you
The default principle: before any action it carries out on an account for you, Claude pauses and waits for your consent, right inside the conversation.
On Uber Eats, the tool that sends data is the card's telemetry, which Uber forbids Claude to call. No source assigns it a specific confirmation, so the general rule covers it. In a Team or Enterprise organization, owners set whether a member can skip confirmation for some actions, and they can limit what the connector does for everyone. Nobody unlocks that choice from a personal account, whatever their role in the team.
Availability by plan
Of the 819 connectors in the official directory, not one lists its availability plan by plan. That information does not exist anywhere, connector by connector.
Only the shared rule is published. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions go through Claude Desktop. In a Team or Enterprise organization, an Owner or Primary Owner enables the connector first. Uber Eats' current status is on its sheet in the official directory.
Limits worth knowing
Claude only uses these tools while it answers you; none of them fires on its own. And only Uber documents this connector, through the tool list its own server publishes.
The sheet exposes a search and a telemetry tool, nothing to build a cart, pay or follow a driver, at least in what public sources show. That is an observed floor, since an admin can open actions missing from the sheets. The directory badge is not a security audit, and Anthropic notes on every sheet that it neither picks a publisher's tools nor guarantees how they behave. To chain actions without you, the automation side lives under Integrations.
Need help connecting Uber Eats to Claude?
A person reads every message.
