Industrial-AIOps Energy MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add iaiops-energy -- uvx iaiops-energy

{
  "mcpServers": {
    "iaiops-energy": {
      "command": "uvx",
      "args": [
        "iaiops-energy"
      ]
    }
  }
}

[mcp_servers.iaiops-energy]
command = "uvx"
args = ["iaiops-energy"]

{
  "mcpServers": {
    "iaiops-energy": {
      "command": "uvx",
      "args": [
        "iaiops-energy"
      ]
    }
  }
}

{
  "servers": {
    "iaiops-energy": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "iaiops-energy"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: IAIOPS_CONFIG (Path to the iaiops endpoints config YAML (defines IEC-104/DNP3/IEC-61850 targets); omit to use the default location), IAIOPS_MASTER_PASSWORD (Master password that unlocks the encrypted secret store holding endpoint credentials), IAIOPS_NO_EGRESS (Set 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).