Ext Ops Panel
Open dashboard
Comparison

io.github.dynatrace-oss/Dynatrace-mcp vs VMware Debug

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). VMware Debug is an MCP server published by vmware-skills. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.dynatrace-oss/Dynatrace-mcpVMware Debug
Official MCP Registry Listed
Version: 2.1.2
Downloads/month (npm): 64 896
Downloads/week (npm): 12 165
Forks (GitHub): 27
Stars (GitHub): 137
Not marked · First seen
Listed
Version: 2.3.0
Downloads/month (PyPI): 1 118
Downloads/week (PyPI): 211
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:df93c6f1912a
Forks (GitHub): 27
Pulls (Docker Hub): 308 873
Stars (Docker Hub): 0
Stars (GitHub): 137
Not marked · First seen
Not listed

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

io.github.dynatrace-oss/Dynatrace-mcp vs VMware Debug
Factio.github.dynatrace-oss/Dynatrace-mcpVMware Debug
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)137 (better)1 (worse)
Pulls (Docker Hub) (differs)308 873No figure on Docker Hub
Forks (GitHub) (differs)27 (better)0 (worse)
Last release (differs)Not published2026-10-16
Where it runs (differs)On your machine (@dynatrace-oss/dynatrace-mcp-server)On your machine (vmware-debug)
Transportstdiostdio
Tools it declares (differs)18Not published
Environment variables it asks for (differs)5, secrets among them: 0Not published
Licence (differs)MITNot stated
Repository (differs)github.com/dynatrace-oss/dynatrace-mcpgithub.com/vmware-skills/vmware-debug
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.dynatrace-oss/Dynatrace-mcp

In its own words, on Official MCP Registry:

[DEPRECATED] Dynatrace MCP Server. Migrate to dynatrace-for-ai or Dynatrace Remote MCP Server.

VMware Debug

In its own words, on Official MCP Registry:

VMware incident timeline, root-cause routing, local case ledger; no vSphere access. 14 MCP tools.

How to run each

io.github.dynatrace-oss/Dynatrace-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "DT_ENVIRONMENT=<YOUR_DT_ENVIRONMENT>" --transport stdio dynatrace-mcp -- npx -y @dynatrace-oss/dynatrace-mcp-server

Requires: DT_ENVIRONMENT

VMware Debug As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio vmware-debug -- uvx vmware-debug mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of VMware Debug publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of VMware Debug publish no settings it asks for, so we do not compare settings.

What it can do: io.github.dynatrace-oss/Dynatrace-mcp · What it can do: VMware Debug · Compare two other plugins

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.

Where the data comes from: how the catalog is built