# Industrial-AIOps [Health: Active]

**Category:** 🏭 Industrial & IoT  
**Repository:** https://github.com/industrial-aiops/industrial-aiops  
**GitHub Stars:** 8  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/industrial-aiops

## Description
Governed OT data tap: 12 field protocols + cross-protocol RCA brain; audit + MOC gating.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "industrial-aiops": {
    "command": "uvx",
    "args": ["iaiops"]
  }
}
```

## Documentation

## What Industrial-AIOps does

Industrial-AIOps is a read-first data tap for operational technology environments. It connects to protocols including OPC UA, Modbus TCP/RTU, S7comm, Mitsubishi MC, Omron FINS, MTConnect, MQTT/Sparkplug B, EtherNet/IP, EtherCAT, PROFINET, SECS/GEM, HART-IP, BACnet/IP, and IO-Link. It also supports read-only REST access to Metasys, Niagara, and Ignition Gateway layers.

The server correlates observations across protocols instead of treating each source independently. Its analysis covers downtime root cause, ISA-18.2 alarm load, broken dataflows, data trustworthiness, OEE, asset inventory, and explanations of legacy PLC programs in ST, AWL, and L5X formats. Ten industry editions add read-only advisory checks for sectors such as factories, buildings, water, pharma, and renewables.

## How it works

MCP communication uses stdio. The same governance engine is used by the MCP interface and the CLI, applying audit, budget, risk-tier, and undo controls to calls. Read paths are the default operating model; write-capable paths are limited, disabled by default, and subject to dry-run, one-shot approval, undo capture, and hash-chained audit requirements.

The analysis engine is deterministic and does not need a language model API or GPU. An optional model can rephrase an already computed and cited RCA verdict through `rca_narrate`; it is not responsible for the underlying calculation. Every call is audited, and the project states that it does not send telemetry or phone home.

An Industrial-AIOps MCP server can also enforce an air-gapped posture with `IAIOPS_NO_EGRESS=1`. That setting withholds six deliberate egress tools: `stream_publish`, `stream_publish_event`, `uns_publish`, `historian_push`, `mqtt_publish`, and `rca_narrate`.

## Setup and configuration

Install the package with a protocol extra, such as `pip install "iaiops[modbus]"`, or select `[all]`. Run `iaiops init` to create `~/.iaiops/config.yaml`. Before connecting to equipment, `iaiops onboard status` checks local onboarding state without contacting devices, while `iaiops doctor` checks configuration, secrets, reachability, and version information.

The documented workflow is to create a scan plan, run the scan, draft configuration from stored scan results, collect a bounded sample, export and apply tag metadata, and then run analysis. `iaiops readiness` reports which scenarios are currently available and what each missing prerequisite requires. Container deployments use the published image over stdio and should mount a volume for the audit store. The repository also provides hardened, air-gapped deployment material.

## Tools and capabilities

- Survey devices with `iaiops scan plan` and `iaiops scan run`.
- Collect time-bounded data with `iaiops collect run`.
- Measure OEE with `iaiops oee measure`.
- Open investigations with `iaiops investigate open` and run RCA with `iaiops diag rca`.
- Export and apply tag metadata with `iaiops tags export` and `iaiops tags apply`.
- Validate deterministic analysis with `iaiops verify determinism`; the MCP-side equivalent is `verify_determinism`.
- Use protocol-specific reads, cross-protocol correlation, audit controls, and selected governed egress operations.

## Limitations and notes

The documented verification covers protocol libraries, containers, and in-process servers, but not real plant equipment. Evidence levels differ by protocol: some use third-party implementations, some use project-written servers, and some are mock-only. The separate `iaiops-energy` project contains substation and utility telecontrol support for IEC-104, DNP3, and IEC-61850; those protocols are not part of this package.

Although the project describes a read-first design, several tools can send data or perform other externally visible actions. Review the audit, approval, risk, and egress controls before enabling them in an OT environment. The optional narration model does not replace the deterministic, cited result.

_Full upstream README: https://allmcps.com/mcp/industrial-aiops/readme_