TeslaMate MCP Server
Related Servers
Alternatives to TeslaMate MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA Model Context Protocol server for the TeslaFi API that lets MCP clients query live vehicle data, drive and charge history, commute patterns, and optionally send commands.2MIT
- AlicenseBqualityDmaintenanceMCP server combining TeslaMate historical analytics with Fleet API live data and commands. Works with Claude Code, Claude Desktop, Cursor, and any MCP-compatible client.292MIT
- AlicenseNot gradedqualityCmaintenanceComprehensive development tools for Home Assistant, enabling file management, template testing, entity/state management, service calls, log access, and system information retrieval through MCP.MIT
- AlicenseCqualityAmaintenanceEnables reading Tesla vehicle data from a TeslaMate PostgreSQL database, including status, trips, charging, efficiency, weather integration, and more, via 38 tools for MCP-compatible clients like Claude Code.38MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to query homelab infrastructure such as Proxmox VE, NetBox, systemd services, Grafana, InfluxDB, AdGuard Home, ping logs, and configured HTTP JSON endpoints through read-only tools.AGPL 3.0
- FlicenseNot gradedqualityBmaintenanceExposes Garmin Connect health and activity data (steps, sleep, heart rate, etc.) via MCP tools, with built-in login and MFA support.-
TDQS
Scored across 9 tools
All tools have distinct purposes. Even suspend/resume logging are clearly opposite actions. The generic api_request is distinct from the specialized tools. No ambiguity.
All tools follow the consistent pattern 'teslamate_verb_noun' (e.g., teslamate_health_check, teslamate_suspend_logging). The prefix and structure are uniform.
9 tools cover the core functionalities of a TeslaMate integration: connection, health, logging control, drive export, and a generic API. The count is well-scoped and not excessive.
The set includes essential operations and a generic api_request to cover any missing endpoints. However, dedicated tools for common queries like charge data or updates are absent, though the generic tool mitigates this.