Inspektor Gadget vs Suzieq
Inspektor Gadget is an MCP server published by inspektor-gadget. Marketplaces we read that list it: 1 (Docker MCP Catalog). Suzieq is an MCP server published by PovedaAqui. Marketplaces we read that list it: 1 (Docker MCP Catalog). As of our marketplace pass on 2026-10-19. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:a54c99a50a81 Forks (GitHub): 6 Pulls (Docker Hub): 13 353 Stars (Docker Hub): 2 Stars (GitHub): 28 Not marked · First seen |
Listed Version: sha256:ea9f7d06053d Forks (GitHub): 1 Pulls (Docker Hub): 33 565 Stars (Docker Hub): 1 Stars (GitHub): 4 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 | Inspektor Gadget | Suzieq |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 28 (better) | 4 (worse) |
| Pulls (Docker Hub) (differs) | 13 353 (worse) | 33 565 (better) |
| Forks (GitHub) (differs) | 6 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/inspektor-gadget) | On your machine (mcp/suzieq-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 37 | 2 |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/inspektor-gadget/ig-mcp-server | github.com/povedaaqui/suzieq-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
Inspektor Gadget
AI interface to troubleshoot and observe Kubernetes/Container workloads.
Suzieq
MCP Server to interact with a SuzieQ network observability instance via its REST API.
How to run each
Inspektor Gadget As a local MCP server: Docker image
claude mcp add --transport stdio inspektor-gadget -- docker run -i --rm mcp/inspektor-gadget
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-mcp
Requires: SUZIEQ_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Only Inspektor Gadget declares
gadget_advise_networkpolicygadget_advise_seccompgadget_audit_seccompgadget_bpfstatsgadget_deadlockgadget_fdpassgadget_fsnotifygadget_profile_blockiogadget_profile_cpugadget_profile_qdisc_latencygadget_profile_tcprttgadget_snapshot_process
Show the remaining 25
gadget_snapshot_socketgadget_tcpdumpgadget_top_blockiogadget_top_filegadget_top_processgadget_top_tcpgadget_trace_bindgadget_trace_capabilitiesgadget_trace_dnsgadget_trace_execgadget_trace_fsslowergadget_trace_lsmgadget_trace_mallocgadget_trace_mountgadget_trace_oomkillgadget_trace_opengadget_trace_signalgadget_trace_snigadget_trace_sslgadget_trace_tcpgadget_trace_tcpdropgadget_trace_tcpretransgadget_traceloopig_deployig_gadgets
Only Suzieq declares
run_suzieq_showrun_suzieq_summarize
Both declare
None
Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of Inspektor Gadget publish no settings it asks for, so we do not compare settings.
What it can do: Inspektor Gadget · What it can do: Suzieq · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.