Keithah Tessie Mcp

ai.smitheryPublished by smithery.aiOfficial publisherv1.1.1Updated Oct 24, 2026

Unofficial integration! ## ✨ Key Features ### 💰 Financial Intelligence - **Smart Charging Cost An…

The publisher's own server: 222wcnm Bilistalkermcp

VerifiedStreamable HTTPWeb executableLocation & LifestyleFinance

Overview

AI-generated overview

Unofficial Tessie integration that lets an assistant list Tesla vehicles, analyze driving history and send vehicle commands through a self-hosted MCP server.

What you can do
List and select vehicles, with a chosen VIN persisted as the default for later calls (list_vehicles, get_vehicle). Analyze driving history over a default 90-day window, including autopilot telemetry (analyze_history). Retrieve the driving path for a trip (get_driving_path). Send commands to a vehicle (vehicle_command).
When to use it
For a single owner who wants an AI assistant to inspect their own Tesla data through Tessie and issue vehicle commands, and who is comfortable running a small self-hosted Docker service behind a bearer token.
Requirements
A self-hosted deployment: Docker Compose, a Tessie access token in TESSIE_API_KEY, and a generated MCP_AUTH_TOKEN. Clients connect to the /mcp endpoint with an Authorization bearer header. Optional Cloudflare tunnel via TUNNEL_TOKEN for remote access.
Before you install
The repository is archived and an official Tessie MCP server now exists. vehicle_command can act on a real vehicle, so commands carry physical consequences. The Tessie token and MCP_AUTH_TOKEN are secrets; the bearer token is required even behind Cloudflare. Autopilot values do not uniquely prove FSD usage.

Installation

In SourceWeft

  1. Open Keithah Tessie Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.smithery%2Fkeithah-tessie-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "keithah-tessie": {
      "type": "http",
      "url": "https://server.smithery.ai/@keithah/tessie-mcp/mcp"
    }
  }
}

README

Tessie MCP

[!NOTE] This repository is archived. Tessie now publishes an official MCP server. See the Tessie MCP reference documentation.

Personal, self-hosted MCP access to Tessie. It is a Streamable HTTP server at /mcp, designed for one owner and protected by a static bearer token.

Setup

  1. Generate a Tessie access token at https://dash.tessie.com/settings/api.
  2. Create .env from .env.example and generate MCP_AUTH_TOKEN with openssl rand -base64 48.
  3. Start the service: docker compose up -d --build.
  4. Configure an MCP client with URL http://127.0.0.1:3000/mcp and header Authorization: Bearer <MCP_AUTH_TOKEN>.

TESSIE_API_KEY never leaves the server. Passing vin to get_vehicle selects and persists the default vehicle; later calls can omit it.

Tools

list_vehicles, get_vehicle, analyze_history, get_driving_path, and vehicle_command. History analysis defaults to 90 days. Autopilot/FSD values are Tessie's native autopilot_distance and historical autopilot telemetry; they do not uniquely prove FSD usage.

Remote access

For a temporary URL without a tunnel token, run the app locally then execute cloudflared tunnel --url http://127.0.0.1:3000. For a stable named tunnel, set TUNNEL_TOKEN in .env and run docker compose -f docker-compose.yml -f docker-compose.tunnel.yml up -d.

The app bearer token remains required even behind Cloudflare.

Nginx

Use examples/nginx.conf; preserve the Authorization header, disable buffering, and use long timeouts.

Caddy

Use examples/Caddyfile; it forwards headers and supports streaming by default.

Smoke check

curl http://127.0.0.1:3000/healthz verifies liveness. The server has no command-line operation that invokes vehicle commands.

Source: README.md at commit 3ef4da4

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.1LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Smithery integrations