Tools & Safety

The Teslemetry MCP server exposes four tools. Read tools are served from cache and are free; only send_command can wake a vehicle or consume credits.

Tools

products

Lists the vehicles and energy sites your subscription can control, with each vehicle's known issue (if any) and capability flags. Cache‑only — no credits, never wakes a vehicle. Agents should call this first to discover VINs and site IDs.

get_vehicle_telemetry

Returns the latest cached Fleet Telemetry for a vehicle, with each value stamped with when it was received. Cache‑only — never wakes the car and costs no credits.

• vin — the vehicle to read.
• fields (optional) — specific telemetry field names (e.g. BatteryLevel, ChargeState) to return. Omit for the full snapshot.

list_commands

Lists every available vehicle and energy command with its parameters, including long‑tail commands not exposed as first‑class tools. Pair with send_command to invoke any of them.

• filter (optional) — a case‑insensitive substring to narrow the list.

send_command

Invokes any vehicle or energy command by name. May wake the vehicle and cost credits.

• command — a command name from list_commands, e.g. command_door_lock or energy_backup.
• vin — for vehicle commands.
• site_id — for energy commands.
• params — the command's parameters, as defined by its schema.

Credits & waking

Reads (products, get_vehicle_telemetry, list_commands) are always free and never wake your vehicle.

send_command runs the real Fleet API command pipeline. If the vehicle is asleep, Teslemetry wakes it automatically — this costs credits and adds a short delay. See Handling Sleep for the wake‑up process and credit costs, and Command Signing for how signed commands are delivered.

Permissions

An agent connected over MCP has the same access to your Tesla products that you do. There is no separate read‑only mode at the connection level — if you need to restrict an agent to reads, configure it on the client side (for example, by disabling the send_command tool, or keeping command approvals enabled).

Authentication

The server accepts two kinds of credentials:

• OAuth 2.0 with Dynamic Client Registration and PKCE — clients discover the authorization server automatically and send you to teslemetry.com/connect to approve access. No client secret is required.
• Bearer token — pass a Teslemetry access token as Authorization: Bearer YOUR_TESLEMETRY_TOKEN for unattended use.

The endpoint advertises standard discovery documents at /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server, and automatically routes to the correct regional cluster for your account.