Claude Uber connectorWhat Claude can do with Uber, and what stays in the app.
The Claude Uber connector exposes 2 tools. 1 reads ride estimates, 0 change anything, and 1 is documented nowhere. Below: what Claude shows you, what still happens in the Uber app, which trips it turns down, and who can switch it off.
Verified Trustpilot reviews · AI, automation & growth agency
What changes before you call a ride
Ask Claude what a ride between two exact addresses would cost and it queries Uber, then drops an interactive card into the chat: the ride options on offer, a price range for each, the pickup time and a link to book. The Uber app only comes out when you are ready to order.
See every option side by side. Uber's own description says the card lines up what is available right now, from UberX and UberXL to Comfort and Black, with the key features of each. One tool does all of it: get_estimates_between_two_locations_claude.
Go straight to one product. Say you want a six-seater or a black car and the card narrows to that option. Uber's description lists this case: asking for an estimate on a specific product type.
Book without retyping anything. The links on the card open the official Uber app, which is where the trip is actually completed. Nothing gets ordered inside the conversation.
What Claude won't do: schedule a ride for later, chain several stops, or price a trip that starts or ends outside the United States. It also never sees the fares themselves, because they live in the card, not in its reply. And nothing runs on its own: no tool watches prices or pings you when they drop. That kind of background job belongs to an automation tool, which is a different line of work; Integrations gathers that side.
The vocabulary in one minute
Five words that make the rest of the page easy to follow.
- Connector
- The link you set up once between Claude and a service, so Claude can work with it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the one it needs by itself; the directory sheet lists each by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use afterwards. You can take it back the same way.
- Approval
- The confirmation Claude waits for before an action that changes an account, shown in the chat right when it matters.
- MCP
- The shared standard behind connectors: it is what lets an assistant like Claude talk to an outside service.
Connect Uber to Claude in three steps
- 01
Find Uber in the list
In Claude's settings, open Customize, then Connectors, and look for Uber. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it first before each member can hook it up.
- 02
Start the connection
Click Connect on its row and follow the window the service opens. If the link ever breaks, use Disconnect and then connect it again from that same row.
- 03
Read before you accept
If an authorization screen appears, read it before you approve. It belongs to the service, not to Claude, and it sets what the access covers. Whatever you grant there can be withdrawn later on.
The 2 tools in the Claude Uber connector
Uber gives Claude 2 tools: 1 that read your account, 0 that change something in it, and 1 no official source describes.
One documented tool, one known only by name. Tool names stay exactly as Claude displays them.
- 1 read
- 1 not documented
What Claude reads (1)
1 toolget_estimates_between_two_locations_claude
Pulls Uber's estimates between a pickup and a drop-off you have spelled out, then shows them in an interactive card with fares, arrival time and links that open the app to book.
Not documented (1)
1 toolThe directory publishes this name and nothing about its role. This page won't guess from the name.
publish_analytics_events
This name appears on the directory sheet and no official source says anything more about it. Uber's own server did not even list it on October 1, 2026.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before every action it takes on an account for you. The request shows up in the chat at the moment it applies.
On this connector, no source describes a tool that changes anything: the estimate is read-only material and ordering happens in the Uber app. On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked again. They can also cap what a connector may do across the whole organization, and nobody can override that from their own account. Turning the connector off is just as simple from Claude's settings.
Which plans it is available on
None of the 819 sheets in the official directory shows plan availability. That answer, connector by connector, is not published anywhere.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organization before members can connect. For the current state, check the connector's sheet in the official directory.
Where this connector stops
A connector is not an automation: Claude calls the tool while it answers you, and nothing fires on its own. Everything below comes from Uber, the only party documenting this connector.
Uber keeps the tool to immediate rides inside the United States, within one city or between two, and to ride-hailing onlyonly. The directory badge is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee how they behave. Only connect what comes from a publisher you know. If you need something to run without you on a schedule, look at the automation side gathered under Integrations.
Need help connecting Uber to Claude?
A person reads every message.