teslamate-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTH_TOKEN | No | Optional bearer token for securing your remote MCP server | |
| 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_all_charging_sessions_summaryB | Get the summary of all charging sessions for each car. Returns charging statistics including total sessions, energy consumed, and costs. |
| get_average_efficiency_by_temperatureB | Get the average efficiency by temperature for each car. Helps understand how temperature affects vehicle efficiency. |
| get_basic_car_informationB | Get the basic car information for each car. Returns VIN, model, firmware version, and other vehicle details. |
| get_battery_degradation_over_timeB | Get the battery degradation over time for each car. Tracks battery health metrics and capacity changes. |
| get_battery_health_summaryB | Get the battery health summary for each car. Provides current battery health status and statistics. |
| get_charging_by_locationB | Get the charging by location for each car. Shows charging patterns and statistics grouped by location. |
| get_current_car_statusB | Get the current car status for each car. Returns real-time vehicle status including location, battery level, and state. |
| get_daily_battery_usage_patternsB | Get the daily battery usage patterns for each car. Analyzes battery consumption patterns throughout the day. |
| get_daily_driving_patternsB | Get the daily driving patterns for each car. Shows driving habits and patterns by day of week and time. |
| get_drive_summary_per_dayB | Get the drive summary per day for each car. Provides daily driving statistics including distance, duration, and efficiency. |
| get_efficiency_by_month_and_temperatureB | Get the efficiency by month and temperature for each car. Analyzes how seasonal temperature changes affect vehicle efficiency. |
| get_longest_drives_by_distanceB | Get the longest drives by distance for each car. Lists the longest trips taken with details about distance and duration. |
| get_monthly_driving_summaryB | Get the monthly driving summary for each car. Provides monthly statistics for distance, energy usage, and costs. |
| get_most_visited_locationsB | Get the most visited locations for each car. Shows frequently visited places with visit counts and durations. |
| get_software_update_historyB | Get the software update history for each car. Tracks firmware updates and version changes over time. |
| get_tire_pressure_weekly_trendsB | Get the tire pressure weekly trends for each car. Monitors tire pressure changes and patterns by week. |
| get_total_distance_and_efficiencyB | Get the total distance and efficiency for each car. Provides lifetime statistics for distance traveled and energy efficiency. |
| get_unusual_power_consumptionB | Get the unusual power consumption for each car. Identifies anomalies in power usage that might indicate issues. |
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
Most tools have distinct purposes focusing on different aspects of Tesla vehicle data (charging, driving, battery, efficiency, locations, etc.), though some like 'get_battery_degradation_over_time' and 'get_battery_health_summary' could potentially overlap in scope, and 'get_daily_driving_patterns' and 'get_drive_summary_per_day' might be confused for similar daily analyses. Descriptions help clarify, but there is minor ambiguity in a few cases.
All tool names follow a consistent 'get_' prefix with descriptive snake_case nouns, such as 'get_all_charging_sessions_summary' and 'get_current_car_status'. This uniform pattern makes the tool set predictable and easy to navigate, with no deviations in naming conventions.
With 18 tools, the count is slightly high but reasonable for a comprehensive Tesla data analytics server, covering various metrics like charging, driving, battery, and efficiency. It might feel a bit heavy, but each tool appears to serve a specific purpose within the domain, avoiding redundancy.
The tool set provides extensive coverage for analyzing Tesla vehicle data, including real-time status, historical trends, charging patterns, driving habits, battery health, efficiency metrics, and anomaly detection. There are no obvious gaps; it supports a full lifecycle of data retrieval and analysis without dead ends for the stated purpose.