What is MCP?
The Model Context Protocol is an open standard for connecting AI assistants to external systems. Instead of an assistant being boxed into its own chat window, MCP lets it call "tools" published by a server — read a calendar, query a database, or, in this case, talk to a car. The assistant sees a catalog of available actions and chooses the right one based on what you asked.
Why an MCP server for Tesla
Tesla publishes a powerful Fleet API, but it’s built for developers: OAuth flows, signed vehicle commands, token refresh, strict rate limits. An MCP server like mytesla.io does that plumbing once and hands your AI a clean, safe set of actions. You get natural-language control; the server handles authentication, command signing, retries, and limits.
What the server exposes
mytesla.io’s MCP server publishes the car’s remote functions as discrete tools, grouped roughly like this:
- Status & reads — vehicle status (battery, range, location, climate, doors), list vehicles, credit balance.
- Charging — set charge limit, set charging amps, start/stop charging, scheduled charging and departure, open/close the charge port.
- Climate — start/stop climate, set cabin temperature, seat heaters and coolers, steering-wheel heater, max defrost, cabin-overheat protection, climate-keeper modes.
- Security & body — lock/unlock, flash lights, honk, actuate the trunk or frunk, control windows, Sentry mode.
- Navigation — share a destination to the car’s nav, wake the vehicle.
The assistant only ever sees these defined actions — it can’t do anything Tesla’s API doesn’t allow.
Supported clients
Any client that speaks Streamable HTTP MCP with OAuth 2.1: Claude Desktop, Claude.ai (web), ChatGPT (Pro/Team/Enterprise/Edu with Developer Mode), Cursor, VS Code, and Claude Code. That’s essentially every MCP-aware assistant on the market today.
How to connect
For most assistants you paste the MCP URL from your mytesla.io dashboard into the app’s "custom connector" field and approve the OAuth popup. Command-line users can wire it in one line:
claude mcp add --transport http mytesla https://mcp.mytesla.io/mcp
Step-by-step guides per assistant: Claude and ChatGPT.
Security and the Fleet API
mytesla.io is an authorized Tesla Fleet API client; your car’s OAuth grant appears as "Embay, LLC" in your Tesla Account, where you can revoke it anytime. The server doesn’t store location, drive, or charge history — data is fetched per request and not retained beyond aggregate usage counts — and it never trains models on your data. Vehicle commands are signed per Tesla’s Vehicle Command Protocol.
Connect your AI to Tesla’s API — without the plumbing
mytesla.io is the MCP server that does OAuth, command signing, and rate limits for you. Paste one URL and go.
Frequently asked questions
Is there a free Tesla MCP server?
Running your own against Tesla’s Fleet API is possible but means handling OAuth, command signing, and rate limits yourself, plus Tesla’s API access costs. mytesla.io handles all of that for $4.99/month.
What’s the MCP URL?
You get a personal MCP endpoint from your mytesla.io dashboard after signing up and authorizing your car. The base is https://mcp.mytesla.io/mcp.