Skip to main content
Glama

Rivian MCP

Ask Claude or ChatGPT about your Rivian and its recorded drives. Host the recorder in your Cloudflare account, or use the local version for live vehicle data. Tool results go to the AI app you connect. See data handling.

It only reads from Rivian. It sends no commands to your vehicle and changes no settings. This project is unofficial and not affiliated with or endorsed by Rivian.

Claude showing a recorded drive with its route on a map, distance, speed and elevation

Self-host on Cloudflare

You need:

  • A free Cloudflare account. See cost and removal.

  • A free GitHub account. The Deploy button asks you to connect it, and Cloudflare keeps your copy of the project there.

  • Your Rivian email and password, and the phone or email that gets Rivian's one-time code.

To skip GitHub, deploy from a terminal with Node.js 24.

1. Deploy

Deploy to Cloudflare

  1. Select the button and sign in to Cloudflare.

  2. Connect your GitHub account when asked.

  3. On Create and deploy, keep the suggested names and select Deploy.

  4. In the Worker's Settings, then Build, clear Enable Preview Builds.

See the setup guide for screenshots and account sign-up.

The first Rivian account that signs in becomes the owner. Connect right after you deploy.

Cloudflare creates the storage and starts the server. It shows your address:

https://rivian-mcp.<your-name>.workers.dev

Add /mcp to get your connector address:

https://rivian-mcp.<your-name>.workers.dev/mcp

2. Connect Claude

Works on claude.ai and in the Claude desktop and mobile apps.

  1. Open Settings, then Connectors, then Add custom connector.

  2. Name it Rivian and paste your connector address.

  3. Select Add, then Connect.

  4. Sign in with your Rivian email and password, then enter the one-time code Rivian sends you.

Recording starts as soon as you are signed in. In a new chat, ask "Is the recorder running?"

ChatGPT and Codex work too: Connect ChatGPT, Connect Codex.

What you can ask

  • "Show my last drive."

  • "Rivian status."

  • "List my drives this week."

  • "Show my stats for the last 30 days."

  • "Show my charging sessions."

  • "Export my last drive for Roadbook."

  • "What's my battery level?"

  • "Is there a software update available?"

  • "Are all the doors locked?"

Take your drives to Roadbook

Export your route, places and stats for Roadbook, an electric road-trip planner. Importing requires a Roadbook connector with an import_drive tool. Check its availability and privacy settings before sending a drive. See the export format.

Tools

Tool

What it does

show_status

Live dashboard: doors, locks, tires, battery, charging and updates

show_drive

One drive with its route map and speed, energy and elevation charts

show_stats

Totals and efficiency for a period, with every route on one map

show_charging

Charging sessions with energy added, power and battery level curves

list_drives

Drives with places, local times, energy, elevation and quality

get_drive

One drive as a GeoJSON Feature with the route and all stats

export_drive

One drive or a date range as a Roadbook payload, GeoJSON or GPX

recorder_status

Whether the recorder is signed in and connected

rivian_get_user_info

Your account, vehicles and software versions

rivian_get_vehicle_state

Live battery, doors, tires, location, climate and OTA status

rivian_get_ota_status

Current and available software versions

rivian_get_charging_session

Active charging session

rivian_get_charging_history

Past charging sessions with energy, cost and location

rivian_get_charging_schedule

Your charging schedule

rivian_get_drivers_and_keys

Drivers and their phone keys and key fobs

Cost, updates, where your data lives and how to remove it are in docs/cloudflare.md.

Related MCP server: Tesla Tessie MCP Server

Run it locally

The npm package provides a CLI and a local MCP server. Both query your vehicle while they are running; neither records drives. You need Node.js 24 or newer.

CLI

npx rivian-mcp ota    # software update status
npx rivian-mcp stats  # full vehicle state

Or install it globally:

npm install -g rivian-mcp
rivian ota
rivian stats

The CLI reads RIVIAN_EMAIL and RIVIAN_PASSWORD from the environment, or asks for them. Password and one-time-code prompts require an interactive terminal.

Local MCP server

claude mcp add rivian \
  -e RIVIAN_EMAIL=your@email.com \
  -e RIVIAN_PASSWORD=your-password \
  -- npx rivian-mcp

Add to ~/.claude.json or your project's .mcp.json:

{
  "mcpServers": {
    "rivian": {
      "command": "npx",
      "args": ["-y", "rivian-mcp"],
      "env": {
        "RIVIAN_EMAIL": "your@email.com",
        "RIVIAN_PASSWORD": "your-password"
      }
    }
  }
}

Rivian asks for a one-time code on every new sign-in:

  1. Ask Claude, "Log in to Rivian."

  2. Rivian sends a code to your phone or email.

  3. Tell Claude, "The code is 123456."

The local server adds rivian_login and rivian_submit_otp for this step. The CLI and the local server share the session in ~/.rivian-mcp/session.json. It is reused for up to 90 days.

Support

If you are thinking about getting a Rivian, my referral code gets you benefits on your purchase and supports this project:

Get a Rivian R1 with referral benefits

Development

git clone https://github.com/zentered-studios/rivian-mcp.git
cd rivian-mcp
npm ci
npm run typecheck
npm run lint
npm test
npm run build
npx wrangler deploy --dry-run

