Ext Ops Panel
Open dashboard
Comparison

Suzieq vs runraid

Suzieq is an MCP server published by PovedaAqui. Marketplaces we read that list it: 1 (Docker MCP Catalog). runraid is a plugin bundle for AI coding tools published by Jacob Magar. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-22. 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
MarketplaceSuzieqrunraid
Docker MCP Catalog Listed
Version: sha256:ea9f7d06053d
Forks (GitHub): 1
Pulls (Docker Hub): 33 589
Stars (Docker Hub): 1
Stars (GitHub): 4
Not marked · First seen
Not listed
Community marketplace dinglebear-ai/unraid Not listed Listed
Version: 0.6.2
Forks (GitHub): 37
Stars (GitHub): 141
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 runraid
FactSuzieqrunraid
Marketplaces that list it11
Stars (GitHub) (differs)4 (worse)141 (better)
Pulls (Docker Hub) (differs)33 589No figure on Docker Hub
Forks (GitHub) (differs)1 (worse)37 (better)
Last release (differs)Not published2026-10-20
Where it runs (differs)On your machine (mcp/suzieq-mcp)On your machine (@dinglebear/unraid)
Transport (differs)stdioNot stated
Tools it declares (differs)2Not published
Environment variables it asks for (differs)2, secrets among them: 112, secrets among them: 6
Parts of the bundle (differs)Not a bundle2
LicenceMITMIT
Repository (differs)github.com/povedaaqui/suzieq-mcpgithub.com/dinglebear-ai/unraid
Changes in the last 7 days (differs)01
First seen (differs)2026-10-112026-10-13

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.

runraid

In its own words, on Community GitHub marketplaces:

Unraid monitoring via the Rust MCP server + CLI (single static binary). Bearer/OAuth auth, systemd or Docker deployment.

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)

runraid As a Claude Code plugin

Claude Code
/plugin marketplace add dinglebear-ai/unraid
/plugin install runraid@unraid-mcp

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

Tools each declares

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

Settings each asks for

Only Suzieq asks for

  • SUZIEQ_API_ENDPOINT
  • SUZIEQ_API_KEY (secret)

Only runraid asks for

  • UNRAID_API_KEY (secret)
  • UNRAID_API_SKIP_TLS_VERIFY
  • UNRAID_API_URL
  • UNRAID_RMCP_AUTH_ADMIN_EMAIL (secret)
  • UNRAID_RMCP_AUTH_MODE (secret)
  • UNRAID_RMCP_DISABLED_TOOLS
  • UNRAID_RMCP_ENABLED_TOOLS
  • UNRAID_RMCP_GOOGLE_CLIENT_ID
  • UNRAID_RMCP_GOOGLE_CLIENT_SECRET (secret)
  • UNRAID_RMCP_NO_AUTH (secret)
  • UNRAID_RMCP_PUBLIC_URL
  • UNRAID_RMCP_TOKEN (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Suzieq · What it can do: runraid · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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