TeslaMate MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_ADMIN_AUTH_KEY | No | Optional security key for mutating operations | |
| TESLAMATE_BASE_URL | No | Base URL of the TeslaMate instance | http://127.0.0.1:4000 |
| TESLAMATE_AUTH_MODE | Yes | Authentication mode to use | |
| TESLAMATE_BEARER_TOKEN | No | Bearer token for bearer authentication | |
| TESLAMATE_BASIC_PASSWORD | No | Password for basic authentication | |
| TESLAMATE_BASIC_USERNAME | No | Username for basic authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| teslamate_connection_infoA | Return TeslaMate MCP server and target TeslaMate instance connection details. |
| teslamate_scope_infoC | Return user scoping metadata used to resolve the TeslaMate target connection. |
| teslamate_list_endpointsA | List documented/implemented TeslaMate HTTP endpoints exposed by this MCP server. |
| teslamate_query_suggestionC | Recommend the best TeslaMate MCP tools for a query and optionally return schema discovery for all tools. |
| teslamate_health_checkC | Call TeslaMate health check endpoint. |
| teslamate_suspend_loggingC | Suspend logging for a TeslaMate car id via PUT /api/car/:id/logging/suspend. |
| teslamate_resume_loggingC | Resume logging for a TeslaMate car id via PUT /api/car/:id/logging/resume. |
| teslamate_get_drive_gpxC | Fetch a drive GPX export by id from GET /drive/:id/gpx. |
| teslamate_api_requestC | Generic TeslaMate HTTP API call. Supports all available TeslaMate endpoints while enforcing host/auth safeguards. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.