MCP Uber Server
Related Servers
Alternatives to MCP Uber Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server connector for Uber ride-sharing, enabling ride requests, fare estimates, and trip tracking via browser automation.7 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI assistants to search for rental cars, query prices, and access map services using the AMAP API.8 npm1MIT
- AlicenseAqualityDmaintenanceMCP server for Uber Eats that lets AI agents search restaurants, browse menus, place orders, and track deliveries using Playwright browser automation.1148 npm3MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to order food from TGO Yemek by browsing restaurants, managing carts, and completing checkouts. It allows users to handle address selection and order tracking directly through natural language interactions.22 npm13MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that connects AI assistants to the TehProf Booking platform for checking real-time availability and managing reservations.MIT
- FlicenseNot gradedqualityBmaintenanceAn MCP server enabling AI assistants to make voice calls, send SMS/MMS, and manage group conversations using Twilio and OpenAI.5 npm-
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.