Keithah Tessie Mcp
Monitor Tesla vehicles via Tessie—charging costs, session analytics, and fleet-style signals—from your agent for ops-minded owners and side projects.
Overview
ai.smithery/keithah-tessie-mcp is an Operate-phase MCP server that monitors Tesla data and charging cost intelligence through Tessie for agents.
What is this MCP server?
- Unofficial Tessie integration with financial intelligence around smart charging cost analysis
- Exposes vehicle and charging workflows agents can use for personal ops or niche SaaS experiments
- Smithery streamable-HTTP remote; source at github.com/keithah/tessie-mcp
- Catalog version 1.1.1 on MCP schema 2025-09-29
- Bearer smithery_api_key authentication on the hosted remote
- Version 1.1.1; GitHub source keithah/tessie-mcp
- One streamable-HTTP Smithery remote with Bearer auth
- README advertises smart charging cost analysis under financial intelligence features
Community signal: 6 GitHub stars.
What problem does it solve?
EV owners want charging cost insight and vehicle status in the same agent session as their automation code, without exporting CSVs from Tessie manually.
Who is it for?
Technical Tesla drivers using Tessie who build personal monitoring scripts, cost reports, or small EV-focused utilities with an agent.
Skip if: Non-Tessie users, buyers needing OEM-official Tesla support, or safety-critical vehicle control without human verification.
What do I get? / Deliverables
After setup, your agent can query Tessie-backed vehicle and charging analytics so you monitor costs and sessions from Claude Code or Cursor.
- Smithery-connected Tessie MCP remote in your agent
- Agent-queryable charging and vehicle intelligence workflows
- Baseline for personal cost dashboards or EV ops automations you extend in code
Recommended MCP Servers
Journey fit
Operate fits ongoing vehicle and energy monitoring after the car and Tessie account are already in production daily use. Monitoring matches Tessie’s charging intelligence and vehicle state reads rather than one-time setup or marketing.
How it compares
Unofficial Tessie telemetry MCP, not a Tesla OEM skill or a generic OBD diagnostic bundle.
Common Questions / FAQ
Who is ai.smithery/keithah-tessie-mcp for?
Solo builders and Tessie subscribers who want MCP access to Tesla charging analytics and vehicle-oriented Tessie features from their coding agent.
When should I use ai.smithery/keithah-tessie-mcp?
Use it in Operate when you routinely monitor charging costs, sessions, or vehicle state and want those answers inside agent-driven workflows.
How do I add ai.smithery/keithah-tessie-mcp to my agent?
Register the Smithery remote @keithah/tessie-mcp with streamable HTTP and set Authorization to Bearer your smithery_api_key.