Tessie

You run an MCP server that wraps the Tessie API to let LLM clients query and control a Tesla through focused, efficient endpoints. It uses VIN-based vehicle identification for reliability and exposes both telemetry and real-time control actions you can invoke from MCP clients.

How to use

You connect to the Tessie MCP server from your MCP client to retrieve focused telemetry data and perform safe, live controls on your vehicle. Use the new specialized telemetry endpoints to fetch battery info, health, location, tire pressures, and vehicle status, while still benefiting from legacy telemetry if you need the full vehicle state. You can trigger live actions like honking the horn or flashing lights. Authentication is VIN-based and relies on your Tessie API token.

Typical usage patterns include starting the server, configuring your credentials, and then querying endpoints or invoking control actions from your MCP client. For example, you will supply your Tessie token and VIN, and then request the latest battery or location information, or issue a honk or flash action as needed.

How to install

python -m venv venv
source venv/bin/activate  # On Windows: venv\Scripts\activate
pip install -r requirements.txt

# Configure environment
cp .env.example .env

Edit the environment file to set your Tessie API token, vehicle VIN, and telemetry interval.

TESSIE_TOKEN=your_tessie_api_token_here
VEHICLE_VIN=5YJ3E1EA1KF123456  # Your Tesla VIN
TELEMETRY_INTERVAL=5           # minutes; use 'realtime' to skip caching

Run the server using the standard entrypoint. The default transport is STDIO.

python -m src.server

If you want to expose the server remotely for network clients, run it in SSE mode on your host.

python -m src.server --transport sse --host 0.0.0.0 --port 8000

Configuration and notes

Key configuration points include enabling VIN-based vehicle identification, setting a Tessie API token, and choosing a telemetry interval. The server exposes new specialized endpoints for battery, battery health, location, tire pressures, and vehicle status, while preserving access to legacy telemetry tools. Control actions such as honk_horn and flash_lights are live and execute real commands on your Tesla.

Environment variables you configure in the .env file are respected by the server for authentication, caching behavior, and VIN lookup.

Security and stability notes

VIN-based identification improves reliability when multiple vehicles are in use. Ensure your Tessie API token is kept secret and rotate tokens as needed. Be aware that some control actions trigger real vehicle behavior; exercise caution and test in a safe environment.

Troubleshooting

If the server fails to start, verify that Python is installed, the virtual environment is activated, and dependencies installed successfully. Confirm that the Tessie API token and VIN are set in the environment file and correct. Check that the Tessie service is reachable with the provided token.

Available tools

get_battery_information

Fetch battery level, drain, energy, voltage, current, and temperature for efficient battery monitoring.

get_battery_health_information

Retrieve battery capacity and maximum range estimates.

get_location_information

Query GPS coordinates with an address/location context.

get_tire_pressure_information

Return tire pressures with status for all tires.

get_vehicle_status

Check sleep/wake status of the vehicle.

honk_horn

Trigger the vehicle horn for a real in-vehicle honk action.

flash_lights

Trigger the vehicle lights to flash as a real action.