mission-control vs Action1 MCP
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. Action1 MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-21. 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 |   Action1 MCP | |
|---|---|---|
| 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.1.7 Forks (GitHub): 13 Stars (GitHub): 61 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 · | Action1 MCP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 2 | 61 |
| Forks (GitHub) (differs) | 0 | 13 |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (https://github.com/Servosity/msp-skills/releases/download/action1-v0.1.7/action1-mcp.mcpb) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 6, secrets among them: 3 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/cleanexpo/pi-dev-ops | github.com/servosity/msp-skills |
| Changes in the last 7 days (differs) | 4 | 3 |
| 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
-
Read-only agent radar, weekly editions, sourced guides, scenario choices and revision sync.
-
unifi io.github.us-all/unifi
UniFi semantic-analysis MCP — fleet health, anomaly detection, cross-site analytics
-
Fleet-wide Cove Data Protection backup health, billing, and storage trends from your terminal.
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.
Action1 MCP
Every Action1 endpoint, plus fleet-wide patch and vulnerability views across all your organizations.
How to run each
mission-control
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Action1 MCP As a Claude Code plugin
/plugin marketplace add servosity/msp-skills
/plugin install action1@msp-skillsRequires: ACTION1_CLIENT_ID (secret), ACTION1_CLIENT_SECRET (secret), ACTION1_OAUTH2 (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of mission-control publish no settings it asks for, so we do not compare settings.
What it can do: mission-control · What it can do: Action1 MCP · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.