Waymo MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WAYMO_DEVICE_ID | No | Optional device ID associated with the refresh token. Only used when WAYMO_REFRESH_TOKEN is set. | |
| WAYMO_REFRESH_TOKEN | No | Your Waymo refresh token. Optional if WAYMO_CREDENTIALS_FILE or the default credentials file is used. | |
| WAYMO_CREDENTIALS_FILE | No | Path to a credentials JSON file containing refresh_token and optional device_id. Used if WAYMO_REFRESH_TOKEN is not set. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| waymo_search_placesA | Resolve a place name or address to canonical Waymo locations. |
| waymo_ride_historyB | Return recent Waymo trips, including cancelled and completed rides. |
| waymo_ride_statusA | Return the active ride and any terminal trip still cached by Waymo. |
| waymo_list_payment_methodsA | List safe payment-method labels and IDs accepted by the booking tool. |
| waymo_get_quoteB | Quote an ASAP route, or re-quote using one returned scheduling option. |
| waymo_book_rideB | Book a quoted ride. Call only after the user explicitly requests booking. |
| waymo_preview_cancellationA | Preview cancellation and its fee without cancelling the active ride. |
| waymo_cancel_rideA | Cancel after a fresh fee preview and explicit user confirmation. |
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 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.