list_vehicles
Every vehicle on your account — detailed or compact list.
vehicles
Model Context Protocol
Your vehicles, in any AI assistant
Use Teslascope as an MCP server: list vehicles, trips, charging, and send supported commands. Works with clients that support remote MCP over HTTP.
How it works
Three steps from “paste a URL” to asking your assistant about your car.
1
Add the server in your client
Paste the MCP origin into a compatible app (e.g. Codex). The client uses GET to discover OAuth, then POST for the protocol.
2
Sign in with Teslascope
Complete OAuth in the browser, or configure a personal access token with the scopes you need (vehicles, and controls scopes for commands).
3
Use natural language
Ask the model to list vehicles, summarize drives, or run allowed commands using your public_id as vehicle_id.
Endpoints
The MCP host is separate from this page so https://teslascope.com/mcp can stay a friendly overview while tools talk to the origin below.
MCP server (Streamable HTTP)
https://mcp.teslascope.com
OAuth protected-resource metadata
https://mcp.teslascope.com/.well-known/oauth-protected-resource
Remote clients receive WWW-Authenticate with resource_metadata on GET. This page also sends the same hint (plus a Link header) so discovery works if something probes here first.
Tools
These identifiers match what the model sees when calling your Teslascope MCP server.
get_vehicle
Full detail for one vehicle by public id.
vehicles
get_drives
Driving history with optional date filters and pagination.
vehicles
get_drive
A single drive session by id.
vehicles
get_charges
Charging sessions for a vehicle.
vehicles
get_charge
One charging session by id.
vehicles
send_vehicle_command
Remote actions — horn, locks, climate, charge limit, and more.
vehicles
controls
Use each vehicle’s Teslascope public_id as vehicle_id. If the model doesn’t know ids yet, have it call list_vehicles first.