Ext Ops Panel
Open dashboard
Comparison

Suzieq vs Network AIops

Suzieq is an MCP server published by PovedaAqui. Marketplaces we read that list it: 1 (Docker MCP Catalog). Network AIops is an MCP server published by AIops-tools. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceSuzieqNetwork AIops
Docker MCP Catalog Listed
Version: sha256:ea9f7d06053d
Forks (GitHub): 1
Pulls (Docker Hub): 33 526
Stars (Docker Hub): 1
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.12.3
Downloads/month (PyPI): 970
Downloads/week (PyPI): 130
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Suzieq vs Network AIops
FactSuzieqNetwork AIops
Marketplaces that list it11
Stars (GitHub) (differs)4 (better)0 (worse)
Pulls (Docker Hub) (differs)33 526No figure on Docker Hub
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/suzieq-mcp)On your machine (network-aiops)
Transportstdiostdio
Tools it declares (differs)2Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/povedaaqui/suzieq-mcpgithub.com/aiops-tools/network-aiops
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Suzieq

In its own words, on Docker MCP Catalog:

MCP Server to interact with a SuzieQ network observability instance via its REST API.

Network AIops

In its own words, on Official MCP Registry:

Governed network device ops (NAPALM) — 33 MCP tools with audit/undo.

How to run each

Suzieq As a local MCP server: Docker image

Claude Code
claude mcp add --env "SUZIEQ_API_KEY=<YOUR_SUZIEQ_API_KEY>" --transport stdio suzieq -- docker run -i --rm -e SUZIEQ_API_KEY mcp/suzieq-mcp

Requires: SUZIEQ_API_KEY (secret)

Network AIops As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio network-aiops -- uvx network-aiops

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of Network AIops publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Network AIops publish no settings it asks for, so we do not compare settings.

What it can do: Suzieq · What it can do: Network AIops · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built