Skip to content
MCP server

Cisco Meraki / Catalyst / ACI & Multi-vendor Controller AIops

Audited MCP tools for Meraki, Catalyst Center, ACI, Arista CVP and UniFi networks

Runs locallyStatus and history
Install
Pricing
Open source
Platforms
CLI, self-hosted
Runs
Locally
Version
0.15.1
Listing updated
today

Similar MCP servers

About Cisco Meraki / Catalyst / ACI & Multi-vendor Controller AIops

Cisco Meraki / Catalyst / ACI & Multi-vendor Controller AIops is an open-source MCP server for cloud and infrastructure. It runs locally on your machine and is started by your AI client.

Meraki is the reference platform here, with full read and write coverage, while the other controllers get a subset: Catalyst Center (read), Arista CloudVision (read), UniFi Network (read plus device restart) and Cisco ACI (read-only endpoint tracing and faults). Each controller maps the same canonical operations onto its own REST API through a registry, and anything unsupported returns an explanatory error instead of failing silently.

Three analyses stand out. An uplink analysis ranks MX WAN links by loss and latency and suggests a likely cause. A 0-100 network health score combines device online percentage, uplink health and an alert penalty, with every component shown. A template drift check lists settings that differ from the config template a network is bound to.

The server has 37 tools, 28 read and 9 write, all passing through an audit harness. Writes fetch the real prior state first, support dry runs and record an inverse where one exists, while rebooting a device or blinking LEDs cannot be undone. Controller secrets are held in an encrypted local store. The README says the project is community-maintained, MIT licensed and unaffiliated with the vendors, and that full end-to-end verification is still open.

Install

Run in a terminal

claude mcp add fabric-aiops -- uvx fabric-aiops

Add to claude_desktop_config.json

{
  "mcpServers": {
    "fabric-aiops": {
      "command": "uvx",
      "args": [
        "fabric-aiops"
      ]
    }
  }
}
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "fabric-aiops": {
      "command": "uvx",
      "args": [
        "fabric-aiops"
      ]
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "fabric-aiops": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "fabric-aiops"
      ]
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "fabric-aiops": {
      "command": "uvx",
      "args": [
        "fabric-aiops"
      ]
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "fabric-aiops": {
      "command": "uvx",
      "args": [
        "fabric-aiops"
      ]
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Tools this server provides (8)

Taken from the project documentation; the running server may differ.

overview
Rolls up the organisation, site or container.
uplink_loss_and_latency_rca
Ranks degraded uplinks and maps each to a likely cause.
network_health_score
Computes a 0-100 health score per network.
config_template_drift
Lists settings drifted from the template.
aci_endpoint_trace
Reconstructs an ACI endpoint path.
aci_faults_list
Lists ACI faults.
reboot_device
Reboots a device; cannot be undone.
undo_apply
Replays a recorded inverse operation.

What it does

Uplink loss ranking
Ranks WAN uplinks by composite loss and latency and suggests causes.
Network health score
A 0-100 score with every component returned.
Template drift
Lists settings that differ from the bound config template.
Five controller platforms
Meraki, Catalyst Center, CVP, UniFi and read-only ACI.
Undo and dry run
Writes record prior state, with dry-run previews and inverse operations.
Encrypted credentials
Secrets live in an encrypted local store, not plaintext.

Good for

  • Find the worst WAN uplinks across a Meraki organisation
  • Score the health of each network from device and alert data
  • Spot networks that have drifted from their config template
  • Trace an ACI endpoint path or list fabric faults

Pricing

Open source

Cisco Meraki / Catalyst / ACI & Multi-vendor Controller AIops FAQ

Which platforms can it change?

Writes are Meraki-only, except a UniFi device restart; other platforms return a not-supported error.

How many tools are there?

37, of which 28 are read and 9 write.

Can writes be undone?

Most record an inverse, but reboot_device and blink_device_leds declare no undo.

Is it affiliated with Cisco?

No. The README says it is community-maintained and not affiliated with Cisco, Meraki, Arista or Ubiquiti.

Is Cisco Meraki / Catalyst / ACI & Multi-vendor Controller AIops free?

Yes. Cisco Meraki / Catalyst / ACI & Multi-vendor Controller AIops is open source, so you can use and self-host it for free.

How do I add Cisco Meraki / Catalyst / ACI & Multi-vendor Controller AIops to Claude Code?

Run this command in your terminal: claude mcp add fabric-aiops -- uvx fabric-aiops

What are the best alternatives to Cisco Meraki / Catalyst / ACI & Multi-vendor Controller AIops?

The closest alternatives to Cisco Meraki / Catalyst / ACI & Multi-vendor Controller AIops are mcp, Webflow, Ripe Stat, Vercel MCP and OpenWrt MCP.

Where this comes from

  • Description: written from the project's README.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers