TeslaMate MCP Server
Allows querying Tesla vehicle data and analytics from a TeslaMate database, including driving statistics, charging history, battery health, efficiency metrics, and location analytics.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@TeslaMate MCP Server what's my current battery level and range?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
TeslaMate MCP Server
A Model Context Protocol (MCP) server that provides access to your TeslaMate database, allowing AI assistants to query Tesla vehicle data and analytics.

Overview
This MCP server connects to your TeslaMate PostgreSQL database and exposes various tools to retrieve Tesla vehicle information, driving statistics, charging data, battery health, efficiency metrics, and location analytics. It's designed to work with MCP-compatible AI assistants like Claude Desktop, enabling natural language queries about your Tesla data.
Related MCP server: PostgreSQL MCP Server
Prerequisites
TeslaMate running with a PostgreSQL database
Python 3.11 or higher
Access to your TeslaMate database
Installation
Option 1: Local Installation
Clone this repository:
git clone https://github.com/yourusername/teslamate-mcp.git cd teslamate-mcpInstall dependencies using uv (recommended):
uv syncOr using pip:
pip install -r requirements.txtCreate a
.envfile in the project root:DATABASE_URL=postgresql://username:password@hostname:port/teslamate
Option 2: Docker Deployment (Remote Access)
For remote deployment using Docker. Quick start:
# Clone and navigate to the repository
git clone https://github.com/yourusername/teslamate-mcp.git
cd teslamate-mcp
# Run the deployment script
./deploy.sh deploy
# Or manually:
cp env.example .env
# Edit .env with your database credentials
docker-compose up -dThe remote server will be available at:
Streamable HTTP:
http://localhost:8888/mcp
Configuring Authentication (Optional)
To secure your remote MCP server with bearer token authentication:
Set a bearer token in your
.envfile:AUTH_TOKEN=your-secret-bearer-token-hereGenerate a secure token:
# Use the provided token generator python3 generate_token.py # Or generate manually with openssl openssl rand -base64 32 # Or use any other method to create a secure random stringWhen connecting from MCP clients, include the Authorization header:
{ "mcpServers": { "teslamate-remote": { "url": "http://your-server:8888/mcp", "transport": "streamable_http", "headers": { "Authorization": "Bearer your-secret-bearer-token-here" } } } }Or use curl for testing:
curl -H "Authorization: Bearer your-secret-bearer-token-here" \ http://localhost:8888/mcp
Security Considerations
Use HTTPS in production: Bearer tokens are sent in plain text. Always use HTTPS/TLS in production environments.
Strong tokens: Use long, random tokens (at least 32 characters).
Environment variables: Never commit tokens to version control. Use environment variables or secrets management.
Network security: Consider using a VPN or restricting access by IP address for additional security.
Token rotation: Regularly rotate your bearer tokens.
Available Tools
The MCP server provides 20 tools for querying your TeslaMate data:
Pre-defined Query Tools
get_basic_car_information- Basic vehicle details (VIN, model, name, color, etc.)get_current_car_status- Current state, location, battery level, and temperatureget_software_update_history- Timeline of software updatesget_battery_health_summary- Battery degradation and health metricsget_battery_degradation_over_time- Historical battery capacity trendsget_daily_battery_usage_patterns- Daily battery consumption patternsget_tire_pressure_weekly_trends- Tire pressure history and trendsget_monthly_driving_summary- Monthly distance, efficiency, and driving timeget_daily_driving_patterns- Daily driving habits and patternsget_longest_drives_by_distance- Top drives by distance with detailsget_total_distance_and_efficiency- Overall driving statisticsget_drive_summary_per_day- Daily drive summariesget_efficiency_by_month_and_temperature- Efficiency analysis by temperatureget_average_efficiency_by_temperature- Temperature impact on efficiencyget_unusual_power_consumption- Anomalous power usage detectionget_charging_by_location- Charging statistics by locationget_all_charging_sessions_summary- Complete charging history summaryget_most_visited_locations- Frequently visited places
Custom Query Tools
get_database_schema- Returns complete database schema (tables, columns, data types)run_sql- Execute custom SELECT queries with safety validationOnly SELECT statements allowed
Prevents DROP, CREATE, INSERT, UPDATE, DELETE, ALTER, etc.
Blocks multiple statement execution
Safely handles strings and comments
Configuration
Environment Variables
DATABASE_URL: PostgreSQL connection string for your TeslaMate database
MCP Client Configuration
To use this server with Claude Desktop, add the following to your MCP configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Local Configuration (stdio transport)
{
"mcpServers": {
"teslamate": {
"command": "uv",
"args": ["run", "python", "/path/to/teslamate-mcp/main.py"],
"env": {
"DATABASE_URL": "postgresql://username:password@hostname:port/teslamate"
}
}
}
}Remote Configuration (streamable HTTP transport)
For connecting to a remote server:
{
"mcpServers": {
"TeslaMate": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"http://your-private-server:8888/mcp",
"--allow-http"
]
}
}
}With authentication enabled:
{
"mcpServers": {
"TeslaMate": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"http://your-private-server:8888/mcp",
"--allow-http",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer <secret bearer token>"
}
}
}
}Usage
Running the Server (STDIO)
uv run python main.pyExample Queries
Once configured with an MCP client, you can ask natural language questions organized by category:
Basic Vehicle Information
"What's my Tesla's basic information?"
"Show me my current car status"
"What software updates has my Tesla received?"
Battery and Health
"How is my battery health?"
"Show me battery degradation over time"
"What are my daily battery usage patterns?"
"How are my tire pressures trending?"
Driving Analytics
"Show me my monthly driving summary"
"What are my daily driving patterns?"
"What are my longest drives by distance?"
"What's my total distance driven and efficiency?"
Efficiency Analysis
"How does temperature affect my efficiency?"
"Show me efficiency trends by month and temperature"
"Are there any unusual power consumption patterns?"
Charging and Location Data
"Where do I charge most frequently?"
"Show me all my charging sessions summary"
"What are my most visited locations?"
Custom SQL Queries
"Show me the database schema"
"Run a SQL query to find drives longer than 100km"
"Query the average charging power by location"
"Find all charging sessions at superchargers"
Note: The run_sql tool only allows SELECT queries. All data modification operations (INSERT, UPDATE, DELETE, DROP, etc.) are strictly forbidden for safety.
Adding New Queries
Create a new SQL file in the
queries/directoryAdd a corresponding tool function in
main.pyFollow the existing pattern for error handling and database connections
License
This project is licensed under the MIT License - see the LICENSE file for details.
Acknowledgments
TeslaMate - Tesla data logging software
Model Context Protocol - Protocol for AI-tool integration
For bugs and feature requests, please open an issue on GitHub.
Available Tools
18 toolsget_all_charging_sessions_summaryA
Get the summary of all charging sessions for each car.
Inputs: no named parameters. Returns: result
get_average_efficiency_by_temperatureB
Get the average efficiency by temperature for each car.
Inputs: no named parameters. Returns: result
get_basic_car_informationB
Get the basic car information for each car.
Inputs: no named parameters. Returns: result
get_battery_degradation_over_timeA
Get the battery degradation over time for each car.
Inputs: no named parameters. Returns: result
get_battery_health_summaryA
Get the battery health summary for each car.
Inputs: no named parameters. Returns: result
get_charging_by_locationC
Get the charging by location for each car.
Inputs: no named parameters. Returns: result
get_current_car_statusB
Get the current car status for each car.
Inputs: no named parameters. Returns: result
get_daily_battery_usage_patternsA
Get the daily battery usage patterns for each car.
Inputs: no named parameters. Returns: result
get_daily_driving_patternsB
Get the daily driving patterns for each car.
Inputs: no named parameters. Returns: result
get_drive_summary_per_dayA
Get the drive summary per day for each car.
Inputs: no named parameters. Returns: result
get_efficiency_by_month_and_temperatureA
Get the efficiency by month and temperature for each car.
Inputs: no named parameters. Returns: result
get_longest_drives_by_distanceB
Get the longest drives by distance for each car.
Inputs: no named parameters. Returns: result
get_monthly_driving_summaryA
Get the monthly driving summary for each car.
Inputs: no named parameters. Returns: result
get_most_visited_locationsA
Get the most visited locations for each car.
Inputs: no named parameters. Returns: result
get_software_update_historyA
Get the software update history for each car.
Inputs: no named parameters. Returns: result
get_tire_pressure_weekly_trendsA
Get the tire pressure weekly trends for each car.
Inputs: no named parameters. Returns: result
get_total_distance_and_efficiencyA
Get the total distance and efficiency for each car.
Inputs: no named parameters. Returns: result
get_unusual_power_consumptionB
Get the unusual power consumption for each car.
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Tesla data for your AI: battery, range, charging, tires, alerts, history. Controls off by default.
Control your Tesla from your AI assistant - climate, charging, access, and security.
AI for your car: check charge, start climate, lock/unlock, open trunk via Tesla Fleet API. OAuth.
Tesla Fleet API for AI: send navigation destinations, read battery and location, run car commands.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with PostgreSQL databases through natural language queries, schema inspection, and safe SQL execution.4 npm1ISC
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to safely interact with PostgreSQL databases, perform queries, inspect schemas, and analyze query performance.2ISC
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to securely query and modify PostgreSQL databases, supporting SQL queries, table management, and schema inspection.-
- AlicenseCqualityCmaintenanceEnables 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