TeslaMate MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTH_TOKEN | No | Bearer token for authentication (optional) | |
| DATABASE_URL | Yes | PostgreSQL connection string for your TeslaMate database |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_all_charging_sessions_summaryA | Get the summary of all charging sessions for each car. |
| get_average_efficiency_by_temperatureB | Get the average efficiency by temperature for each car. |
| get_basic_car_informationB | Get the basic car information for each car. |
| get_battery_degradation_over_timeA | Get the battery degradation over time for each car. |
| get_battery_health_summaryA | Get the battery health summary for each car. |
| get_charging_by_locationC | Get the charging by location for each car. |
| get_current_car_statusB | Get the current car status for each car. |
| get_daily_battery_usage_patternsA | Get the daily battery usage patterns for each car. |
| get_daily_driving_patternsB | Get the daily driving patterns for each car. |
| get_drive_summary_per_dayA | Get the drive summary per day for each car. |
| get_efficiency_by_month_and_temperatureA | Get the efficiency by month and temperature for each car. |
| get_longest_drives_by_distanceB | Get the longest drives by distance for each car. |
| get_monthly_driving_summaryA | Get the monthly driving summary for each car. |
| get_most_visited_locationsA | Get the most visited locations for each car. |
| get_software_update_historyA | Get the software update history for each car. |
| get_tire_pressure_weekly_trendsA | Get the tire pressure weekly trends for each car. |
| get_total_distance_and_efficiencyA | Get the total distance and efficiency for each car. |
| get_unusual_power_consumptionB | Get the unusual power consumption for each car. |
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 18 tools
Each tool targets a specific metric or report (charging, efficiency, battery, driving, locations, etc.), and the descriptions are clear. However, a few tools like get_daily_driving_patterns and get_drive_summary_per_day could seem overlapping at first glance, though they cover different time granularities and aspects.
All 18 tools follow a strict get_<metric> naming convention with no deviations. The pattern is uniform and predictable, making it easy to understand the tool set at a glance.
With 18 tools, the server is slightly above the typical 3-15 range, but the count is justified by the breadth of Tesla telemetry data covered. Each tool provides a distinct report, and there are no obvious redundant tools.
The server covers a wide range of analytics and summarization reports for vehicle data. As a read-only reporting server, it lacks action-based tools, which is acceptable. Some minor gaps exist, such as raw individual charging/driving sessions, but comprehensive summaries and trends are provided.