Provides control and monitoring of Tesla vehicles through the Tessie API, including state queries (battery, range, location, climate, doors, charging status) and commands (lock/unlock, climate control, trunk operations, sentry mode, navigation)
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., "@Tesla MCP Serverwhat's my battery level and estimated range?"
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.
Tesla MCP Server
Streamable HTTP MCP server for Tesla vehicle control via the Tessie API.
Author: overment
You connect this server to your MCP client at your own responsibility. Language models can make mistakes, misinterpret instructions, or perform unintended actions. Always verify commands before execution, especially for actions like unlocking, opening trunks, or sending navigation destinations.
The HTTP layer is designed for convenience during development, not production-grade security. If deploying remotely, harden it: proper token validation, secure storage, TLS termination, strict CORS/origin checks, rate limiting, and audit logging.
Notice
This repo works in two ways:
As a Node/Hono server for local workflows
As a Cloudflare Worker for remote interactions
Features
✅ State — Battery, range, location, climate, doors, charging status
✅ Commands — Lock/unlock, climate, trunks, sentry, navigation
✅ Location-aware — GPS coordinates for context-aware interactions
✅ Dual Runtime — Node.js/Bun or Cloudflare Workers
Design Principles
LLM-friendly: Two unified tools, not 1:1 API mirrors
Watch-ready: Designed for AI agents with location context
Secure: Tessie API key stored as secret, clients use separate bearer token
Clear feedback: Detailed command results and vehicle state
Installation
Prerequisites: Bun, Tessie Account.
Ways to Run (Pick One)
Local Development — Standard setup with bearer token auth
Cloudflare Worker (wrangler dev) — Local Worker testing
Cloudflare Worker (deploy) — Remote production
1. Local Development — Quick Start
Get Tessie credentials:
Visit developer.tessie.com
Go to Developer Settings → Generate Access Token
Copy your access token
Note your vehicle's VIN
Configure environment:
cd tesla-mcp
bun install
cp .env.example .envEdit .env:
PORT=3000
AUTH_ENABLED=true
AUTH_STRATEGY=bearer
# Generate with: openssl rand -hex 32
BEARER_TOKEN=your-random-auth-token
# Tessie credentials
TESSIE_ACCESS_TOKEN=your-tessie-access-token
TESSIE_VIN=your-vehicle-vinRun:
bun dev
# MCP: http://127.0.0.1:3000/mcpClaude Desktop / Cursor:
{
"mcpServers": {
"tesla": {
"command": "npx",
"args": ["mcp-remote", "http://localhost:3000/mcp", "--transport", "http-only"],
"env": { "NO_PROXY": "127.0.0.1,localhost" }
}
}
}2. Cloudflare Worker (Local Dev)
bun x wrangler dev --local | catCreate .dev.vars for local secrets:
BEARER_TOKEN=your_random_auth_token
TESSIE_ACCESS_TOKEN=your_tessie_token
TESSIE_VIN=your_vehicle_vinEndpoint: http://127.0.0.1:8787/mcp
3. Cloudflare Worker (Deploy)
Create KV namespace for session storage:
bun x wrangler kv:namespace create TOKENSOutput will show:
Add the following to your wrangler.toml:
[[kv_namespaces]]
binding = "TOKENS"
id = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"Update
wrangler.tomlwith your KV namespace ID:
[[kv_namespaces]]
binding = "TOKENS"
id = "your-kv-namespace-id-from-step-1"Set secrets:
# Generate a random token for client authentication
openssl rand -hex 32
bun x wrangler secret put BEARER_TOKEN
# Paste the generated token when prompted
# Tessie API credentials
bun x wrangler secret put TESSIE_ACCESS_TOKEN
# Paste your Tessie token when prompted
bun x wrangler secret put TESSIE_VIN
# Paste your VIN when promptedDeploy:
bun x wrangler deployEndpoint: https://<worker-name>.<account>.workers.dev/mcp
Client Configuration
Alice App
Add as MCP server with:
URL:
https://your-worker.workers.dev/mcpType:
streamable-httpHeader:
Authorization: Bearer <your-BEARER_TOKEN>
Claude Desktop / Cursor (Local Server)
{
"mcpServers": {
"tesla": {
"command": "npx",
"args": ["mcp-remote", "http://127.0.0.1:3000/mcp", "--transport", "http-only"],
"env": { "NO_PROXY": "127.0.0.1,localhost" }
}
}
}Claude Desktop / Cursor (Cloudflare Worker)
{
"mcpServers": {
"tesla": {
"command": "npx",
"args": ["mcp-remote", "https://your-worker.workers.dev/mcp", "--transport", "http-only"]
}
}
}MCP Inspector (Quick Test)
bunx @modelcontextprotocol/inspector
# Connect to: http://localhost:3000/mcp (local) or https://your-worker.workers.dev/mcp (remote)Tools
tesla_state
Get the current state of your Tesla vehicle.
// Input
{}
// Output
{
display_name: string; // Vehicle name
battery_level: number; // 0-100%
battery_range_km: number; // Estimated range in km
charging: {
state: string; // "Disconnected", "Charging", "Complete", "Stopped"
minutes_remaining: number | null;
charge_limit: number; // Charge limit %
};
location: {
latitude: number;
longitude: number;
heading: number; // 0-359°
speed: number | null; // km/h or null if parked
};
locked: boolean;
sentry_mode: boolean;
climate: {
is_on: boolean;
inside_temp: number; // °C
outside_temp: number; // °C
target_temp: number; // °C
is_defrosting: boolean;
};
doors: {
front_left: boolean; // true = open
front_right: boolean;
rear_left: boolean;
rear_right: boolean;
frunk: boolean;
trunk: boolean;
charge_port: boolean;
};
state: "online" | "asleep" | "offline";
odometer_km: number;
last_updated: string; // ISO 8601
}tesla_command
Execute commands on your Tesla vehicle.
// Input
{
command: "lock" | "unlock" | "start_climate" | "stop_climate" |
"set_temperature" | "start_defrost" | "stop_defrost" |
"open_frunk" | "open_trunk" | "open_charge_port" |
"close_charge_port" | "enable_sentry" | "disable_sentry" |
"flash" | "honk" | "share";
temperature?: number; // Required for set_temperature (15-28°C)
destination?: string; // Required for share
locale?: string; // Optional for share (e.g., "en-US")
}
// Output
{
success: boolean;
command: string;
message: string;
}Commands Reference:
Command | Description | Parameters |
| Lock the vehicle | — |
| Unlock the vehicle | — |
| Start climate control | — |
| Stop climate control | — |
| Set cabin temperature |
|
| Turn on max defrost | — |
| Turn off defrost | — |
| Open front trunk | — |
| Toggle rear trunk | — |
| Open charge port door | — |
| Close charge port door | — |
| Enable sentry mode | — |
| Disable sentry mode | — |
| Flash the lights | — |
| Honk the horn | — |
| Send destination to navigation |
|
Examples
1. Get vehicle state
{
"name": "tesla_state",
"arguments": {}
}2. Lock the car
{
"name": "tesla_command",
"arguments": {
"command": "lock"
}
}3. Set temperature to 22°C
{
"name": "tesla_command",
"arguments": {
"command": "set_temperature",
"temperature": 22
}
}4. Start climate before leaving
{
"name": "tesla_command",
"arguments": {
"command": "start_climate"
}
}5. Navigate to a destination
{
"name": "tesla_command",
"arguments": {
"command": "share",
"destination": "Golden Gate Bridge, San Francisco"
}
}Authentication Flow
┌─────────────────────────────────────────────────────────────────┐
│ Client (Alice App, Claude Desktop) │
│ │ │
│ │ Authorization: Bearer <BEARER_TOKEN> │
│ ▼ │
│ ┌─────────────────────────────────────────────────────────┐ │
│ │ Cloudflare Worker / Node.js Server │ │
│ │ │ │
│ │ 1. Validate BEARER_TOKEN (client auth) │ │
│ │ 2. Use TESSIE_ACCESS_TOKEN (internal API key) │ │
│ │ │ │
│ │ env.TESSIE_ACCESS_TOKEN ──┐ │ │
│ │ env.TESSIE_VIN ───────────┼──► TessieClient │ │
│ │ │ │ │ │
│ │ │ ▼ │ │
│ │ │ api.tessie.com │ │
│ └─────────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────────┘Key points:
BEARER_TOKEN: Random token you generate — authenticates clients to your MCP serverTESSIE_ACCESS_TOKEN: Your Tessie API key — used internally by the serverClients never see your Tessie credentials
HTTP Endpoints
Endpoint | Method | Purpose |
| POST | MCP JSON-RPC 2.0 |
| GET | Health check |
Development
bun dev # Start with hot reload
bun run typecheck # TypeScript check
bun run lint # Lint code
bun run build # Production build
bun start # Run productionArchitecture
src/
├── shared/
│ └── tools/
│ ├── tesla-state.ts # Get vehicle state
│ └── tesla-command.ts # Execute commands
├── services/
│ └── tessie.service.ts # Tessie API client
├── schemas/
│ ├── commands.ts # Command definitions
│ ├── outputs.ts # Tool output schemas
│ └── tessie.ts # Tessie API response schemas
├── config/
│ └── metadata.ts # Server & tool descriptions
├── index.ts # Node.js entry
└── worker.ts # Workers entryEnvironment Variables
Node.js (.env)
Variable | Required | Description |
| ✓ | Tessie API access token |
| ✓ | Tesla Vehicle VIN |
| ✓ | Auth token for MCP clients |
| Server port (default: 3000) | |
| Server host (default: 127.0.0.1) | |
| Enable auth (default: true) | |
|
|
Cloudflare Workers (wrangler.toml + secrets)
wrangler.toml vars:
AUTH_ENABLED = "true"
AUTH_STRATEGY = "bearer"Secrets (set via
BEARER_TOKEN— Random auth token for clientsTESSIE_ACCESS_TOKEN— Tessie API access tokenTESSIE_VIN— Your vehicle's VIN
KV Namespace:
[[kv_namespaces]]
binding = "TOKENS"
id = "your-kv-namespace-id"Troubleshooting
Issue | Solution |
401 Unauthorized | Check |
"TESSIE_ACCESS_TOKEN not configured" | Set secret: |
"TESSIE_VIN not configured" | Set secret: |
"Tessie API error" | Verify |
Vehicle not found | Check |
Vehicle offline | Vehicle may be in deep sleep. Commands will wake it (takes ~30s) |
Command timeout | Tessie waits up to 90s for vehicle wake. Try again. |
KV namespace error | Run |
"ReadableStream is not defined" | Node.js version too old (needs 18+). Use full path to newer node. |
"spawn bunx ENOENT" | Claude Desktop can't find |
Debugging
Test with MCP Inspector:
bunx @modelcontextprotocol/inspector
# Connect to your endpoint and test toolsCheck Worker logs:
wrangler tailLicense
MIT