Skip to main content
Glama
Ownership verified

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.

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsA

Average 4/5 across 15 of 15 tools scored. Lowest: 2.9/5.

Server CoherenceA
Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Sign in to create a connector for this server.

Resources