🚗 Tessie MCP Server - Tesla Intelligence Platform

🚗 The most advanced Tesla MCP server available - Transform your Tesla ownership with intelligent analytics, cost optimization, and predictive insights through the Tessie API. From smart charging reminders to efficiency trends analysis, get the intelligence you need to optimize every aspect of your Tesla experience.

🆕 What's New in v1.2.0

• 📊 Efficiency Trends Analysis - Weekly/monthly/seasonal efficiency tracking with weather & speed impact

• 🔌 Smart Charging Reminders - Intelligent charging optimization with time-of-use cost savings

• 🛡️ Enhanced Error Handling - Robust retry logic with graceful degradation for vehicle sleep/offline states

• ⚡ Improved FSD Detection - Removed reliance on broken autopilot_distance API field

• 🎯 Production Ready - Comprehensive error classification with user-friendly messages

✨ Key Features

💰 Financial Intelligence

• Smart Charging Cost Analysis - Track home vs Supercharger vs public charging costs

• Trip Cost Optimization - Calculate real trip costs with gas vehicle comparisons

• Money-Saving Recommendations - "Shift to off-peak charging to save $45/month"

• Environmental Impact Tracking - CO2 savings and tree-planting equivalents

🧠 Predictive Analytics

• Commute Pattern Detection - Auto-identify regular routes (home ↔ work)

• Efficiency Trend Analysis - Track route performance over time

• FSD Usage Estimation - Predict autopilot usage from driving patterns

• Future Trip Planning - Cost estimates and charging strategy for upcoming trips

📊 Advanced Insights

• Efficiency Trends - Weekly/monthly/seasonal efficiency analysis with confidence scoring

• Weather Impact Analysis - Hot/cold weather penalties with optimization tips

• Speed Factor Analysis - Highway vs city efficiency with optimal speed recommendations

• Smart Charging Reminders - Priority-based alerts with cost savings calculations

• Time Pattern Detection - Best/worst days and times for efficient driving

• Route Optimization - "Your Santa Rosa commute efficiency is declining 📉"

• Charging Strategy - Optimal departure battery levels and time-of-use scheduling

• Weekly/Monthly Summaries - Comprehensive ownership analytics with actionable insights

🚗 Complete Tesla Data Access

• Real-time Vehicle State - Battery, location, climate, locks, speed

• Historical Driving Data - Trips, mileage, efficiency, routes

• Charging Analytics - Sessions, costs, locations, optimization

• Smart VIN Resolution - Automatically detects your active vehicle

🛡️ Production-Ready Reliability

• Intelligent Error Handling - Automatic retry with exponential backoff

• Graceful Degradation - Fallback responses when vehicle is asleep/offline

• Rate Limit Respect - Smart handling of Tessie API limits with retry-after

• Network Resilience - Robust handling of timeouts and connectivity issues

• User-Friendly Errors - Clear explanations with actionable troubleshooting tips

• Context-Aware Responses - Different retry strategies for real-time vs historical data

Installation

Choose your preferred installation method:

Option 1: Via Smithery (Universal - Recommended) 🌐

Install automatically via Smithery:

Benefits of Smithery Installation:

• ✅ Works with any MCP-compatible client (Claude Desktop, Kiro, Cursor, Windsurf, etc.)

• ✅ Automatic updates when new versions are released

• ✅ HTTPS remote access - no local installation required

• ✅ Secure configuration management

• ✅ Cross-device configuration sync

• ✅ One-command installation and setup

After installation, you'll be prompted to configure your Tessie API token. See the Configuration section below for details.

Option 2: Manual HTTPS Configuration (Remote Access)

For direct HTTPS access without the Smithery CLI, add to your MCP client configuration:

Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):

Kiro (.kiro/settings/mcp.json):

Other MCP Clients: Consult your client's documentation for adding remote MCP servers via HTTPS.

Option 3: MCPB Package (For MCP Clients)

1. Download the latest tessie-mcp-v*.mcpb file from the GitHub releases page

2. Double-click the .mcpb file to install it in your MCP client

3. Enable the extension in your client settings

4. Configure your Tessie API token when prompted

Prerequisites

• MCP-compatible client (Claude Desktop v0.10.0+, Kiro, Cursor, Windsurf, or any MCP client)

