Skip to main content
Glama
keithah

Tessie MCP Extension

by keithah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Tessie MCP Extension

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 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.
      -

    • 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
      -

    • Rivian MCP

      PatrickHeneise
      A
      license
      A
      quality
      B
      maintenance
      Enables read-only access to vehicle data via the unofficial Rivian GraphQL API, allowing users to monitor battery levels, OTA updates, and charging status. It provides tools to check vehicle state and user account information directly through Claude.
      9
      8 npm
      2
      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

    B3.2/5.0

    Scored across 5 tools

    Disambiguation4/5

    The tools have mostly distinct purposes, but 'get_driving_history' and 'get_weekly_mileage' could be confused as both involve retrieving mileage data over time periods. However, their descriptions clarify that one is for general history and the other specifically for weekly totals, reducing ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent 'get_*' verb_noun pattern, making them predictable and easy to understand. The naming is uniform across all five tools, with no deviations in style or convention.

    Tool Count4/5

    Five tools is reasonable for a vehicle management server, though it feels slightly thin for comprehensive coverage. The tools cover key read operations but may benefit from additional actions like vehicle control or settings management to be fully scoped.

    Completeness3/5

    The server provides good read-only coverage for vehicle data, including state, history, and mileage. However, there are notable gaps such as missing update/control operations (e.g., lock/unlock, climate control) and administrative functions, which limits agent workflows to retrieval only.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources