Provides access to Tesla vehicle telemetry data including battery status, charging information, climate controls, heater settings, location/GPS data, and vehicle state through the Tessie API.
Tesla Tessie MCP Server
A Model Context Protocol (MCP) server that provides Tesla vehicle telemetry data via the Tessie API. Exposes vehicle status, battery, charging, climate, and location data as tools for LLM consumption.
Features
Intelligent Caching: Configurable data refresh intervals to minimize API calls
Thread-Safe: Concurrent access to cached data is safely handled
LLM-Optimized Output: Human-readable formatted strings for each data point
Comprehensive Telemetry: 30+ tools covering all vehicle data categories
Installation
Configuration
Environment Variables
Create a .env file in the project root:
Vehicle Configuration
The vehicle plate can also be configured in config.py:
Usage
1. Create .env File
Copy the example and add your Tessie API token:
Edit .env:
Get your token from: https://dash.tessie.com/settings/api
2. Running the MCP Server
Local Mode (STDIO)
Remote Mode (HTTP/SSE)
This starts an HTTP server with:
SSE endpoint:
http://your-server:8000/sseHealth check:
http://your-server:8000/health
3. Connecting to the MCP Server
Option A: Cursor IDE Integration
Add to your Cursor settings (~/.cursor/mcp.json or via Settings > MCP):
After adding, restart Cursor. The Tesla tools will appear in your tool list.
Option B: Claude Desktop Integration
Add to Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
Option C: Direct Testing with MCP Inspector
Option D: Remote Connection (HTTP/SSE)
Start the server in SSE mode on your remote machine:
Then connect from a client using the SSE URL:
For Cursor/Claude, configure with SSE transport:
Option E: Programmatic Usage (Python)
Available Tools
Battery & Charging
Tool | Description |
| Current battery percentage |
| Remaining energy in kWh |
| Total lifetime energy consumption |
| Battery heater status (cold weather) |
| Current charging status |
| Charging limit percentage |
| Charge port door status |
| Time remaining to full charge |
| Estimated completion datetime |
| Comprehensive battery summary |
Climate & Temperature
Tool | Description |
| HVAC system status |
| Ambient temperature |
| COP enabled status |
| Fan-only COP capability |
Heaters
Tool | Description |
| Driver seat heater level |
| Passenger seat heater level |
| Rear left seat heater level |
| Rear center seat heater level |
| Rear right seat heater level |
| Steering wheel heater status |
| Side mirror heaters status |
| Wiper blade heater status |
| Summary of all heaters |
Drive State & Location
Tool | Description |
| GPS coordinates and heading |
| Current vehicle speed |
| Power usage/regeneration |
| Current gear (P/R/N/D) |
| Active navigation info |
Vehicle State
Tool | Description |
| Service mode status |
| Sentry Mode status |
| Vehicle's custom name |
Architecture
Telemetry Class
The Telemetry class implements a dual-method pattern for each data field:
Private methods (
_get_*): Return raw values for programmatic usePublic methods (
get_*): Return formatted strings for LLM consumption
Example:
Caching Strategy
Data is cached with timestamps
On each request, elapsed time is checked against the interval
If stale, fresh data is fetched from Tessie API
Thread-safe access using locks
License
MIT