MCP Server
MCP
Industrial-AIOps
Governed OT data tap: 14 field protocols + cross-protocol RCA brain; audit + MOC gating.
Install
uvx iaiops
Configuration Example
{
"remotes": [],
"packages": [
{
"registryType": "pypi",
"identifier": "iaiops",
"version": "0.22.0",
"transport": {
"type": "stdio"
},
"environmentVariables": [
{
"description": "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.",
"isRequired": true,
"name": "IAIOPS_MCP"
},
{
"description": "Path to the endpoints config YAML (default: ~/.iaiops/config.yaml).",
"name": "IAIOPS_CONFIG"
},
{
"description": "Master password unlocking the encrypted secret store (~/.iaiops/secrets.enc).",
"isSecret": true,
"name": "IAIOPS_MASTER_PASSWORD"
},
{
"description": "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.",
"name": "IAIOPS_NO_EGRESS"
}
]
}
]
}
mcp
model-context-protocol
pypi
By
Comments
Sign in to leave a comment