Skip to main content
Glama
Sign In
Rivian MCP

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
      F
      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 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
      289 npm
      MIT

    • TeslaMate MCP Server

      6547709
      A
      license
      C
      quality
      C
      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
      A
      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.
      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

    A4.6/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, with descriptions that explicitly differentiate similar tools (e.g., live vs. historical charging, OTA vs. vehicle state). No overlapping functionality; an agent can easily select the right tool.

    Naming Consistency5/5

    All tool names follow a consistent 'rivian_' prefix followed by a verb or noun phrase in snake_case, with no deviations. The pattern is predictable and readable.

    Tool Count5/5

    Nine tools provide a well-scoped set for reading Rivian vehicle and account data, without unnecessary or missing operations. The count is appropriate for the read-only focus.

    Completeness3/5

    The toolset is entirely read-only and lacks any commands to control the vehicle (e.g., lock/unlock, start charging, climate control) or manage schedules and access. These are notable gaps for a Rivian MCP server.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources