English Français العربية

ai.smithery/keithah-tessie-mcp

Official registry Archived Other

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

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http keithah-tessie-mcp 'https://server.smithery.ai/@keithah/tessie-mcp/mcp' --header 'Authorization: <Bearer token for Smithery authentication>'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "keithah-tessie-mcp": {
            "type": "http",
            "url": "https://server.smithery.ai/@keithah/tessie-mcp/mcp",
            "headers": {
                "Authorization": "<Bearer token for Smithery authentication>"
            }
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Tessie MCP
  2. Setup
  3. Tools
  4. Remote access
  5. Smoke check

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.

Frequently asked questions

What is ai.smithery/keithah-tessie-mcp?

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

How do I install ai.smithery/keithah-tessie-mcp?

It runs as a remote server. In Claude Code: claude mcp add --transport http keithah-tessie-mcp 'https://server.smithery.ai/@keithah/tessie-mcp/mcp' --header 'Authorization: <Bearer token for Smithery authentication>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does ai.smithery/keithah-tessie-mcp need an API key?

Yes. It expects Authorization, which you set in its configuration.

Is ai.smithery/keithah-tessie-mcp open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains ai.smithery/keithah-tessie-mcp?

It is published by keithah. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.