Suzieq vs Performance Co-Pilot
Suzieq is an MCP server published by PovedaAqui. Marketplaces we read that list it: 1 (Docker MCP Catalog). Performance Co-Pilot is an MCP server published by major. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
| Marketplace |   Suzieq |  Performance Co-Pilot |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ea9f7d06053d Forks (GitHub): 1 Pulls (Docker Hub): 33 528 Stars (Docker Hub): 1 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.5.1 Downloads/month (PyPI): 185 Downloads/week (PyPI): 35 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
| Fact | Suzieq | Performance Co-Pilot |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 33 528 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/suzieq-mcp) | On your machine (pcp-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 3, secrets among them: 0 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/povedaaqui/suzieq-mcp | github.com/major/pcp-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
MCP Server to interact with a SuzieQ network observability instance via its REST API.
Performance Co-Pilot
Query system performance metrics via MCP - CPU, memory, disk I/O, network, processes
How to run each
Suzieq As a local MCP server: Docker image
claude mcp add --env "SUZIEQ_API_KEY=<YOUR_SUZIEQ_API_KEY>" --transport stdio suzieq -- docker run -i --rm -e SUZIEQ_API_KEY mcp/suzieq-mcpRequires: SUZIEQ_API_KEY (secret)
Performance Co-Pilot As a local MCP server: PyPI package
claude mcp add --transport stdio pcp -- uvx pcp-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Performance Co-Pilot publish no list of tools, so we do not compare tools.
Settings each asks for
Only Suzieq asks for
SUZIEQ_API_ENDPOINTSUZIEQ_API_KEY (secret)
Only Performance Co-Pilot asks for
PCP_HOSTPCP_PORTPCP_TARGET_HOST
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Suzieq · What it can do: Performance Co-Pilot · 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.