Uber Eats
by Uber Eats
Search restaurants and menus on Uber Eats from an AI agent. Two tools — one search, one telemetry publisher. Uber states you can only view restaurants and menus; checkout happens in the Uber Eats app. 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 Uber Eats via MCP
https://mcp.ubereats.com/eats-claude/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Uber Eats 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
- The nominated documentation URL is not documentation. Anthropic's directory gives
https://www.ubereats.comas this connector's docs link. That is the consumer food-ordering homepage — no MCP section, no API reference, no tool list. It also returned 403 to every text client we tried, including a browser-identified fetch, so it yielded nothing at all. The real documentation is a single help-centre article, reached through the directory'ssupportfield rather than itsdocumentationfield. - Uber publishes no tool enumeration. The two names come from Anthropic's directory. We checked
ubereats.com, itsllms.txt,llms-full.txtand.mdvariants,developer.uber.comand itsllms.txt,robots.txtandsitemap.xml, the MCP endpoint host root, and third-party aggregators.developer.uber.comreturned a plain-text 404 for every path we tried, includingrobots.txt— the host answers nothing to a non-browser client. No vendor list exists to diff against, so we cannot call the listing clean. - We could not verify the authentication posture. The endpoint returned 403 "access denied" to an anonymous
initializeon 2026-08-23, with nowww-authenticateheader. That is an edge block, not an authentication challenge, so our authVerified flag is false and the auth mode is undetermined. Anthropic's directory records the endpoint as authless; that is the directory's claim, not our observation. - We could not read tool schemas or safety annotations. No parameter-level detail is published here, including for
publish_analytics, whose arguments are the one thing on this connector we would most want to see. publish_analyticstransmits undisclosed data. Uber documents no schema, field list or retention period for it, and Uber's privacy notice does not mention AI-assistant integrations at all. Treat what leaves the conversation through it as unspecified rather than as nothing.- Advertised scopes are not enforced scopes. We read Uber's scope declaration over the wire; we did not observe the server checking a token against it. No public source describes the enforcement.
- United States only, and one country deep. Uber names no other market for the integration.
- Uber's help article is five questions long. It is genuine first-party documentation and it answers the decisive question, but it covers nothing about data sharing with Anthropic, disconnecting the connector, plan requirements, rate limits or troubleshooting. Several sections of this page say "undocumented" for that reason.
- One path on the MCP host behaves oddly. A request to
/.well-known/oauth-protected-resource/eats-claude/mcpreturned a JSON-RPC error rather than a resource descriptor or a 404, meaning that well-known path is routed into the MCP handler itself. No RFC 9728 protected-resource descriptor exists at any path we probed. The scope evidence on this page comes from the authorization-server document instead, which is a different RFC.
Frequently asked questions
No. Uber's help centre answers the question directly, stating that at this time you can only view restaurants and menus. Selecting a dish in Claude hands you to the Uber Eats app to finalize your cart and check out there. Neither listed tool carries an order, cart, checkout or payment verb, and no ordering scope appears in the server's advertised list.
Anthropic's directory lists two, search and publish_analytics. Uber publishes no machine-readable tool list anywhere we could find, so those two names have no vendor counterpart to check them against. The endpoint returned 403 to our anonymous request on 2026-08-23, so we could not read the live listing either.
It sends usage telemetry from the conversation back to Uber. The verb points outward, which is unusual: across 41,300 tool names in Anthropic's directory snapshot, 251 carry analytics in the name and all but three of them read. Only Uber's two connectors publish. Uber documents no schema for it, so what it transmits is undisclosed.
Not to search, but yes to eat. Anthropic's directory records the endpoint as authless, and searching restaurants requires no sign-in. Uber's help centre states that completing an order in the Uber app requires an Uber account, and directs anyone without one to download the app. The account gate sits at checkout, not at search.
The United States only, as of launch. Uber's help centre states the Claude integration launched on April 23rd, 2026 in the United States, and that it is available on Claude web and the Claude mobile apps for Android and iOS. Uber names no other country. Uber Eats itself operates far more widely than the connector currently does.
Two, and neither can place an order. The server's authorization metadata advertised fourteen scopes on 2026-08-23, twelve of them identity claims, plus eats.3p.mcp and eats.partner.mcp. Uber's wider identity platform publishes 508 scopes including several for ordering and payment methods, and the MCP server's own list excludes every one of them.
Because Uber's edge gateway blocks unrecognised clients, not because it demands a token. The host returns a plain 404 page-not-found for paths that do not exist and a thirteen-byte access denied for the real one, with no www-authenticate header on either. The route exists and is gated at the edge, so we could not observe the authentication posture.
Anthropic's directory labels it Read + Write, and it is one of only two authless servers in the whole snapshot carrying that label. The write is almost certainly publish_analytics sending telemetry rather than anything touching your account. Nothing in the surface writes an order, a cart or a payment method, and Uber's help centre rules ordering out in prose.
Sources
- Uber Help, "Claude Integration for Eaters" (retrieved 2026-08-23). The decisive source, reached via the directory's support field.
help.uber.com/robots.txtcarries an emptyDisallow:and noContent-Signal, so fetching and synthesis are both permitted. · retrieved 2026-08-23 - Uber Eats consumer homepage, the URL Anthropic's directory nominates as documentation (probed 2026-08-23, HTTP 403 to all clients;
llms.txt,llms-full.txtand.mdroutes all 403) · retrieved 2026-08-23 - Uber Eats MCP server authorization metadata,
scopes_supported—https://mcp.ubereats.com/.well-known/oauth-authorization-server(retrieved 2026-08-23) · retrieved 2026-08-23 - Uber identity platform OpenID configuration, the 508-scope catalogue (retrieved 2026-08-23) · retrieved 2026-08-23
- Live endpoint probe, anonymous
initializereturning 403 with no authentication challenge, and RFC 9728 four-path probe againstmcp.ubereats.com(2026-08-23) · retrieved 2026-08-23 - Uber privacy notice for riders and order recipients (retrieved 2026-08-23) · retrieved 2026-08-23
- Anthropic Connectors Directory entry, including the two tool names, the Read + Write permission label and the MCP app flag — , read from our directory snapshot dated 2026-08-16. Corpus comparisons over 41,300 non-blank tool names are computed from that same snapshot. · retrieved 2026-08-16
- Anthropic Connectors Directory entry for Uber's sibling rides connector, used for the naming comparison (same snapshot)
- Uber Eats support — · 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
- Uber Eats
- Tools
- 2
- Domain
- mcp.ubereats.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.