Use Node.js 24 or newer. Tests use fixtures, mocked requests and an in-memory SQLite database; they do not need Rivian credentials or a Cloudflare account. The dry run builds the Worker and embedded views without deploying.

For local Worker development, run npm run worker:dev and apply the schema with npx wrangler d1 migrations apply DB --local. No .dev.vars file is required. To pin the owner, create an ignored .dev.vars containing RIVIAN_EMAIL="you@example.com". Hosted AI connectors need a publicly reachable HTTPS Worker; localhost is for development.

Register live queries in src/tools.ts and local login tools in src/mcp-server.ts. Recorder tools belong in worker/src/mcp.ts; embedded views belong in worker/ui/. Add a regression test for behavior changes. Rivian access must remain read-only apart from authentication.

See tool-call examples for JSON arguments.

Claude Code plugin

The plugin documents the Rivian API fields, authentication and formatters for Claude Code.

claude /plugin marketplace add zentered-studios/rivian-mcp
claude /plugin install rivian-mcp@rivian-ai

References

Available Tools

9 tools
rivian_get_charging_historyA
Read-only

List past charging sessions, newest first. Each row has date, start and end time, duration, energy in kWh, cost or free, city, charging network and charger type (home, public or other). Use it for completed sessions. For a charge in progress use rivian_get_charging_session. Returns readable text. Includes charging sessions from every vehicle on the account. Requires a signed-in Rivian session and returns an error without one. Read-only: sends no command to the vehicle.

Inputs: limit.

rivian_get_charging_scheduleA
Read-only

Get the charging schedules saved for the vehicle: start and end time, duration, whether each is enabled, amperage, the days of the week and the location it applies to. Use it to see when the vehicle is set to charge. It does not change a schedule. For a charge in progress use rivian_get_charging_session. Returns readable text. Reads the first vehicle on the account. Requires a signed-in Rivian session and returns an error without one. Read-only: sends no command to the vehicle.

Inputs: no named parameters.

rivian_get_charging_sessionA
Read-only

Get the charge happening now: battery level, power in kW, energy added in kWh, current in A, time elapsed and remaining, cost so far or free, whether it is a Rivian charger, and the charger location. When no live session exists, it reports the vehicle charging state instead. For finished sessions use rivian_get_charging_history; for planned charging use rivian_get_charging_schedule. Returns readable text. Reads the first vehicle on the account. Requires a signed-in Rivian session and returns an error without one. Read-only: sends no command to the vehicle.

Inputs: no named parameters.

rivian_get_drivers_and_keysA
Read-only

List who and what can open and drive the vehicle: invited drivers, enrolled phone keys and key fobs. Use it to audit access to the vehicle. It does not add or revoke access. For account and vehicle details use rivian_get_user_info. Returns readable text. Reads the first vehicle on the account. Requires a signed-in Rivian session and returns an error without one. Read-only: sends no command to the vehicle.

Inputs: no named parameters.

rivian_get_ota_statusA
Read-only

Get the installed software version, the update status reported by the vehicle (for example idle) and any available update with its version and release notes link. Use it to check whether an update is waiting. For the full account and vehicle list use rivian_get_user_info. Returns readable text; shows "up to date" when no update is available. Reads the first vehicle on the account. Requires a signed-in Rivian session and returns an error without one. Read-only: sends no command to the vehicle.

Inputs: no named parameters.

rivian_get_user_infoA
Read-only

Get the account owner and each vehicle on the account: name, model, VIN, trim, drive system, colors, wheels, build date, installed software version and any available update with a release notes link. Use it to identify the vehicle or the account. For update progress use rivian_get_ota_status; for live readings use rivian_get_vehicle_state. Returns readable text. Requires a signed-in Rivian session and returns an error without one. Read-only: sends no command to the vehicle.

Inputs: no named parameters.

rivian_get_vehicle_stateA
Read-only

Get the live vehicle state as readable text: battery level and range, doors, windows, tires, location, climate, seat heating and ventilation, steering wheel heat, software versions, and security and trailer status. Use it for how the vehicle is right now. For an active charge use rivian_get_charging_session; for past charges use rivian_get_charging_history; for updates use rivian_get_ota_status. Distances follow the unit set in the vehicle. Reads the first vehicle on the account. Requires a signed-in Rivian session and returns an error without one. Read-only: sends no command to the vehicle.

Inputs: properties.

rivian_loginA

Sign in to Rivian with the RIVIAN_EMAIL and RIVIAN_PASSWORD set in the MCP server configuration. Call it when no session is saved or after the session expires; a saved session is restored on launch. Takes no arguments. Replaces the current session and saves it to ~/.rivian-mcp/session.json. When Rivian requires two-step verification, it sends a code to your phone or email and the sign-in stays pending until you pass the code to rivian_submit_otp. Returns a message saying either that you are signed in or that a code was sent, and an error if the credentials are missing or Rivian rejects them.

Inputs: no named parameters.

rivian_submit_otpA

Finish a Rivian sign-in with the verification code Rivian sent to your phone or email. Use it only after rivian_login reported that a code was sent; without a pending sign-in it returns an error and asks you to call rivian_login. On success it saves the session to ~/.rivian-mcp/session.json. Uses the RIVIAN_EMAIL set in the MCP server configuration. Returns a message saying you are signed in, or an error if Rivian rejects the code.

Inputs: otp_code (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • 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
    • 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.
      -
    • 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
    • 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
      237 npm
      MIT