• Tessie account with API access from tessie.com

• Node.js v18.0.0 or later (only for local development, not required for Smithery installation)

Configuration

Getting Your Tessie API Token

The server requires your Tessie API token to access your Tesla vehicle data:

1. Log into Tessie: Visit https://my.tessie.com and sign in

2. Navigate to API Settings: Go to Settings → API (or visit https://my.tessie.com/settings/api directly)

3. Copy Your Token: Your API token will be displayed on this page

4. Keep It Secret: Treat this token like a password - it provides full access to your vehicle data

Configuring the Token

For Smithery Installation: When you first connect to the server, your MCP client will prompt you to enter the TESSIE_API_KEY. Simply paste your token from the steps above.

For Manual Configuration: Add the token to your MCP client's configuration file:

For Local Development: Create a .env file in the project root:

Verifying Configuration

After configuration, test the connection by asking your MCP client:

• "What's my Tesla's current battery level?"

• "Show me my vehicle status"

If you see vehicle data, you're all set! If you get an authentication error, double-check your API token.

Upgrading

• Smithery: Run the install command again to upgrade to the latest version

• MCPB: Download and install the new .mcpb file (automatically replaces the old version)

• Manual HTTPS: No action needed - Smithery automatically serves the latest version

🌐 Using HTTPS Remote Access

One of the key benefits of Smithery deployment is HTTPS remote access - your MCP server runs in the cloud, so you don't need Node.js or any local installation.

How It Works

Benefits

No Local Installation Required:

• No Node.js installation needed on your machine

• No package management or dependency issues

• Works on any device with an MCP-compatible client

Always Up-to-Date:

• Automatic updates when new versions are released

• No manual upgrade process required

• Always running the latest stable version

Cross-Device Sync:

• Configure once, use everywhere

• Same API token works across all your devices

• Consistent experience on desktop, laptop, etc.

Reliable & Scalable:

• Hosted on Smithery's infrastructure with high availability

• Automatic scaling during high usage

• Professional monitoring and maintenance

Example Usage Scenarios

Scenario 1: Quick Setup on a New Device

Scenario 2: Multiple MCP Clients

Scenario 3: Team Sharing Each team member can install the same server with their own Tessie API token:

🛠️ Available Tools

🚗 Vehicle Information & Status

• get_vehicles - List all vehicles in your Tessie account

• get_vehicle_current_state - Get comprehensive vehicle status with location address

• get_driving_history - Get driving history and trip data

• get_weekly_mileage - Calculate total miles driven in a specific period

💰 Financial & Cost Analysis

• analyze_charging_costs - Comprehensive charging cost analysis by location type

• calculate_trip_cost - Calculate cost and environmental impact of completed trips

• estimate_future_trip - Plan charging strategy and costs for upcoming trips

🧠 Intelligence & Analytics

• analyze_latest_drive - Detailed analysis of recent drive with FSD prediction

• analyze_commute_patterns - Detect regular routes with efficiency trends

• analyze_efficiency_trends - Comprehensive efficiency analysis with weather/speed/time factors

• get_smart_charging_reminders - Intelligent charging optimization with cost savings

• natural_language_query - Process natural language queries about vehicle data

🔋 Battery & Charging

• Smart charging cost tracking with home vs Supercharger vs public analysis

• Money-saving recommendations based on usage patterns

• Time-of-use optimization for peak/off-peak charging rates

📍 Location & Navigation

• Automatic address resolution from GPS coordinates

• Route pattern recognition for commute detection

• Distance and efficiency calculations between locations

🤖 Predictive FSD Detection

• Highway speed consistency analysis for autopilot estimation

• Route-based FSD probability using driving patterns

• Efficiency comparison between predicted FSD and manual driving

💬 Example Commands

🚗 Vehicle Status & Location

💰 Cost Analysis & Optimization

🗺️ Trip Planning & Analysis

🛣️ Commute & Route Intelligence

🤖 FSD & Autopilot Analysis

📊 Advanced Analytics & Efficiency

🔌 Smart Charging & Optimization

📊 Comprehensive Analytics

Your MCP client will automatically use the appropriate Tessie tools to get the information you need.

Smart VIN Resolution

The server automatically handles vehicle identification:

• Single Active Vehicle: If you have one active Tesla, it's used automatically

• Multiple Vehicles: If you have multiple active vehicles, you'll be prompted to choose

• No Active Vehicles: Clear error messages if no vehicles are available

Experimental FSD Detection

⚠️ Important Disclaimer: The FSD detection feature is experimental and provides estimates only. It is not verified by Tesla or Tessie and should not be considered accurate for official purposes.

How It Works

The server analyzes driving patterns to estimate when Full Self-Driving might have been active:

• Speed Consistency: FSD maintains very consistent speeds, especially on highways

• Heading Smoothness: FSD produces smooth, predictable steering patterns

• Route Characteristics: FSD is more commonly used on highways and longer trips

• Duration Analysis: FSD usage typically correlates with longer drive segments

Confidence Scoring

Each analysis receives a confidence score (0-100%):

• 80-100: Very High - Strong FSD-like patterns detected

• 60-79: High - Likely FSD usage based on multiple indicators

• 40-59: Moderate - Mixed signals, uncertain

• 20-39: Low - Likely manual driving

• 0-19: Very Low - Manual driving patterns

Limitations

• No Ground Truth: Tesla doesn't provide official FSD usage data

• Pattern-Based Only: Analysis relies on driving patterns, not direct FSD status

• Individual Variation: Driving styles vary; what looks like FSD for one person might be manual for another

• External Factors: Weather, traffic, and road conditions can affect patterns

• Experimental Feature: This is a research tool, not a definitive measurement

Use FSD detection results for personal analysis and insights, but don't rely on them for anything requiring precision.

API Coverage

This server implements all GET endpoints under "Vehicle Data" from the official Tessie API documentation:

• All vehicle information endpoints

• Complete battery and charging data

• Full location and driving history

• Climate and weather information

• Vehicle configuration and settings

• Service and alert data

• Tire pressure and consumption metrics

Security

Your Tessie API token security is our top priority:

Smithery Deployment:

• 🔒 Encrypted Storage: API tokens are encrypted at rest in Smithery's secure database

• 🔐 Session Isolation: Each user session is completely isolated - your configuration is never shared

• 🌐 HTTPS Transport: All communication between your client and Smithery uses TLS encryption

• 📝 No Logging: API tokens are never logged or exposed in error messages

• 🔄 Secure Updates: Configuration updates are transmitted securely and validated

Local/Manual Configuration:

• 🔒 API tokens are stored securely in your MCP client's configuration files

• 🚫 No hardcoded credentials in the server code

• 🌐 All API communication with Tessie uses HTTPS

• 📋 Tokens are passed via environment variables, never in URLs or logs

Best Practices:

• Never share your Tessie API token with anyone

• Rotate your token periodically from https://my.tessie.com/settings/api

• If you suspect your token is compromised, regenerate it immediately in Tessie

• Use different tokens for different applications when possible

Requirements

• Node.js: v18.0.0 or later

• MCP Client: Any compatible client (Claude Desktop v0.10.0+, etc.)

• Platforms: macOS, Windows, Linux

• Tessie Account: Active subscription with API access

Troubleshooting

Server Not Running

• Check that you've enabled the server in your MCP client settings

• Verify your Tessie API token is correctly configured

• Try disabling and re-enabling the server

API Errors

• Ensure your Tessie API token is valid and hasn't expired

• Check that your Tesla is connected to Tessie

• Verify your Tesla is awake (some operations require the vehicle to be active)

No Vehicles Found

• Make sure your Tesla is linked to your Tessie account

• Check that the vehicle status shows as "active" in Tessie

• Try refreshing your vehicle connection in Tessie

Development

The server is built as a Node.js MCP (Model Context Protocol) server with:

• TessieClient: Handles all API communication with Tessie

• TessieMCPServer: Implements the MCP protocol for universal client compatibility

• Smart Error Handling: Comprehensive error messages and fallbacks

• Zero Dependencies: No external npm packages required

License

MIT License - see LICENSE file for details.

Support

For issues with the server:

1. Check the troubleshooting section above

2. Verify your Tessie account and API token

3. Check your MCP client logs for detailed error messages

For Tessie API questions, visit the official Tessie documentation.

Note: This server requires a Tessie account and active API access. Tessie is a third-party service that provides enhanced Tesla vehicle data access. Visit tessie.com to learn more.