MCP Server

MCP MCP server exists for a simple reason — assistants are far more useful when they can act on MCP directly instead of describing what you should do. MCP server wrapping the Tesla Fleet API and TeslaMate API.

What you get

This repository provides a Model Context Protocol server that wraps both the Tesla Fleet API and the TeslaMate API. It includes vehicle endpoints, vehicle commands, energy endpoints (Powerwall/Solar), and charging endpoints. The implementation is modular and fully featured, exposing 98 MCP tools for the Tesla Fleet API and 9 MCP tools for the TeslaMate API.

• Modular package under tesla_mcp with a reusable TeslaClient
• Vehicle endpoints — (29 read-only endpoints):
• Core Vehicle Info —
• GET /api/1/vehicles - List vehicles
• GET /api/1/vehicles/{vehicle_tag} - Get vehicle metadata
• GET /api/1/vehicles/{vehicle_tag}/vehicle_data - Get live vehicle data

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration and credentials

You will need 3 environment variables: TESLA_BASE_URL, YOUR_MYTESLAMATE_TOKEN, YOUR_TESLA_FLEET_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by jlestel; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.