Skip to main content
Glama
akrowczyk

Tessie MCP Server

by akrowczyk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Tessie MCP Server

No user-submitted related servers found.

    Related Servers

    • Tessie MCP Server

      alexcz-a11y
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides intelligent Tesla vehicle analytics and control through the Tessie API, including real-time status monitoring, charging cost optimization, efficiency trend analysis, trip planning, and predictive insights for Tesla owners.
      MIT

    • Tesla MCP Server

      iceener
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
      -

    • Tesla Tessie MCP Server

      EzeLLM
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides access to Tesla vehicle telemetry data via the Tessie API, enabling real-time monitoring of battery status, charging state, climate controls, location, and other vehicle metrics through 30+ tools with intelligent caching.
      -

    • Tessie MCP Extension

      keithah
      A
      license
      B
      quality
      A
      maintenance
      Enables Claude Desktop to access Tesla vehicle data through the Tessie API. Users can query their car's location, battery level, mileage, driving history, and charging status using natural language.
      5
      9
      MIT

    • Tesla MCP Server

      MyTeslaMate
      A
      license
      Not graded
      quality
      D
      maintenance
      Integrates with Tesla Fleet API and TeslaMate API to control vehicles, monitor energy (Powerwall/Solar), manage charging, and analyze driving data, with generative UI and skill workflows.
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 61 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes, but get_vehicle_state, get_vehicle_status, and get_full_status overlap in scope, which could confuse an agent. The many enable/disable pairs are otherwise unambiguous.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun snake_case pattern (get_*, set_*, start_*, stop_*, enable_*, disable_*). Exceptions like 'boombox' and 'remote_start' are minor and do not disrupt the overall pattern.

    Tool Count2/5

    At 61 tools, the set is excessively large. Many enable/disable pairs (e.g., enable_sentry_mode/disable_sentry_mode) could be consolidated into single set_* commands with boolean parameters, reducing bloat without losing functionality.

    Completeness5/5

    The tool surface is remarkably complete for a Tesla management server, covering state retrieval, climate, charging, security, historical drive/charge data, software updates, and comfort features. No major operational gaps are apparent.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources