Industrial-AIOps MCP Server

Industrial-AIOps is an MCP integration. Governed OT data tap: 14 field protocols + cross-protocol RCA brain; audit + MOC gating.

Packages and local setup

The published pypi package is iaiops, version 0.28.0. Its declared MCP transport is stdio.

The package declares IAIOPS_MCP (required): Tool-menu selection: comma-separated protocols or a named profile (e.g. 'fab', 'process', 'building', 'opcua,modbus'). No default since 0.10.0 — unset prints the selection menu and exits; set to a profile name (e.g. factory) or comma-list of protocols.; IAIOPS_CONFIG: Path to the endpoints config YAML (default: /.iaiops/config.yaml).; IAIOPS_MASTER_PASSWORD: Master password unlocking the encrypted secret store (/.iaiops/secrets.enc).; 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. This is a data-exfiltration axis only, not read/write authorisation — whether a write is allowed is the caller's decision, and every call (read or write) is audited. Gates MCP tools only — not a firewall..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.28.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.