mcpField
K
keithah-tessie-mcp

keithah-tessie-mcp

Remote
github.com/keithahMaps & Travel9Updated 2w ago
Repository

About keithah-tessie-mcp

Tessie MCP is an archived, self-hosted MCP server for one Tessie account, intended for access to vehicle data and commands. It uses Streamable HTTP and a static bearer token; the repository notes that Tessie now offers an official MCP server.

Key features

  1. 01List and select vehicles
  2. 02Retrieve vehicle details
  3. 03Analyze driving history
  4. 04Get driving paths
  5. 05Send vehicle commands

Use cases

  1. 01Review vehicle history
  2. 02Inspect a vehicle's driving path
  3. 03Run vehicle commands through an MCP client

MCP support

It exposes vehicle, history, driving-path, and command tools over Streamable HTTP at `/mcp`. MCP clients authenticate with a static bearer token.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://server.smithery.ai/@keithah/tessie-mcp/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://server.smithery.ai/@keithah/tessie-mcp/mcpAuth required

Tools

Details

From the project 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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.