Waymo MCP
Related Servers
Alternatives to Waymo MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server for Google Maps — routing, place discovery, and commute comparison over stdio.41ISC
- FlicenseNot gradedqualityCmaintenanceProvides mock travel planning tools including flight and hotel search, recommendations, and multi-turn trip drafting. Supports stdio and HTTP transports and is intended for testing/demo purposes only.-
- AlicenseAqualityCmaintenanceEnables agents to search places, get live fares and route previews, list payment methods, book rides, monitor ride and vehicle status, preview and confirm cancellations, and retrieve ride history for Tesla Robotaxi rider accounts.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables a local Grok Bot to talk to the unofficial MySubaru API over stdio, supporting vehicle status, locate, tire pressure, fuel, odometer, climate presets, and explicit lock/unlock/remote start actions without exposing secrets.1MIT
- AlicenseAqualityCmaintenanceA local stdio MCP server exposing the Bixi Montréal bike-share API as tools, enabling users to list stations in service and view their ride history through MCP clients.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables assistants to sign in to and interact with a user's own Hinge account through MCP tools, resources, and prompts, including session lifecycle and account reads. Runs locally over stdio or Streamable HTTP with authentication options.12MIT
TDQS
Scored across 8 tools
Each tool maps to a distinct phase of the Waymo rider workflow: place search, quote, booking, cancellation, payment methods, trip history, and active ride status. The two ride-related tools are separated by historical trips versus active/cached status, so there is no meaningful overlap.
Most tools follow a clear waymo_<verb>_<noun> pattern such as get_quote, book_ride, and cancel_ride. waymo_ride_history and waymo_ride_status break the pattern by leading with a noun, but the shared prefix and consistent snake_case keep the set readable.
Eight tools is well-scoped for a ride-hailing server: the set covers discovery, quoting, booking, cancellation, payments, and trip lookups without unnecessary duplication. Each tool serves a concrete user-facing need.
The core rider lifecycle is well covered: search places, get a quote, book, cancel with fee preview, list payment methods, and retrieve history/status. There are minor gaps like no explicit way to fetch details for an arbitrary past trip or manage payment methods, but these do not block the main workflows.