In-depth architectural comparison of the Teslamate MCP and MCP Teslamate Fleet MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Teslamate MCP
Travel & Transportation · Local stdio
Quality: 51/100 (Good) | Auth: other
MCP Teslamate Fleet
Travel & Transportation · Local stdio
Quality: 47/100 (Fair) | Auth: OAuth 2.0
Verdict Summary: Choose Teslamate MCP if you need specialized Travel & Transportation tools running via a local process. Choose MCP Teslamate Fleet if your workspace requires Travel & Transportation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Teslamate MCP when:
You need dedicated capabilities in the Travel & Transportation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: DATABASE_URL, AUTH_TOKEN.
Primary tools included: 35 TeslaMate analytics and search tools, Read-only custom SQL execution, Live database schema introspection.
A Model Context Protocol (MCP) server that provides access to your TeslaMate database, allowing AI assistants to query Tesla vehicle data and analytics.
Combined TeslaMate analytics + Fleet API commands — 29 tools for vehicle telemetry, driving history, energy analytics, and remote control (climate, charging, locks, sentry).
Category & Scope
Tools & Capabilities Breakdown
Teslamate MCP Tools (6)
35 TeslaMate analytics and search tools
Read-only custom SQL execution
Live database schema introspection
Filterable vehicle and time-range reports
Three optional SVG chart tools
Local stdio and remote streamable HTTP modes
MCP Teslamate Fleet Tools (6)
29 tools across TeslaMate and Fleet API backends
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Teslamate MCP is categorized under Travel & Transportation and uses a local stdio subprocess. In contrast, MCP Teslamate Fleet belongs to Travel & Transportation using local stdio subprocess. Select Teslamate MCP when you need capabilities focused on travel & transportation and MCP Teslamate Fleet when you require tools for travel & transportation.
Primary tools included: 29 tools across TeslaMate and Fleet API backends, Driving, charging, location, and vehicle-state history, Energy, efficiency, savings, and trip-cost analytics.