MCP Servers for Energy and Grid Systems

The Model Context Protocol (MCP) is rapidly becoming a real way to give an AI agent observability and write-access to energy hardware — solar inverters, battery management systems, microgrid controllers, utility-side grid meters. This is a guide to the servers that exist, the protocols they speak, and what's still missing for a serious AI-driven energy stack.

The protocols an energy MCP server has to speak

Energy hardware lives in an awkward intersection of standards. The ones any practical MCP server has to handle:

What's real today

The energy-MCP space is the earliest of the verticals in this directory, but the servers that exist are real.

Victron — solar + battery + grid in one stack

lubosstrejcek/victron-tcp is the cleanest entry into "MCP for an energy system." Targets Victron GX devices (Cerbo GX, CCGX) — the central controller in any Victron solar + battery installation — over Modbus TCP and MQTT. Local-LAN-only, no Victron VRM cloud required, no data leaves the building. 32 tools and 23 guided workflows across 900+ Modbus registers cover live battery state-of-charge, solar production, grid import/export, load consumption, and inverter configuration. TypeScript, MIT-licensed.

Realistic users: off-grid homes and farms, RV / boat owners running Victron systems, microgrid integrators who want an AI co-pilot watching production vs. load. If you have a Cerbo GX on the network, this server is <10 minutes from install to "Claude, how much energy did the array produce yesterday and is the battery healthy?"

Multi-asset energy infrastructure

kasathur/energyatit-mcp-server claims first-mover status as a multi-asset energy MCP server — 30+ tools across battery energy storage systems (BESS), HVAC, solar, and EV chargers, across 8 protocols. Still early; vendor support varies. Worth pulling if you have a heterogeneous energy stack and want one MCP surface across all of it instead of vendor-by-vendor servers.

Carbon-aware compute

karthikravva/MCP-Energy-Hub is a thinner cut at the problem: real-time grid carbon-intensity data so an AI agent can schedule compute (or charging, or HVAC pre-cooling) for the cleanest hour of the day. Not a hardware-control server; a decision-support layer that pairs well with one of the actuation servers above.

What's still missing

Picking one to start with

If you have a Victron stack: victron-tcp, 5 minutes. If you have a generic Modbus-speaking inverter or battery: kukapay/modbus-mcp as the bridge, then write the energy-specific prompts on top. For a multi-asset DER stack the EnergyAtIt server is the closest single-pane offering today.

Read the getting-started guide →