Tesla
Server Details
Control your Tesla - wake it, warm it up, unlock and more. Get your developer token at https://Infoseek.ai/mcp. Also requires your own Tesla developer token which is tied to your car/fleet.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over 38 days
- Last Tested
- Transport
- Streamable HTTP
- URL
TDQS
Scored across 15 tools
Each tool has a clearly distinct purpose with no functional overlap. The three navigation variants are explicitly differentiated by input type (GPS coordinates vs. Place IDs vs. multi-stop waypoints), and vehicle control actions (climate, locks, lights, horn, windows, sunroof) target separate physical systems.
Most tools follow a consistent 'vehicle_<feature>_<action>' pattern (e.g., vehicle_door_lock, vehicle_auto_conditioning_start). Minor deviations exist with verb-first naming for vehicle_flash_lights, vehicle_honk_horn, and vehicle_wake_up, but these remain readable and predictable.
Fifteen tools is an ideal count for this domain—comprehensive enough to cover essential remote vehicle operations (climate, security, navigation, alerts) without bloat. Each tool earns its place; even the three navigation variants serve distinct integration scenarios.
The surface covers the core remote control lifecycle well (wake, status, climate, locks, lights, navigation). Minor gaps exist for EV-specific operations like charging control (start/stop charging, open charge port) and trunk/frunk access, but agents can accomplish primary 'remote control' workflows without these.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
15 tool updates
- First observed
vehicle_auto_conditioning_start - First observed
vehicle_auto_conditioning_stop - First observed
vehicle_door_lock - First observed
vehicle_door_unlock - First observed
vehicle_flash_lights - First observed
vehicle_honk_horn - First observed
vehicle_list - First observed
vehicle_navigation_gps_request - First observed
vehicle_navigation_placeid_request - First observed
vehicle_navigation_waypoints_request - First observed
vehicle_remote_boombox - First observed
vehicle_status_overview - First observed
vehicle_sun_roof_control - First observed
vehicle_wake_up - First observed
vehicle_window_control
Related MCP Connectors
- mytesla.ioOAuthio.mytesla
Control your Tesla from your AI assistant - climate, charging, access, and security.
MCP server wrapping the Tesla Fleet API and TeslaMate API
Unofficial integration! ## ✨ Key Features ### 💰 Financial Intelligence - **Smart Charging Cost An…
Hosted MCP server with managed OAuth for 15+ toolkits: Google Workspace, Fitbit, Oura, Kalshi, etc.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceA Model Context Protocol server for the TeslaFi API that lets MCP clients query live vehicle data, drive and charge history, commute patterns, and optionally send commands.2MIT
- FlicenseNot gradedqualityDmaintenanceEnables control and monitoring of Tesla vehicles via the Tessie API, providing state and command tools for climate, locks, charging, and navigation.-
- FlicenseNot gradedqualityCmaintenanceEnables control and monitoring of Tesla vehicles through the Tessie API, providing access to vehicle state (battery, location, climate) and commands (lock/unlock, climate control, navigation) with support for both local and Cloudflare Worker deployment.11-
- AlicenseNot gradedqualityBmaintenanceMinimal stdio MCP server for Tesla Fleet API, enabling vehicle listing, state checks, live data, nearby chargers, wake, and command tools (climate, charge, lock) via optional tesla-http-proxy.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.