Fabric Aiops
Governed Cisco Meraki fabric ops: uplink RCA, health score, drift; 34 tools with audit/undo.
- Transport
- Not stated
- Package
- —
- Registry id
- io.github.AIops-tools/fabric-aiops
No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.
Disclaimer: Community-maintained open-source project. Not affiliated with, endorsed by, or sponsored by Cisco, Meraki, Arista, Ubiquiti, or any network-controller vendor. "Cisco", "Meraki", "Catalyst", "DNA Center", "Arista", "CloudVision", "Ubiquiti", "UniFi" and all product/trademark names belong to their respective owners. MIT licensed.
Governed AI-ops for network fabrics managed through a controller — the
Cisco Meraki Dashboard API (the reference platform, full read + write),
Cisco Catalyst Center (formerly DNA Center; read subset), Arista
CloudVision Portal (CVP) (read subset), and UniFi Network (self-hosted
controller or UniFi OS console; read subset + device restart) — with a
built-in governance
harness: unified audit log, token/runaway budget guard,
undo-token recording, and descriptive risk tiers. Multi-platform by
construction: a registry keyed by platform maps every canonical operation
onto each controller's REST API (path templates + response adapters), so adding
a controller is a registry entry, never new ops/CLI/MCP surface. An operation a
platform doesn't map returns a clear teaching error ("not supported on X yet —
open an issue"), never a silent no-op. The test suite is mock-based; no
platform has yet been exercised against a live controller — see
docs/VERIFICATION.md.
What it does
Three flagship signature analyses, plus the guarded reads and writes around them:
- Uplink loss & latency RCA — pull MX WAN uplink loss + latency across an org, rank the worst uplinks by a composite of average loss and latency, and map each degraded uplink to a likely cause + recommended action. Every ranking carries its numbers, not a black-box verdict.
- Network health score — a composite 0-100 score per network from device online %, uplink health %, and an alert-severity penalty (weighted 0.5/0.3/0.2), with every component returned so the number is explainable.
- Config template drift — for networks bound to a config template, list the settings that have drifted from the template (expected vs actual).
What works
- CLI (
fabric-aiops ...):init,overview,org,network,device,client,health,remediate,secret,doctor,mcp. - MCP server (
fabric-aiops mcporfabric-aiops-mcp): 34 tools (25 read, 9 write), every one wrapped with the bundled@governed_toolharness. - Encrypted credentials: the controller secret (Meraki API key / Catalyst Center
username:password/ CVP service-account token / UniFi API key) lives in an encrypted store~/.fabric-aiops/secrets.enc(Fernet + scrypt) — never plaintext on disk. Unlock with a master password fromFABRIC_AIOPS_MASTER_PASSWORD(MCP/CI) or an interactive prompt (CLI). - Reversibility: mutating writes fetch the real before-state first and record a faithful inverse (
update_device/update_network_vlanrestore prior values;claim↔remove;bind↔unbind/rebind). Irreversible ops (reboot_device,blink_device_leds) record the prior state for audit but declare no undo. - Safety: every state-changing CLI op supports
--dry-runand requires double confirmation; every write MCP tool takes adry_runpreview.
Capability matrix (34 MCP tools)
From the project's README.