Skip to main content
Glama
PatrickHeneise

Rivian MCP

by PatrickHeneise
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
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

    • 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.
      17
      586 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.9/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose. The three charging tools are well-differentiated: history for past sessions, schedule for future plans, and session for active charging. No overlap between any tools.

    Naming Consistency5/5

    All tools follow a consistent pattern: 'rivian_' prefix, with most using 'get_' for read operations, and two auth tools using action verbs. Naming is uniform, snake_case, and predictable.

    Tool Count5/5

    9 tools is appropriate for a vehicle management server. It covers essential areas (vehicle state, charging, access, updates, account, login) without being excessive or sparse.

    Completeness3/5

    The tool set is heavily read-only, covering status queries well but lacking write operations like setting charging schedules, locking/unlocking doors, or adjusting climate. This is a notable gap for a vehicle management domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources