Inspektor Gadget vs mission-control
mission-control is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
Inspektor Gadget is an MCP server published by inspektor-gadget. Marketplaces we read that list it: 1 (Docker MCP Catalog). mission-control is a plugin bundle for AI coding tools published by Unite-Group. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-23. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Inspektor Gadget | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:a54c99a50a81 Forks (GitHub): 6 Pulls (Docker Hub): 13 430 Stars (Docker Hub): 2 Stars (GitHub): 28 Not marked · First seen |
Not listed |
| Community marketplace cleanexpo/pi-dev-ops | Not listed | Removed on 2026-10-16 Version: not stated Forks (GitHub): 0 Stars (GitHub): 2 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 | mission-controlno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 28 | 2 |
| Pulls (Docker Hub) (differs) | 13 430 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 6 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/inspektor-gadget) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 37 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/inspektor-gadget/ig-mcp-server | github.com/cleanexpo/pi-dev-ops |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of mission-control
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Read your TacticalRMM fleet; run commands only after per-command human approval.
-
Read-only health and storage diagnostics for an enrolled CMDOP machine fleet.
-
Every Better Stack Uptime feature, plus an offline SQLite mirror and cross-resource fleet analytics
-
Direct MCP integration with the Claude Code Agent Monitor dashboard — real-time session data access, quick stats, and dashboard health monitoring via Model Context Protocol.
-
Uptime monitoring for developers — monitors, incidents, heartbeats, maintenance, status pages
-
Read-only agent radar, weekly editions, sourced guides, scenario choices and revision sync.
What each says it does
Inspektor Gadget
AI interface to troubleshoot and observe Kubernetes/Container workloads.
mission-control
Read-only fleet view: /mc opens a pane with each machine's status and heartbeat age, open claims and recent ships; fleet_status gives Claude the same summary. A failed read shows as unknown, never as a healthy fleet.
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-gadgetmission-control
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of mission-control publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Inspektor Gadget · What it can do: mission-control · 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.