Mcp Tesla
Query Tesla vehicle and charging data through MCP for personal dashboards, automations, or ops-style alerts alongside your other agent tools.
Overview
io.github.jlestel/mcp-tesla is an Operate-phase MCP server that wraps Tesla Fleet and TeslaMate APIs for agent-driven vehicle and charging monitoring.
What is this MCP server?
- MCP server wrapping Tesla Fleet API and TeslaMate API (v1.0.0)
- Hosted remote endpoint: streamable-http at https://mcp.myteslamate.com/mcp
- Enables agent questions about charge state, trips, and fleet data without custom scripts
- GitHub source: MyTeslaMate/mcp-tesla
- Niche personal infra bridge rather than a general SaaS builder toolkit
- Server version 1.0.0
- 1 remote transport: streamable-http at mcp.myteslamate.com
- Wraps 2 API surfaces: Tesla Fleet API and TeslaMate API
Community signal: 2 GitHub stars.
What problem does it solve?
Tesla and TeslaMate data sit behind separate APIs, so agents cannot answer status questions without bespoke scripts you maintain.
Who is it for?
Solo builders running TeslaMate or Fleet API who want agent-assisted monitoring, automations, and personal ops dashboards.
Skip if: Teams building a generic SaaS without Tesla ownership, or anyone who cannot manage OAuth, tokens, and location-sensitive data responsibly.
What do I get? / Deliverables
After you connect the remote MCP endpoint, your agent can query fleet and TeslaMate-backed metrics through standardized tools.
- Agent-accessible Tesla and TeslaMate API operations
- Remote MCP endpoint without local stdio packaging
Recommended MCP Servers
Journey fit
Fleet and TeslaMate telemetry is most aligned with Operate when you monitor real-world device state, trips, and charging—not with greenfield app UI work. Monitoring fits because the server wraps Tesla Fleet API and TeslaMate API for live status and historical vehicle metrics.
How it compares
Vehicle telemetry MCP remote, not a cross-platform IoT skill or generic cloud monitoring template.
Common Questions / FAQ
Who is mcp-tesla for?
Tesla owners and hackers using TeslaMate or Fleet API who want MCP access from Claude Code, Cursor, or other streamable-http clients.
When should I use mcp-tesla?
Use it in Operate when monitoring charge state, drive history, or fleet health and you prefer agent queries over one-off API scripts.
How do I add mcp-tesla to my agent?
Register the remote MCP URL https://mcp.myteslamate.com/mcp (streamable-http) per your client docs and complete Tesla/TeslaMate auth on the provider side.