mission-control vs Dynatrace
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. Dynatrace is a plugin bundle for AI coding tools published by Dynatrace. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-27. 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 |   Dynatrace | |
|---|---|---|
| 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 |
| Claude Code: claude-plugins-official | Not listed | Listed Version: 8.0.1 Forks (GitHub): 38 Stars (GitHub): 169 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 7.0.0 Forks (GitHub): 38 Stars (GitHub): 169 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 · | Dynatrace |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 3 |
| Stars (GitHub) (differs) | 2 | 169 |
| Forks (GitHub) (differs) | 0 | 38 |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs | Installs as a plugin bundle | Installs as a plugin bundle |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not published | 35 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/cleanexpo/pi-dev-ops | github.com/dynatrace/dynatrace-for-ai |
| Changes in the last 7 days | 0 | 0 |
| 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 — monitors, incidents, heartbeats, maintenance windows, status page incidents
-
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.
Dynatrace
Dynatrace observability skills: DQL query patterns, application and infrastructure monitoring, log analysis, problem investigation, and incident response workflows, with the Dynatrace MCP server for live platform access.
How to run each
mission-control
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Dynatrace As a Claude Code plugin
/plugin install dynatrace@claude-plugins-officialCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: mission-control · What it can do: Dynatrace · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. 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.