Rivian MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RIVIAN_EMAIL | Yes | Your Rivian account email address. | |
| RIVIAN_PASSWORD | Yes | Your Rivian account password. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rivian_loginA | Log in to your Rivian account. Rivian will send a verification code to your phone or email — use rivian_submit_otp to complete sign-in. |
| rivian_submit_otpA | Complete Rivian sign-in with the verification code sent to your phone or email. |
| rivian_get_user_infoA | Look up your Rivian account — your vehicles, software versions, and account details. |
| rivian_get_vehicle_stateA | Check your vehicle's current status — battery, range, doors, windows, tires, location, climate, seat heat/vent, steering wheel heat, software versions, security, trailer status, and more. |
| rivian_get_ota_statusA | Check for software updates — what version you're running and whether a new one is available. |
| rivian_get_charging_sessionA | Check on an active charging session — power, battery level, time remaining, and cost. |
| rivian_get_charging_historyB | View past charging sessions — energy, cost, duration, and location for every charge. |
| rivian_get_charging_scheduleA | See your charging schedule — what times and days your vehicle is set to charge. |
| rivian_get_drivers_and_keysA | See who has access to your vehicle — drivers, phone keys, and key fobs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
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.
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.
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.
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.