Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TESLA_REGIONNoTesla region. One of na, eu, or cn. A wrong region returns HTTP 421.
TESLA_TOKEN_KEYYesAES key used to encrypt the Tesla tokens. It is not written into the token file.
TESLA_MCP_DATA_DIRNoOverrides the data directory. Default is /workspace/.tesla-mcp/ on the Grok Bot computer, which holds the encrypted tokens (tokens.json.enc) and history (history.db)./workspace/.tesla-mcp/
TESLA_ENABLE_COMMANDSNoSet to true to request the vehicle_cmds scope. Only used by the optional tesla-commands-mcp program, which is off by default; tesla-mcp itself never requests vehicle_cmds.false
TESLA_ENABLE_LOCATIONNoSet to true to enable the vehicle_location scope (opt-in). You must sign in again after changing it.false
TESLA_COMMANDS_DRY_RUNNoSet to false (0, no, and off also turn it off) to leave dry-run mode for the optional vehicle commands. A blank or unrecognized value stays in dry-run.true
TESLA_ENABLE_CHARGING_HISTORYNoSet to true to enable the vehicle_charging_cmds scope for charging history (opt-in, grants charge control too). You must sign in again after changing it.false

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
tesla_list_vehiclesA

List vehicles on the Tesla account. VINs are masked. This does not wake the car.

tesla_get_statusA

Battery, range, charging, and lock state. Live when the car is online, otherwise cached.

Distances are miles, as returned by the Fleet API. This does not wake the car.

tesla_get_climateA

Inside and outside temperature in Celsius, and whether climate is on. Does not wake the car.

tesla_get_odometerA

Odometer in miles, plus distance over a period from local snapshots. Does not wake the car.

tesla_get_softwareA

Installed software version and pending update status. Does not wake the car.

Field names follow vehicle_state.car_version and vehicle_state.software_update. A missing value means this firmware did not return that field.

tesla_query_historyA

Time series from the local snapshot database. Does not call Tesla or wake the car.

tesla_reportA

A ready-to-read summary. Local reports do not wake the car.

weekly_mileage uses the last 7 days of odometer snapshots. range_trend compares 30-day and 90-day normalized rated range. low_charge alerts below 30% when unplugged, and says so if the snapshot is older than 6 hours. charging_summary calls Tesla only when charging history is opted in.

tesla_wake_and_refreshA

Wake the car, then store a fresh snapshot. Refuses unless confirm is true.

Default budget: at most one wake every 30 minutes and 3 wakes in any 24-hour period. A hard cap of 3 wakes per minute cannot be raised. This is the only wake path.

tesla_usageA

Calls recorded this month, estimated cost, and the wake budget. Local only.

Prompts

Interactive templates invoked by user choice

NameDescription
weekly_mileage_reportSummarize miles driven over the last 7 days from local snapshots.
range_trend_reportCompare recent normalized battery range with the 90-day baseline.
low_charge_checkCheck the latest snapshot for a low, unplugged battery. Does not wake the car.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 9 tools

Disambiguation4/5

Each tool targets a distinct data slice (climate, status, odometer, software, history, usage) and the descriptions repeatedly clarify scope and wake behavior. There is mild overlap between tesla_get_status (battery, range, charging, lock) and the narrower getters (climate, odometer), and between tesla_query_history and tesla_report, but the raw-vs-summary framing keeps them separable.

Naming Consistency4/5

All tools share a tesla_ prefix and most follow a clean verb_noun pattern (list_vehicles, get_climate, get_status, query_history, wake_and_refresh). tesla_report and tesla_usage break the pattern by being bare verbs/nouns, a minor inconsistency in an otherwise predictable set.

Tool Count5/5

Nine tools is well within the sweet spot for a vehicle telemetry server, with each tool covering a distinct aspect (fleet listing, per-signal reads, history, reports, wake, quota). Nothing feels redundant or padded.

Completeness4/5

The read/telemetry lifecycle is well covered: vehicles, climate, status, odometer, software, historical time series, summary reports, wake-and-snapshot, and usage/quota. The only gap is that there are no control operations (lock, climate start, charging control), which appears intentional given the strict wake budget and read-only framing, so agents can still answer monitoring questions without dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues