Victron VRM MCP
Your VRM installations, in your AI assistant.
Connect Claude, ChatGPT, Cursor, VS Code or Claude Code to your VRM installations, and ask about them in plain language.
https://mcp.victronenergy.com/mcp
add_site
running…
done
I read VRM Portal ID c0619ab2f41e from the sticker and added it to your account. VRM will email you when the installation is ready.
Get started with your assistant
Pick your assistant. The first time you connect, a browser window opens so you can sign in with your Victron account.
Claude (claude.ai and Claude Desktop)
- Open Settings and go to Connectors.
- Choose Add custom connector, name it Victron VRM and paste the server URL.
- Select Connect, then sign in with your Victron account.
On Team and Enterprise plans, an owner adds the connector once in the organisation settings; everyone then connects with their own Victron account.
https://mcp.victronenergy.com/mcp
ChatGPT
- Open Settings and go to Apps & Connectors.
- Choose Add custom MCP server, name it Victron VRM, paste the server URL and keep authentication on OAuth.
- Tick I understand and want to continue, then choose Create as a plugin.
- Sign in with your Victron account when ChatGPT asks.
https://mcp.victronenergy.com/mcp
Claude Code
- Add the server from your terminal.
- Start claude and run
/mcp. - Select vrm, choose Authenticate and sign in with your Victron account.
claude mcp add --transport http vrm https://mcp.victronenergy.com/mcp
Cursor
- Select Add to Cursor, or add the configuration to
~/.cursor/mcp.jsonyourself. - In Cursor's MCP settings, connect vrm and sign in with your Victron account.
Or add it manually:
{
"mcpServers": {
"vrm": {
"url": "https://mcp.victronenergy.com/mcp"
}
}
}
VS Code
- Select Install in VS Code, or add the configuration to
.vscode/mcp.jsonin your workspace. - Start the vrm server and sign in with your Victron account when VS Code asks.
- Use it from Copilot Chat in agent mode.
Or add it manually:
{
"servers": {
"vrm": {
"type": "http",
"url": "https://mcp.victronenergy.com/mcp"
}
}
}
Other clients
- If your client supports remote MCP servers over HTTP, give it the server URL and choose OAuth.
- If it only runs local (stdio) servers, connect through mcp-remote with the configuration shown. It needs Node.js 18 or later.
- Sign in with your Victron account in the browser window that opens.
{
"mcpServers": {
"vrm": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.victronenergy.com/mcp"]
}
}
}
What you can ask
Talk about your systems the way you would to an installer. Your assistant picks the right VRM tool.
-
Works today
Add this GX device to VRM.
Attach a photo of the sticker on your Cerbo GX, Ekrano GX or Venus device. The assistant reads the VRM Portal ID and adds the installation to your account.
-
Works today
How much solar did my boat produce last week?
Solar yield per day, split into what went to your loads, the battery and the grid, and compared with the week before.
-
Works today
Which of my sites have alarms right now?
Active alarms across every installation you have access to, with when each site last sent data.
-
Works today
Which firmware is my Cerbo GX and solar charger on?
Every device in the installation with its product name, firmware version and last connection.
-
Works today
Compare battery SoC across my installations.
Live state of charge for each site side by side, so a fleet or a row of off-grid cabins fits in one answer.
-
Works today
What is Dynamic ESS planning for tonight?
The hourly plan: target battery charge, buy and sell prices, and when it will charge from or sell to the grid.
-
Works today
What happened to my battery voltage last night?
The logged values from the night, summarised per few minutes with lows and highs, so dips and charge cycles stand out.
-
Works today
Give me yesterday's data as CSV.
VRM's full data export with a download link you can open right away. Longer ranges, like last month, arrive by email.
Available tools
The tools your assistant can call today. Read tools only look; write tools change something in your VRM account.
| Tool | What it does | Access |
|---|---|---|
add_site |
Adds an installation to your VRM account using its VRM Portal ID, the ID printed on the GX device. It can also hand a new installation to one of your teams or put it in an installation group. | Write |
list_installations |
Lists the installations you can see in VRM, with their name and VRM Portal ID. Can filter by name and include active alarms and when each site last sent data. | Read |
search_installations |
Searches your installations like the VRM search box: by name, VRM Portal ID, a device's serial number or product, or a user's name or email. Handy for large fleets. | Read |
get_system_overview |
Shows the devices in one installation, such as the GX device, solar chargers and battery monitors, with their product, firmware version and last connection. | Read |
get_live_status |
Shows the latest values of an installation: battery state of charge, voltage and power, solar power, grid power, AC loads, system state and Dynamic ESS mode. | Read |
get_energy_stats |
Reports energy in kWh for a day, week, month or year: solar yield, consumption, grid import and export, and battery flows, in the installation's local time. | Read |
get_alarm_log |
Lists recent alarms, warnings and faults with their device and start and clear times, active ones first. | Read |
clear_alarm |
Clears an active alarm, as the Clear button in VRM does. It is recorded in the installation's event log. | Write |
get_dess_schedule |
Shows whether Dynamic ESS is on and its plan for the coming hours: target state of charge, buy and sell prices, and planned grid and battery energy. | Read |
get_data_log |
Reads the detailed logged values of an installation, such as battery voltage, state of charge and solar power, for up to one day at a time, so your assistant can analyse them. | Read |
export_data |
Exports logged data or hourly kWh as a CSV or Excel file, like Data download in VRM. For up to a day you get a download link that works for 15 minutes; longer ranges, up to a year, arrive by email. | Read |
Safe by design. Your assistant sees what you see in VRM.
The server never holds a password or API token for you. Every request runs as you, with your VRM permissions.
- Sign in with your Victron account
- OAuth 2.1 with PKCE. There is no long-lived token to create, copy or keep in your client's config.
- Exactly your VRM permissions
- The assistant acts as you. Installations you can't open in VRM don't exist for it, and read-only access stays read-only.
- Writes need your consent
- When you connect, you choose between read-only and read and write. Anything that changes VRM, like adding an installation, only works with read and write.