Skip to main content
Glama
lodordev

mcp-teslamate-fleet

by lodordev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp-teslamate-fleet

  • Tesla MCP Server

    scald
    A
    license
    Not graded
    quality
    C
    maintenance
    A Model Context Protocol server that connects to the Tesla Fleet API, allowing AI assistants like Claude to control Tesla vehicles and access vehicle information through natural language commands.
    15
    MIT

  • 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

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

Related Servers

  • Tesla MCP Server

    Sara3
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that connects to the Tesla Fleet API, allowing users to control vehicles and retrieve real-time status updates through Claude and other AI assistants. It supports functions such as waking up vehicles, viewing detailed vehicle information, and debugging via both stdio and HTTP/SSE transports.
    MIT

  • Unoffical Polestar 2 MCP

    holger1411
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP (Model Context Protocol) server that exposes Polestar 2 vehicle data to AI assistants like Claude. Query your car's battery status, vehicle info, and health data through natural conversation.
    MIT

  • TeslaFi MCP Server

    Zenotech-bv
    A
    license
    Not graded
    quality
    A
    maintenance
    A 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.
    2
    MIT

  • tesla-fleet-mcp

    supervised-nl
    A
    license
    Not graded
    quality
    B
    maintenance
    Minimal 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

  • TeslaMate MCP Server

    6547709
    A
    license
    C
    quality
    A
    maintenance
    Enables reading Tesla vehicle data from a TeslaMate PostgreSQL database, including status, trips, charging, efficiency, weather integration, and more, via 38 tools for MCP-compatible clients like Claude Code.
    38
    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 29 tools

Disambiguation3/5

Most tools target distinct actions or data views, but several analytics tools overlap in purpose: tesla_status and tesla_live both report current state, charging_history and charging_by_location overlap, and drives vs longest_trips and location_history vs top_destinations cover similar territory. The descriptions help, but users may struggle to pick the right tool without reading carefully.

Naming Consistency4/5

All tools use a consistent tesla_ prefix and snake_case, which is clear and predictable. However, the pattern mixes noun-phrase names (tesla_status, tesla_drives, tesla_savings) with verb-phrase names (tesla_charge_start, tesla_set_temp, tesla_lock), so the naming convention is not fully uniform.

Tool Count2/5

With 29 tools, this server is over the 25-tool threshold that starts to feel heavy. The scope is broad—covering both TeslaMate analytics and Fleet API controls—but several analytics tools could be consolidated without losing functionality.

Completeness4/5

The toolset covers core Tesla workflows well: live state, historical analytics, charging, climate, locks, and sentry mode. Minor gaps exist, such as no charge-port control, no window/vent controls, and no explicit multi-vehicle selection, but these are not critical for the apparent single-owner use case.

Maintenance

ActivityNo data
ResponsivenessUnresponsive

Resources