Uber

Get real-time Uber fare and ETA estimates between two US locations.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Uber connector does

The Uber MCP server gives Claude, ChatGPT and any MCP-compatible agent real-time Uber fare and arrival estimates between two United States locations. Anthropic's directory lists two tools. Nothing in this connector requests a ride — Uber routes booking to its own app, so the agent compares options and the rider confirms the trip.

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.

Uber tools (2)

  • get_estimates_between_two_locations_claude
  • publish_analytics_events

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The no-booking finding is inferred, not declared. This is the distinction that governs how much weight it carries. Uber publishes no exclusion statement — no page saying the connector cannot request a ride, cannot pay, cannot cancel. What exists is a marketing sentence about handing off to the app, a two-name tool listing, and a scope that is not the one gating Uber's booking API. Those converge, and they are not the same as a vendor drawing the line itself.
  • Uber publishes no tool list for this server. The two names come from Anthropic's directory. Both are absent from every Uber page and from every secondary source we searched, so the Reverse-Honeycomb diff has nothing on the vendor side to run against.
  • The directory's authless posture is contradicted by the server. Anthropic's snapshot records an authless posture and an is_authless flag set true. The server publishes OAuth metadata and refused an anonymous request. Trust the server.
  • 3p.rides.mcp is undocumented. It is the only application scope on the consent screen and Uber describes it nowhere, so a user granting it cannot know what it permits.
  • publish_analytics_events has no published behaviour. We could not establish what it sends, when it fires, or whether a user can decline it separately.
  • We could not read tool schemas or safety annotations. The endpoint returned 403 to an anonymous request on 2026-08-23, with no WWW-Authenticate header and no RFC 9728 protected- resource descriptor at any of the four probed paths, so no parameter-level detail is published here.
  • Fare estimates exclude taxes, Service Fees and promotions, per Uber's own generative AI policy, which directs users to the checkout page for the accurate figure. An agent quoting the estimate as the price will be wrong by the fee stack.
  • Price comparison against competitors is called out as a terms violation in Uber's REST API documentation. We found no statement applying that to the MCP connector, and it is unresolved whether it does.
  • United States only, per Anthropic's directory description. No Uber source states an expansion plan.
  • Commercial use needs written permission. Uber's U.S. Terms of Use, last modified 2026-08-12, restrict the Services to noncommercial use absent a separate written agreement, and separately bar using content from the Services to develop software or train AI systems without prior written permission.
  • The .md suffix route is an interpolating catch-all. uber.com/legal/en.md and uber.com/legal/en/.md both return HTTP 200 with a body hash identical to the plain page. A probe that trusted the status code would report a Markdown route that does not exist.

Frequently asked questions

Can the Uber MCP connector request a ride and dispatch a driver?

No. Neither tool Anthropic lists requests a ride. The connector returns fare and ETA estimates, and Uber's own connector listing states that all ride requests are handed off to the official Uber app to be completed securely. Nothing in this surface dispatches a driver or charges a card, so no agent action here is irreversible.

How does booking actually work if the connector cannot book?

Through a deep link the user taps. Uber documents deep links as URLs that launch the Uber app with pickup, dropoff and product pre-filled, and its developer docs describe them as starting the ride request flow rather than completing it. The rider still confirms the trip inside Uber, where the fare and payment method are shown.

What does the second Uber MCP tool, publish_analytics_events, do?

Uber does not say. It is the only write-shaped name in the listing, and no Uber documentation anywhere describes it. Its name implies the connector reports interaction telemetry back to Uber. Uber's rider privacy notice lists usage data including app features or pages viewed and Uber search history, so treat estimate queries as observed.

Does the Uber MCP server require signing in?

Yes, despite the directory marking it authless. Anthropic's snapshot records an authless posture, but the server publishes OAuth authorization server metadata at mcp.uber.com naming auth.uber.com and a dedicated 3p.rides.mcp scope. An anonymous request to the endpoint was refused on 2026-08-23, so treat the directory's authless flag as stale.

Does Uber publish documentation for its MCP server?

No. The documentation URL in Anthropic's directory is uber.com/legal/en, a catalogue of legal documents whose 975-word index contains no mention of MCP, Model Context Protocol, or generative AI. Uber's developer site covers its REST APIs and never names the connector. No vendor tool enumeration exists to check the directory's two names against.

Can the connector see or spend money on my Uber account?

No tool in the listing moves money. Fare estimates are read-only figures and no tool name carries a payment, wallet, tip or receipt verb. Uber's Guest Rides API does document a tip endpoint and its Riders API documents ride requests billed to a card, but neither appears in this connector and both sit behind different OAuth scopes.

Where does the Uber connector work?

The United States only. Anthropic's directory description states the connector gives fare estimates between any two locations in the United States, and names UberX, UberXL, Comfort and Black as the products it compares. No source we found extends it to other countries, and Uber publishes no coverage list for the connector.

Are Uber's fare estimates from the connector accurate enough to rely on?

Treat them as indicative, not final. Uber's generative AI policy states that pricing information provided or used to generate responses is an estimate and excludes taxes, Service Fees and promotions, and directs users to the checkout page for the most accurate information. Surge pricing can also move a fare between the estimate and the booking.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Uber to work.

Connect Uber once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.