Overview
What is Victron VRM MCP — MCP Server?
Victron VRM MCP — MCP Server is an MCP (Model Context Protocol) server for Victron Energy’s VRM cloud API. It exposes 52 VRM tools over Streamable HTTP, enabling remote monitoring and control of Victron installations via the Anthropic MCP Connector API and any HTTP-capable MCP client.
How to use Victron VRM MCP — MCP Server?
Install and run the server using npx victron-vrm-mcp or npm install -g victron-vrm-mcp. It listens on http://127.0.0.1:3000/mcp by default; configure with environment variables (PORT, HOST, ALLOWED_ORIGINS, etc.). For remote access, put HTTPS in front—Cloudflare Tunnel is recommended. Clients connect by providing the server URL and a VRM personal access token (or a deprecated Bearer token for testing). See the README for Anthropic Messages API, Claude Code, Cursor, and Windsurf configuration examples.
Key features of Victron VRM MCP — MCP Server
- 52 tools covering 88 VRM operations (direct + widget endpoints)
- All destructive tools are confirm-gated for safety
- Streamable HTTP transport for remote, API-backed usage
- Security-first design with per-request authentication
- 208 tests for reliability
- Compatible with Anthropic MCP Connector and any MCP-over-HTTP client
Use cases of Victron VRM MCP — MCP Server
- Remotely monitor and control Victron energy systems when away from the boat or house
- Build API-backed applications via the MCP Connector without exposing LAN devices
- Manage multiple installations, alarms, user access, and site settings from a single endpoint
- Automate Dynamic ESS configuration and custom widget CRUD operations
FAQ from Victron VRM MCP — MCP Server
How does Victron VRM MCP differ from victron-tcp?
Victron VRM MCP uses the VRM cloud API over Streamable HTTP, works remotely, and has ~15 minute latency. victron-tcp connects locally via Modbus TCP + MQTT for real-time (~50 ms) access and raw register support. Both can be used simultaneously for different use cases.
What are the requirements to run Victron VRM MCP?
Node.js 18+, a VRM personal access token (or a demo‑login Bearer for testing), and public HTTPS for remote clients (e.g., Cloudflare Tunnel). The server runs as a self-hosted process.
