MCP.so
登录
V

Victron Vrm Mcp — Mcp Server

@lubosstrejcek

关于 Victron Vrm Mcp — Mcp Server

暂无概览

基本信息

分类

其他

传输方式

stdio

发布者

lubosstrejcek

提交者

Lubos Strejcek

配置

暂无标准配置

该服务器的 README 中没有可解析的 MCP 配置块,请前往代码仓库查看安装说明。

代码仓库

工具

50

List all sites the token can access (supports `limit` for markdown truncation)

Search by site ID, email, username, serial number, site identifier, or email domain

Resolve a 12-char portal ID to a numeric `idSite`

List invitations issued/received by the user

Connected devices + roles for a site

Per-device last-known attribute values

Time-series stats (15min/hours/days/weeks/months/years)

Lifetime aggregate stats

Configured alarms, devices, notification users, available attributes

Users + invites + access requests + group links on a site

Tags grouped by source (user/team/group/predefined)

Current Dynamic ESS configuration

GPS position history

Timestamp of the last forecasts reset (0 if never)

Custom widgets configured on a site

Generic dispatcher for any VRM widget name (BatterySummary, SolarChargerSummary, TankSummary, VeBusState, MPPTState, InputState, InverterState, PVInverterStatus, MotorSummary, GlobalLinkSummary, MeteorologicalSensorOverview, Status, HoursOfAc, LithiumBMS, DCMeter, FuelCellState, BatteryRelayState, ChargerRelayState, GatewayRelayState, SolarChargerRelayState, BatteryMonitorWarningsAndAlarms, VeBusWarningsAndAlarms, InverterChargerState, InverterChargerWarningsAndAlarms, EssBatteryLifeState, IOExtenderInOut, BMSDiagnostics, HistoricData, TempSummaryAndGraph, TempAirQuality, EvChargerSummary, etc.)

Time-series graph with `attributeCodes[]` / `attributeIds[]`, `start`/`end`, `useMinMax`

Generator state-change timeline

Mark/unmark a site as favorite

Attach a tag to a site

Detach a tag from a site

Acknowledge an active alarm

Create alarm (float or enum threshold variant)

Modify existing alarm

Delete alarm definition

Reset forecasting baseline for a site

Update site name/notes/geofence/alarm-monitoring/Node-RED restrictions/etc.

Write Dynamic ESS configuration (schedule, b2g, priceSchedule, batteryKwh, etc.)

Invite a user by email with access level (0=monitoring, 1=admin, 2=technician)

Remove a user from a site

Remove the current user from a site (self-unlink)

Bulk-update per-user access levels

Bulk-update pending-invite access levels

Link user groups with access levels

Change or remove a user group's access level

Add an installation to a user account

Create a long-lived personal access token

Revoke one token by id or ALL with `"*"` — **can self-lockout**

Fetch a short-lived Bearer for the demo tenant (read-only)

Log in with email+password (DEPRECATED, security hazard — use access tokens)

Invalidate the current Bearer session

List custom widgets on a site

Create (confirm-gated)

Update (confirm-gated)

Delete (confirm-gated)

Search user's installations by attribute conditions (`bs>=50,au=(1,2)`); server-side `page`/`count` pagination

Catalog of all VRM attribute definitions

All devices across the system

Count installations by data-attribute condition

Bulk search export

概览

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.

How do I get a

评论

其他 分类下的更多 MCP 服务器