MCP Uber Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UBER_CLIENT_ID | Yes | Your Uber API Client ID from the Uber Developer Dashboard | |
| UBER_ENVIRONMENT | No | The Uber API environment (sandbox or production) | sandbox |
| UBER_REDIRECT_URI | No | The redirect URI for OAuth callback | http://localhost:3000/callback |
| UBER_CLIENT_SECRET | Yes | Your Uber API Client Secret from the Uber Developer Dashboard |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| uber_get_auth_urlB | Get the Uber authorization URL for user to authenticate |
| uber_set_access_tokenB | Set the access token for a user after OAuth callback |
| uber_get_price_estimatesC | Get price estimates for a ride between two locations |
| uber_request_rideC | Request an Uber ride |
| uber_get_ride_statusC | Get the current status of a ride request |
| uber_cancel_rideB | Cancel an ongoing ride request |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: authorization (get_auth_url, set_access_token), ride lifecycle (request_ride, get_ride_status, cancel_ride), and price estimation (get_price_estimates). The descriptions reinforce these distinct roles, making tool selection straightforward for an agent.
All tools follow a consistent 'uber_verb_noun' pattern with snake_case throughout (e.g., uber_cancel_ride, uber_get_price_estimates). This predictability makes the tool set easy to navigate and understand at a glance.
With 6 tools, this server is well-scoped for its Uber ride-hailing domain. It covers essential operations without bloat: authentication, price checks, ride requests, status tracking, and cancellation. Each tool earns its place in supporting a complete workflow.
The tool set provides complete coverage for the Uber ride lifecycle: authentication (get_auth_url, set_access_token), pre-ride (get_price_estimates), active ride (request_ride, get_ride_status, cancel_ride). There are no obvious gaps; agents can handle the full process from login to ride completion or cancellation.