by AIOps Tools
An MCP server with 33 tools for multi-vendor network device operations, reached over NAPALM, with an audit row for every call. It reads device state, runs diagnostics and can change config.
PluginContact for pricing
Step 1: Install with uv tool install network-aiops, or add it as a Claude Code plugin from the AIops-tools marketplace.
Step 2: Run network-aiops init to add a device, driver, host and encrypted password.
Step 3: Run network-aiops doctor to check the setup.
Step 4: Try reads such as network-aiops device facts -t core-sw1 or the diagnose commands for interface health and BGP.
Step 5: Dry-run changes with config diff before using the governed merge or replace tools.
Cisco IOS and IOS-XE, NX-OS and IOS-XR, Arista EOS and Juniper Junos. Other platforms may work through NAPALM community drivers but are not tested here.
It has no read-only switch or approval gate. Use a read-only device account so writes fail at the device.
In an encrypted store at ~/.network-aiops/secrets.enc, not in plaintext files.
No. The README says the tests are mock-based and it can be self-tested with cEOS, vMX or containerlab.
Requirements
Assay MCPAssay sits at the MCP tool-call boundary, allows or denies privileged calls by policy, and records offline-verifiable evidence of what happened. It runs in CI with no hosted backend.