uber_cancel_ride
Cancel an ongoing ride request
LABSCO SUMMARY
It books a real ride, so the token handshake is the first thing you have to get right.
Authorization is not hidden: the authorization URL has its own tool, the returned token is stored by another, and every remaining call carries the same userId, which is what lets the server serve more than one rider. Locations are latitude and longitude only — there is no address or place lookup — and a ride request additionally needs a productId and a fareId, so the coordinates alone will not book anything. UBER_ENVIRONMENT is where you decide whether a request is a sandbox exercise or a car arriving.
What it is
An Uber ride-request client with its OAuth handshake exposed as tools, so one server can hold tokens for more than one rider.
What you get
- An authorization URL to hand a rider, and a call to store the access token that comes back for their userId
- Price estimates for a trip given start and end latitude and longitude
- A ride request placed against a chosen productId and fareId
- Current status of a request, and cancellation of one that is still running
Requirements
An Uber developer application supplying four environment variables — UBER_CLIENT_ID, UBER_CLIENT_SECRET, UBER_REDIRECT_URI and UBER_ENVIRONMENT — and a rider who completes the OAuth callback so a token can be stored against their userId.
Setup effort
One command plus credentials — npx mcp-uber, then supply credentials
USE CASES
01
Getting a rider authorised before anything can be booked
Hand the rider the authorization URL, then store the token that comes back against their userId so later calls act on their behalf.
02
Pricing a trip before committing to it
Start and end coordinates return the estimate, which is the check worth doing before a request is placed.
03
Following a ride you booked from the same conversation
Place the request against a productId and fareId, then track the request ID as the ride runs, and cancel it if plans change.
6 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
uber_get_auth_url
Get the Uber authorization URL for user to authenticate
uber_get_price_estimates
Get price estimates for a ride between two locations
uber_get_ride_status
Get the current status of a ride request
uber_request_ride
Request an Uber ride
uber_set_access_token
Set the access token for a user after OAuth callback
BEFORE YOU INSTALL
What to know first
Tools you get
6 tools when we connected. UBER_ENVIRONMENT defaults to sandbox, where uber_request_ride simulates rides with no charge. Real bookings need production mode and Uber's approval of your app for the privileged request scope.
Requires
- npx on PATH
- UBER_CLIENT_ID in your environment
- UBER_CLIENT_SECRET in your environment
Where it runs
Both documented setups run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 6 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx mcp-uberMCP Clients
Claude Desktop — global npm
CLAUDE DESKTOP — GLOBAL NPM · JSON
{
"mcpServers": {
"uber": {
"command": "mcp-uber",
"env": {
"UBER_CLIENT_ID": "<YOUR_UBER_CLIENT_ID>",
"UBER_CLIENT_SECRET": "<YOUR_UBER_CLIENT_SECRET>",
"UBER_REDIRECT_URI": "http://localhost:3000/callback",
"UBER_ENVIRONMENT": "sandbox"
}
}
}
}Claude Desktop — npx
CLAUDE DESKTOP — NPX · JSON
{
"mcpServers": {
"uber": {
"command": "npx",
"args": [
"mcp-uber"
],
"env": {
"UBER_CLIENT_ID": "<YOUR_UBER_CLIENT_ID>",
"UBER_CLIENT_SECRET": "<YOUR_UBER_CLIENT_SECRET>",
"UBER_REDIRECT_URI": "http://localhost:3000/callback",
"UBER_ENVIRONMENT": "sandbox"
}
}
}
}
