Verified

Teslafi MCP Server

TeslaFi vehicle data and command integration for your local AI client.

Data last scanned today · Reviewed today

8 1 dangerous tool7 tools★ 2TypeScriptMIT

Overview

TeslaFi MCP Server allows your AI to query live vehicle data, driving history, and charging statistics directly from your TeslaFi account. It enables complex data analysis, such as generating expense reports, comparing monthly energy consumption, and identifying frequently visited locations by processing your historical telematics.

Our verdict

This server carries a high risk level with a security score of 33/100. It is a community-maintained project that has not undergone editorial review, and critical aspects such as the authentication implementation remain unverified. Given the ability to execute vehicle commands upon user opt-in, only users who are comfortable with the risks of third-party, unvetted integrations should proceed with installation.

Supports granular historical data analysis like commute patterns
Provides optional command capabilities including climate control
Contains only three direct dependencies
Includes well-documented tool definitions in the README

Low security score of 33/100
Single-contributor project increases bus-factor risk
Authentication method has not been independently reviewed

Setup

Claude Desktop

{
  "mcpServers": {
    "teslafi-mcp": {
      "args": [
        "-y",
        "teslafi-mcp"
      ],
      "command": "npx"
    }
  }
}

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.

No read-only mode — running this grants full read/write access.
No built-in authentication — anyone with access to this config can invoke every tool it exposes.

Tools

Tool	Description	Risk
tesla_get_current_data	Live / last-known vehicle data (state, battery, range, charging, location).	low
tesla_get_drives	Stored drive history, with optional date-range filtering.	low
tesla_get_charges	Stored charge sessions, with optional date-range filtering.	low
tesla_get_trips_for_month	All drives in a given calendar month, normalized.	low
tesla_analyze_home_work_trips	Count home-to-work and work-to-home commutes in a month.	low
tesla_get_locations	Unique locations and visit counts derived from drive history.	low
tesla_send_command	Send a vehicle control command.	high

Compatibility

Client	Local	Docker	Remote	Read-only
ChatGPT
Claude Desktop
Cursor
VS Code
Windsurf

Frequently asked questions

›Are vehicle control commands enabled by default?

No, sending vehicle commands via the `tesla_send_command` tool is disabled by default and requires an explicit opt-in.

›How can I set a default unit system for my queries?

You can set a default system by using the `TESLAFI_UNITS` environment variable, which accepts 'metric' or 'imperial'.

›Does the server automatically wake my car to perform commands?

No, a standard command will not wake a sleeping car. You must explicitly request a wake action or provide specific parameters like `wake_seconds` to wake the vehicle.

›How does the server determine which unit system to use if I don't provide one?

The server checks for the `units` tool argument, then the `TESLAFI_UNITS` environment variable, then your TeslaFi account preferences, and finally defaults to metric.

›Does the server have access to my OS locale settings?

No, the operating system locale is not visible to the server.