Tessie MCP Extension
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 "Deploy 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.
Tessie MCP
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.
Related MCP server: Tesla MCP Server
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
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.
Nginx
Use examples/nginx.conf; preserve the Authorization header, disable buffering, and use long timeouts.
Caddy
Use examples/Caddyfile; it forwards headers and supports streaming by default.
Smoke check
curl http://127.0.0.1:3000/healthz verifies liveness. The server has no command-line operation that invokes vehicle commands.
Available Tools
5 toolsget_driving_historyCInspect
Get driving history for a vehicle within a date range
Inputs: vin (required), end_date, limit, start_date.
get_mileage_at_locationCInspect
Find drives to a specific location and return mileage information
Inputs: location (required), vin (required), end_date, start_date.
get_vehicle_current_stateCInspect
Get the current state of a vehicle including location, battery level, odometer reading
Inputs: vin (required), use_cache.
get_vehiclesBInspect
List all vehicles in the Tessie account
Inputs: no named parameters.
get_weekly_mileageCInspect
Calculate total miles driven in a specific week or time period
Inputs: end_date (required), start_date (required), vin (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
The tools have mostly distinct purposes, but 'get_driving_history' and 'get_weekly_mileage' could be confused as both involve retrieving mileage data over time periods. However, their descriptions clarify that one is for general history and the other specifically for weekly totals, reducing ambiguity.
All tool names follow a consistent 'get_*' verb_noun pattern, making them predictable and easy to understand. The naming is uniform across all five tools, with no deviations in style or convention.
Five tools is reasonable for a vehicle management server, though it feels slightly thin for comprehensive coverage. The tools cover key read operations but may benefit from additional actions like vehicle control or settings management to be fully scoped.
The server provides good read-only coverage for vehicle data, including state, history, and mileage. However, there are notable gaps such as missing update/control operations (e.g., lock/unlock, climate control) and administrative functions, which limits agent workflows to retrieval only.
Maintenance
Related MCP Connectors
Tesla data for your AI: battery, range, charging, tires, alerts, history. Controls off by default.
Control your Tesla from your AI assistant - climate, charging, access, and security.
AI for your car: check charge, start climate, lock/unlock, open trunk via Tesla Fleet API. OAuth.
Tesla Fleet API for AI: send navigation destinations, read battery and location, run car commands.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides intelligent Tesla vehicle analytics and control through the Tessie API, including real-time status monitoring, charging cost optimization, efficiency trend analysis, trip planning, and predictive insights for Tesla owners.MIT
- AlicenseNot gradedqualityDmaintenanceEnables control and monitoring of Tesla vehicles through the Tessie API, providing access to vehicle state (battery, location, climate) and commands (lock/unlock, climate control, navigation) with support for both local and Cloudflare Worker deployment.11MIT
- FlicenseNot gradedqualityDmaintenanceProvides access to Tesla vehicle telemetry data via the Tessie API, enabling real-time monitoring of battery status, charging state, climate controls, location, and other vehicle metrics through 30+ tools with intelligent caching.-
- AlicenseAqualityBmaintenanceEnables read-only access to vehicle data via the unofficial Rivian GraphQL API, allowing users to monitor battery levels, OTA updates, and charging status. It provides tools to check vehicle state and user account information directly through Claude.999 npm4MIT