5 minTime to key
NoNo-human path
4Human gates
4/10Onboarding score
Manual reviewPartner applicationPhone OTPTalk to sales
Fastest path to a key
- Phone OTPConsumer agent path (fastest): add Claude connector https://mcp.uber.com/claude/rides-3p/mcp (rides price/ETA estimates) and/or https://mcp.ubereats.com/eats-claude/mcp (restaurant/menu browse) -> OAuth sign-in to Ube…
- Developer path: sign in to developer.uber.com dashboard with an Uber account -> Register App -> pick product (e.g. Rides/Guest Rides) -> accept terms -> get client_id/secret.
- Admin approvalRequest privileged scope (guests.trips, business.*, eats.*) from Uber / Uber for Business rep with org name, admin email, client id, use case and endpoint list -> wait for approval -> enable scope in dashboard.
- Manual reviewclient_credentials token -> call sandbox (sandbox-api.uber.com/v1/guests/) -> production after review.
- Working API key
Biggest gap
No self-serve API for ride requests; no llms.txt/markdown docs; MCP endpoints are per-client paths rather than one open DCR server.
Worth copying
Consumer MCPs scoped to safe read actions (estimates, menus) with booking/payment handed off to the native app.
Sources (11) · checked 2026-10-11
- https://claude.com/marketplace/connectors/uber
- https://claude.com/marketplace/connectors/uber-eats
- https://mcp.uber.com/claude/rides-3p/mcp (probed: 403)
- https://mcp.ubereats.com/eats-claude/mcp (probed: 403)
- https://developer.uber.com/docs
- https://developer.uber.com/docs/guest-rides/introduction
- https://developer.uber.com/docs/guest-rides/guides/authentication
- https://developer.uber.com/docs/businesses/receipts/guides/account-setup
- https://developer.uber.com/llms.txt
- https://www.uber.com/robots.txt
- https://www.pymnts.com/news/artificial-intelligence/2026/anthropic-turns-claude-into-a-front-door-for-daily-apps/
27Readiness score / 100
L1 Agent-readableBeats 28% of 1,846 companies
Access20/20
Context3/20
Interfaces4/32
Onboarding0/19
Trust0/9
Biggest gains
- +12 Remote MCP server for the product. Host a remote MCP server (e.g. mcp.<domain>/mcp, Streamable HTTP) for your core actions.
- +8 llms.txt exists. Publish /llms.txt: a markdown index of your docs at the root or docs host.
- +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
All 20 checks
- PASSAgents get the real page, not a bot wall10
- PASSrobots.txt lets user-triggered agents in6
- PASSContent is server-rendered4
- FAILllms.txt exists8
- FAILllms-full.txt exists3
- FAILDocs available as markdown6
- PASSSitemap2
- PASSStructured metadata1
- PASSPublic developer docs4
- FAILMachine-readable API spec8
- FAILRemote MCP server for the product12
- FAILDocs MCP or searchable docs4
- FAILSDKs and a CLI4
- FAILOAuth discovery metadata5
- FAILAgents can self-register OAuth clients6
- FAILSelf-serve API keys5
- FAILFree tier or test mode3
- FAILAgent manifests4
- FAILsecurity.txt2
- FAILPublic status page3
Your fix pack: 15 changes, up to +73 points
Each change is ready to paste, filled in for uber.com, with a command to check it worked. Or hand the whole list to your coding agent.
Add the badge to your README
[](https://agentsready.dev/c/uber.com)