robotaxi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROBOTAXI_AREA_NAME | No | Optinal area name (e.g., '1:bay-area') used with ROBOTAXI_REFRESH_TOKEN. | |
| ROBOTAXI_REFRESH_TOKEN | No | Tesla Robotaxi refresh token obtained from your own signed-in app session. | |
| ROBOTAXI_CREDENTIALS_FILE | No | Path to a credentials file containing refresh_token and optinal area_name. |
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 |
|---|---|
| robotaxi_search_placesA | Resolve a place name or address to Robotaxi locations. |
| robotaxi_ride_historyB | Return recent Robotaxi rides from Tesla's ownership service. |
| robotaxi_ride_statusA | Return the active ride or most recent terminal TripX session. |
| robotaxi_list_payment_methodsA | List safe labels and IDs for Robotaxi-compatible saved payment methods. |
| robotaxi_get_quoteB | Get a live fare and route preview for two Robotaxi locations. |
| robotaxi_book_rideA | Book a quoted ride only after the user explicitly requests it. |
| robotaxi_preview_cancellationA | Preview the active ride before cancellation without cancelling it. |
| robotaxi_cancel_rideA | Cancel after a fresh 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 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.
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.
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.
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.