Tessie API를 통해 Tesla 차량 제어를 위한 Streamable HTTP MCP 서버.

**Release 상태 (2026-07-27) : **이 저장소 핀 @modelcontextprotocol/server] 및 2.0.0-beta.5, Zod 4 및 후보 2026-07-28 프로토콜. dated 프로토콜과 안정적인 v2 SDK는 이 커밋에서 최종하지 않습니다. 릴리스 게이트가 확인 될 때까지 최종 준수를 주장하지 마십시오.

Bun 및 Cloudflare Workers Entry Point는 배포 당 하나의 fetch-native handler를 공유하고 모든 요청에 대한 신선한 MCP 서버를 만듭니다. 현대 HTTP는 무정; 2025-era 클라이언트와 호환성은 SDK의 무정한 fallback을 사용하고 MCP 세션을 만들지 않습니다.

저자: 과잉

[!수신] 이 서버에 MCP 클라이언트를 자신의 책임에 연결합니다. 언어 모델은 실수를 만들 수 있습니다, misinterpret 지침, 또는 무인 행동을 수행. 항상 실행하기 전에 명령을 확인, 특히 잠금 해제, 개방 트렁크, 또는 탐색 목적지를 전송 같은 작업을 위해. · HTTP 층은 경계된 요구 몸, 정확한 주인 및 근원 수당, 엄격한 CORS 및 활성화될 때 정체되는 부인자 입증을 강제합니다.

Tesla MCP Server

Streamable HTTP MCP server for Tesla vehicle control via the Tessie API.

Release status (2026-07-27): this repository pins @modelcontextprotocol/server and the test-only @modelcontextprotocol/client to 2.0.0-beta.5, with Zod 4 and the candidate 2026-07-28 protocol. The dated protocol and stable v2 SDK are not final at this commit; do not claim final conformance until the release gate is verified.

The Bun and Cloudflare Workers entry points share one fetch-native handler per deployment and create a fresh MCP server for every request. Modern HTTP is stateless; compatibility with 2025-era clients uses the SDK’s stateless fallback and does not create MCP sessions.

Author: overment

[!WARNING] 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 enforces bounded request bodies, exact Host and Origin allowlists, strict CORS, and static bearer authentication when enabled. A production deployment must still set its real HTTPS MCP_PUBLIC_URL and exact allowlists, protect secrets, and provide appropriate rate limiting and audit controls.

Notice

This repo works in two ways:

• As a fetch-native Bun server for local workflows
• As a fetch-native 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)

1. Local Development — Standard setup with bearer token auth
2. Cloudflare Worker (wrangler dev) — Local Worker testing
3. Cloudflare Worker (deploy) — Remote production

---

1. Local Development — Quick Start

1. Get Tessie credentials:

   • Visit developer.tessie.com
   • Go to Developer Settings → Generate Access Token
   • Copy your access token
   • Note your vehicle’s VIN

2. Configure environment:

cd tesla-mcp
bun install
cp .env.example .env

Edit .env:

PORT=3000
AUTH_ENABLED=true
AUTH_STRATEGY=bearer

# Generate with: openssl rand -hex 32
BEARER_TOKEN=your-random-auth-token

# Tessie credentials