Access and analyze Tesla vehicle data through the Tessie API.
List all vehicles associated with the Tessie account
Retrieve current vehicle state including location, battery level, and odometer reading (with caching option)
Get driving history within specified date ranges with configurable limits
Find drives to specific locations with mileage information and date filtering
Calculate total miles driven during weekly or custom time periods
Provides access to Tesla vehicle data through the Tessie API, enabling queries about vehicle location, battery level, charging status, odometer readings, driving history, and mileage calculations using natural language.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Tessie MCP Extension how much battery do I have left and when should I charge?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Generate a Tessie access token at https://dash.tessie.com/settings/api.
Create .env from .env.example and generate MCP_AUTH_TOKEN with openssl rand -base64 48.
Start the service: docker compose up -d --build.
Configure an MCP client with URL http://127.0.0.1:3000/mcp and header Authorization: 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.
Related MCP server: Tesla MCP Server
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.
For a temporary URL without a tunnel token, run the app locally then execute cloudflared tunnel --url http://127.0.0.1:3000. For a stable named tunnel, set TUNNEL_TOKEN in .env and run docker compose -f docker-compose.yml -f docker-compose.tunnel.yml up -d.
The app bearer token remains required even behind Cloudflare.
Use examples/nginx.conf; preserve the Authorization header, disable buffering, and use long timeouts.
Use examples/Caddyfile; it forwards headers and supports streaming by default.
curl http://127.0.0.1:3000/healthz verifies liveness. The server has no command-line operation that invokes vehicle commands.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
WHOOP recovery, strain, sleep and workouts in Claude via official WHOOP OAuth. Free, open source.
Garmin data in Claude & ChatGPT via the Garmin Health API. OAuth sign-in, no password sharing.
Connect Claude to Fathom meeting recordings, transcripts, and summaries
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/keithah/tessie-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
