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 | Sign in to Rivian. If Rivian sends a verification code to your phone or email, submit it with rivian_submit_otp. |
| rivian_submit_otpA | Complete Rivian sign-in with the verification code sent to your phone or email. |
| rivian_get_user_infoA | Get your account details, vehicles and software versions. |
| rivian_get_vehicle_stateB | Get vehicle state: battery, range, doors, windows, tires, location, climate, seat heating and ventilation, steering wheel heat, software versions, security and trailer status. |
| rivian_get_ota_statusA | Get the installed software version and any available update. |
| rivian_get_charging_sessionA | Get the active charging session, including available power, battery level, time remaining and cost. |
| rivian_get_charging_historyA | List charging history newest first, with energy, cost, duration and location. |
| rivian_get_charging_scheduleA | Get the days and times your vehicle is scheduled to charge. |
| rivian_get_drivers_and_keysA | List drivers, phone keys and key fobs with access to your vehicle. |
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 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.
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.
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.
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.