mission-control vs Desktop Commander
mission-control is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
mission-control is a plugin bundle for AI coding tools published by Unite-Group. No marketplace we read lists it any more. Desktop Commander is an MCP server published by wonderwhy-er. Marketplaces we read that list it: 6 (Official MCP Registry, Claude Code: claude-plugins-official, Docker MCP Catalog, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-25. 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 | ||
|---|---|---|
| Community marketplace cleanexpo/pi-dev-ops | Removed on 2026-10-16 Version: not stated Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.1 Downloads/month (npm): 966 995 Downloads/week (npm): 159 845 Forks (GitHub): 1 258 Stars (GitHub): 10 123 Not marked · First seen |
| Claude Code: claude-plugins-official | Not listed | Listed Version: 0.2.0 Forks (GitHub): 1 258 Stars (GitHub): 10 123 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:5df787069e37 Forks (GitHub): 1 258 Pulls (Docker Hub): 239 768 Stars (Docker Hub): 22 Stars (GitHub): 10 123 Not marked · First seen |
| Claude: knowledge-work-plugins | Not listed | Listed Version: 0.2.0 Forks (GitHub): 1 258 Stars (GitHub): 10 123 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.2.0 Forks (GitHub): 1 258 Stars (GitHub): 10 123 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 | mission-controlno longer listed · | Desktop Commander |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 6 |
| Stars (GitHub) (differs) | 2 | 10 123 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 239 768 |
| Forks (GitHub) (differs) | 0 | 1 258 |
| Last release (differs) | Not published | 2026-10-22 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@wonderwhy-er/desktop-commander) |
| Transport (differs) | Not stated | stdio |
| Tools it declares (differs) | Not published | 26 |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not published | 7 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/cleanexpo/pi-dev-ops | github.com/wonderwhy-er/desktopcommandermcp |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
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
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.
Desktop Commander
MCP server for terminal commands, file operations, and process management
How to run each
mission-control
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Desktop Commander As a local MCP server: npm package
claude mcp add --transport stdio desktop-commander -- npx -y @wonderwhy-er/desktop-commander
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: mission-control · What it can do: Desktop Commander · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.