
Keithah Tessie Mcp
This connects Claude to the Tessie API for Tesla vehicle control and telemetry. You get six tools: roster and state snapshots, battery details, drive history with coordinate paths, and a unified command interface for locks, charging, climate, sentry mode, and cabin overheat protection. Destructive operations require explicit confirmation flags. The developer ships both stdio and streamable HTTP transports, includes live smoke tests against the real API, and caches read requests with short TTLs to keep token usage reasonable. Reach for this when you want an LLM to monitor charging costs, pull trip data, or issue commands without opening the Tesla app.
- GitHub stars
- 6
- tools
- 5
- auth
- Required
- transport
- HTTP
- last updated
- Sep 30, 2025
Tools
5 toolsPublic tool metadata for what this MCP can expose to an agent.
list_vehicles
No parameter schema in public metadata yet.
get_vehicle
No parameter schema in public metadata yet.
analyze_history
No parameter schema in public metadata yet.
get_driving_path
No parameter schema in public metadata yet.
vehicle_command
No parameter schema in public metadata yet.
Sponsors
Readme
Tessie MCP
[!NOTE] This repository is archived. Tessie now publishes an official MCP server. See the Tessie MCP reference documentation.
Personal, self-hosted MCP access to Tessie. It is a Streamable HTTP server at /mcp, designed for one owner and protected by a static bearer token.
Setup
- Generate a Tessie access token at https://dash.tessie.com/settings/api.
- Create
.envfrom.env.exampleand generateMCP_AUTH_TOKENwithopenssl rand -base64 48. - Start the service:
docker compose up -d --build. - Configure an MCP client with URL
http://127.0.0.1:3000/mcpand headerAuthorization: Bearer <MCP_AUTH_TOKEN>.
TESSIE_API_KEY never leaves the server. Passing vin to get_vehicle selects and persists the default vehicle; later calls can omit it.
Tools
list_vehicles, get_vehicle, analyze_history, get_driving_path, and vehicle_command. History analysis defaults to 90 days. Autopilot/FSD values are Tessie's native autopilot_distance and historical autopilot telemetry; they do not uniquely prove FSD usage.
Remote access
Details
- Repository
- github.com/keithah/tessie-mcp
- Transport
- HTTP
- Auth
- Required
- Registry
- MCP registry, active