metro vs io.github.dynatrace-oss/Dynatrace-mcp
metro is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
metro is a plugin bundle for AI coding tools published by Bonustrack. No marketplace we read lists it any more. io.github.dynatrace-oss/Dynatrace-mcp is an MCP server published by dynatrace-oss. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). 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 |  io.github.dynatrace-oss/Dynatrace-mcp | |
|---|---|---|
| Community marketplace bonustrack/metro | Removed on 2026-10-15 Version: 0.9.19 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.1.2 Downloads/month (npm): 77 071 Downloads/week (npm): 16 273 Forks (GitHub): 26 Stars (GitHub): 137 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:df93c6f1912a Forks (GitHub): 26 Pulls (Docker Hub): 306 497 Stars (Docker Hub): 0 Stars (GitHub): 137 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 | metrono longer listed · | io.github.dynatrace-oss/Dynatrace-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 0 | 137 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 306 497 |
| Forks (GitHub) (differs) | 0 | 26 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@dynatrace-oss/dynatrace-mcp-server) |
| Transport (differs) | Not stated | stdio |
| Tools it declares (differs) | Not published | 18 |
| Environment variables it asks for (differs) | Not published | 5, secrets among them: 0 |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/bonustrack/metro | github.com/dynatrace-oss/dynatrace-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 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 metro
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Universal MCP gateway with Meta-MCP discovery, routing, and REST API capabilities.
-
Hands-on test results for 560+ remote MCP connectors: does it work, how to sign in, what breaks.
-
Thin MOVA MCP proxy for bindings, transport resolution, and upstream tools/call execution.
-
See what an MCP connector can do for your business, get a scenario map, book a consultation.
-
Meta-MCP gateway: search, inspect and call any MCP server from the public registries.
-
Search thousands of MCP connectors from the AgentHotspot marketplace via your AI agent.
What each says it does
metro
Every connector on this box as its own MCP server through metro's local relay, the orchestrator guard, and the standing rules loaded at session start.
io.github.dynatrace-oss/Dynatrace-mcp
[DEPRECATED] Dynatrace MCP Server. Migrate to dynatrace-for-ai or Dynatrace Remote MCP Server.
How to run each
metro
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.dynatrace-oss/Dynatrace-mcp As a local MCP server: npm package
claude mcp add --env "DT_ENVIRONMENT=<YOUR_DT_ENVIRONMENT>" --transport stdio dynatrace-mcp -- npx -y @dynatrace-oss/dynatrace-mcp-serverRequires: DT_ENVIRONMENT
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of metro publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of metro publish no settings it asks for, so we do not compare settings.
What it can do: metro · What it can do: io.github.dynatrace-oss/Dynatrace-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. 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.