Skip to main content
Glama
zentered-studios

Rivian MCP

by zentered-studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Rivian MCP

No user-submitted related servers found.

    Related Servers

    • 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

    • polestar-mcp

      NicolasKheirallah
      A
      license
      A
      quality
      B
      maintenance
      Enables querying your Polestar vehicle's data through plain-language MCP tools, including telemetry, charging, location, health, and charging plans via the Polestar Data Portal read-only API.
      23
      1
      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.
      -

    • Kia Access MCP

      chrischall
      A
      license
      A
      quality
      A
      maintenance
      A Model Context Protocol server that connects Claude to your own Kia vehicle through the Kia Owners API, enabling vehicle status, location, odometer, EV charge state, and confirm-gated commands for doors, climate, and charging.
      16
      591 npm
      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

    • geotab-mcp

      deanjbrown
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes the MyGeotab API as AI-callable tools, letting Claude query fleet data, device status, trips, tachograph files, fuel, diagnostics, faults, and driver information across multiple customer databases through natural language.
      -
    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.7/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool targets a distinct aspect (auth, account, vehicle state, OTA, three charging facets, keys), and descriptions clarify boundaries well. The only mild overlap is rivian_get_user_info vs rivian_get_drivers_and_keys for access/drivers, but the descriptions keep them separable.

    Naming Consistency5/5

    All tools share the rivian_ prefix and snake_case, with a predictable rivian_get_<noun> pattern for reads and rivian_login/rivian_submit_otp as the clear auth pair. No convention mixing.

    Tool Count5/5

    Nine tools is well-scoped for a vehicle API client, with each tool covering a meaningful slice (state, charging session/history/schedule, OTA, keys). No filler or redundant entries.

    Completeness3/5

    The surface is almost entirely read-only: there are no vehicle command tools (lock/unlock, climate, honk) and no way to set or modify the charging schedule, only read it. If read-only is intentional this is minor, but as an apparent Rivian control surface there are notable write/action gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources