Industrial-AIOps Energy
Read-only substation telemetry over IEC-104, DNP3 and IEC 61850 for AI agents
- Pricing
- Free
- Platforms
- CLI, Linux, macOS
- Runs
- Locally
- Version
- 0.2.1
- Listing updated
- today
Similar MCP servers
About Industrial-AIOps Energy
Industrial-AIOps Energy is a free MCP server for energy and smart home. It runs locally on your machine and is started by your AI client.
The energy edition of Industrial-AIOps adds three monitoring connectors for utility telecontrol: IEC 60870-5-104 for RTU telemetry, DNP3 for outstation monitoring and IEC 61850 MMS for substation IED reads. It sits on the shared iaiops core, which supplies audit, budget, risk-tier and undo governance plus a cross-protocol analysis layer for alarms, OEE and downtime root cause.
No control-direction writes are exposed, and the README says 80 tools are mounted, 75 read-only and none destructive, with every call audited by front-end and client. An IAIOPS_NO_EGRESS setting withholds tools that ship data out, for airgapped sites.
The README is frank that live testing on real RTU or IED hardware is still needed: all three paths pass loopback tests in CI, but physical devices remain unverified and nothing here implies certification. Native protocol libraries differ by platform, and the IEC 61850 wheel is Linux-only.
Install
Run in a terminal
claude mcp add iaiops-energy --env IAIOPS_MASTER_PASSWORD='<IAIOPS_MASTER_PASSWORD>' -- uvx iaiops-energyAdd to claude_desktop_config.json
{
"mcpServers": {
"iaiops-energy": {
"command": "uvx",
"args": [
"iaiops-energy"
],
"env": {
"IAIOPS_MASTER_PASSWORD": "<IAIOPS_MASTER_PASSWORD>"
}
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"iaiops-energy": {
"command": "uvx",
"args": [
"iaiops-energy"
],
"env": {
"IAIOPS_MASTER_PASSWORD": "<IAIOPS_MASTER_PASSWORD>"
}
}
}
}Add to .vscode/mcp.json
{
"servers": {
"iaiops-energy": {
"type": "stdio",
"command": "uvx",
"args": [
"iaiops-energy"
],
"env": {
"IAIOPS_MASTER_PASSWORD": "<IAIOPS_MASTER_PASSWORD>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"iaiops-energy": {
"command": "uvx",
"args": [
"iaiops-energy"
],
"env": {
"IAIOPS_MASTER_PASSWORD": "<IAIOPS_MASTER_PASSWORD>"
}
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"iaiops-energy": {
"command": "uvx",
"args": [
"iaiops-energy"
],
"env": {
"IAIOPS_MASTER_PASSWORD": "<IAIOPS_MASTER_PASSWORD>"
}
}
}
}Using several servers? Build one config file with the MCP config generator.
Configuration
IAIOPS_CONFIGPath to the iaiops endpoints config YAML (defines IEC-104/DNP3/IEC-61850 targets); omit to use the default location.IAIOPS_MASTER_PASSWORDMaster password that unlocks the encrypted secret store holding endpoint credentials.IAIOPS_NO_EGRESSSet to 1 to withhold every data-shipping tool (message bus, external historian, remote LLM) from list_tools() at registration time, for an airgap/sealed-box deployment. A data-exfiltration axis only, not read/write authorisation — every tool is governed and audited. This edition's connectors are monitor-only, so what this withholds are the base brain tools mirrored in from iaiops. Requires iaiops>=0.19.
Tools this server provides (4)
Taken from the project documentation; the running server may differ.
- stream_publish
- Publish data to a message bus (mirrored base tool).
- stream_publish_event
- Publish an event to a message bus.
- historian_push
- Push values to an external historian.
- rca_narrate
- Narrate a root-cause analysis.
What it does
- IEC-104 monitoring
- Reads RTU and substation telemetry.
- DNP3 monitoring
- Polls outstations and reports online state.
- IEC 61850 MMS
- Reads substation IED values on Linux.
- Governed calls
- Audit, budget, risk tiers and undo apply to every tool.
- No control writes
- The connectors only monitor; control is not exposed.
- Airgap mode
- IAIOPS_NO_EGRESS hides data-shipping tools.
Good for
- Inspect point values and quality from a substation RTU
- Compare readings across configured endpoints
- Feed telemetry into downtime root-cause analysis
- Run monitoring in an airgapped plant network
Pricing
Free
Free; installable from PyPI
Industrial-AIOps Energy FAQ
Can it operate breakers or send control commands?
No. The energy connectors are monitor-only and expose no control direction.
Is it tested on real hardware?
Not yet; the README says physical RTU and IED hardware remain unverified.
What does it need?
The iaiops core, a config YAML for endpoints, and native libraries for each protocol.
How is it installed?
From PyPI as iaiops-energy, run over stdio.
Is Industrial-AIOps Energy free?
Yes. Industrial-AIOps Energy is free to use.
How do I add Industrial-AIOps Energy to Claude Code?
Run this command in your terminal: claude mcp add iaiops-energy --env IAIOPS_MASTER_PASSWORD='<IAIOPS_MASTER_PASSWORD>' -- uvx iaiops-energy
What are the best alternatives to Industrial-AIOps Energy?
The closest alternatives to Industrial-AIOps Energy are Entso E, Openei Urdb, myIO, Cutlab CNC and ProofPass.
Where this comes from
- Description: written from the project's README.
- Install steps: from the official MCP Registry entry.
