A
licenseA
qualityD
maintenanceEnables AI agents to manage cab bookings, estimate fares, and dispatch drivers with a 2-tier priority algorithm for hotel guests, providing 18 MCP tools for driver management, dispatch, and ride lifecycle.
20
MIT
robotaxi-mcp
Related Servers
Alternatives to robotaxi-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to search for cabs, view prices, and book rides through the open Beckn Protocol by connecting to Beckn-compliant mobility providers like Namma Yatri and ONDC.-
- AlicenseAqualityAmaintenanceEnables an AI assistant to find places, compare live Uber ride prices, request rides behind a price-capped preview/confirm step, track or cancel active rides, and review trip history.13496 PyPIMIT
- AlicenseBqualityCmaintenanceEnables end-to-end ride-booking workflows, including pickup and destination selection, ride estimates, solo or ShareMatch shared rides, driver tracking with live ETAs, trip management, payments, receipts, saved places, and safety/support tools.39MIT
- AlicenseBqualityBmaintenanceEnables AI agents to get 99Pop and 99Moto fare estimates, ride history, and live tracking while keeping credentials local and ride requests fail-closed by default.1423 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible agents to view and build trip itineraries through conversation, including places, notes, hotels, transit, rentals, checklists, expenses, and search across places, hotels, and guides.173 npmMIT
TDQS
A3.8/5.0
Scored across 8 tools
Disambiguation5/5
Each tool targets a distinct part of the ride lifecycle: place search, quoting, booking, status/history, payment listing, and cancellation preview/execution. The two ride-history/status tools are separated by active/recent vs. historical trips, and the cancellation tools are explicitly split into preview and confirm.
Naming Consistency4/5
Most tools follow a clear robotaxi_<verb>_<noun> pattern, e.g. search_places, get_quote, book_ride, cancel_ride. robotaxi_ride_status and robotaxi_ride_history break the verb pattern slightly, but the prefix and overall readability keep the set predictable.
Tool Count5/5
Eight tools is a well-scoped size for a robotaxi server, covering the main user journey without unnecessary surface area. Each tool corresponds to a needed action or query in the domain.
Completeness5/5
The tool set covers the core ride-hailing lifecycle: discover places, get quotes, book, check status/history, list payment methods, and preview/cancel. The explicit preview-before-cancel pairing avoids dead ends and gives agents safe workflows.
Maintenance
ActivityStale
ResponsivenessNo issues