Skip to main content
Glama
6547709

TeslaMate MCP Server

by 6547709
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to TeslaMate MCP Server

No user-submitted related servers found.

    Related Servers

    • TeslaMate MCP Server

      mikeysrecipes
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to query Tesla vehicle data and analytics from a TeslaMate PostgreSQL database, including battery health, driving statistics, charging sessions, and custom SQL queries.
      18
      1
      MIT

    • mcp-teslamate-fleet

      lodordev
      A
      license
      B
      quality
      C
      maintenance
      MCP server combining TeslaMate historical analytics with Fleet API live data and commands. Works with Claude Code, Claude Desktop, Cursor, and any MCP-compatible client.
      29
      2
      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.
      -

    • teslamate-mcp

      cobanov
      A
      license
      A
      quality
      A
      maintenance
      A Model Context Protocol (MCP) server that provides access to your TeslaMate database, allowing AI assistants to query Tesla vehicle data and analytics.
      18
      140
      MIT

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

    C2.9/5.0

    Scored across 38 tools

    Disambiguation2/5

    Several tool pairs overlap heavily: tesla_status vs tesla_live both report current vehicle state; tesla_charging_history vs tesla_charges both return charging sessions; tesla_monthly_report, tesla_monthly_summary, and generate_monthly_driving_report all produce monthly summaries; tesla_savings vs calculate_eco_savings_vs_icev both compare against a gas car. Descriptions attempt to distinguish them, but the agent can easily pick the wrong one.

    Naming Consistency3/5

    Most tools share a tesla_ prefix without a verb, while a sizable minority use get_/generate_/check_/calculate_ verb patterns. The mix is still readable, but it is not a single predictable convention.

    Tool Count2/5

    With 38 tools, the surface is heavy for a read-only TeslaMate server, and many overlapping analytics could be parameters or consolidated. It far exceeds a well-scoped set and increases selection burden.

    Completeness4/5

    Coverage is broad: vehicle status, charging, drives, efficiency, battery health, TPMS, location, state history, software updates, savings, weather, and reports. Minor gaps exist around geofence/place management and deeper session drill-down, but typical analytics workflows are covered.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources