io.github.VictoriaMetrics-Community/mcp-victoriametrics vs VMware Debug
io.github.VictoriaMetrics-Community/mcp-victoriametrics is an MCP server published by VictoriaMetrics-Community. 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-27. 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
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.18.0 Forks (GitHub): 35 Stars (GitHub): 240 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:177f32eb9164 Forks (GitHub): 35 Stars (GitHub): 240 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
| Fact | io.github.VictoriaMetrics-Community/mcp-victoriametrics | VMware Debug |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 240 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 35 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | On your machine (ghcr.io/victoriametrics-community/mcp-victoriametrics:1.18.0) | On your machine (vmware-debug) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 20 | Not published |
| Environment variables it asks for (differs) | 9, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/victoriametrics-community/mcp-victoriametrics | github.com/vmware-skills/vmware-debug |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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.VictoriaMetrics-Community/mcp-victoriametrics
MCP Server for VictoriaMetrics. Provides integration with VictoriaMetrics API and documentation
VMware Debug
VMware incident timeline, root-cause routing, local case ledger; no vSphere access. 14 MCP tools.
How to run each
io.github.VictoriaMetrics-Community/mcp-victoriametrics As a local MCP server: Docker image
claude mcp add --env "VMC_API_KEY=<YOUR_VMC_API_KEY>" --env "VM_INSTANCE_BEARER_TOKEN=<YOUR_VM_INSTANCE_BEARER_TOKEN>" --env "VM_INSTANCE_ENTRYPOINT=<YOUR_VM_INSTANCE_ENTRYPOINT>" --env "VM_INSTANCE_TYPE=<YOUR_VM_INSTANCE_TYPE>" --transport stdio mcp-victoriametrics -- docker run -i --rm -e VMC_API_KEY -e VM_INSTANCE_BEARER_TOKEN -e VM_INSTANCE_ENTRYPOINT -e VM_INSTANCE_TYPE ghcr.io/victoriametrics-community/mcp-victoriametrics:1.18.0
Requires: VMC_API_KEY (secret), VM_INSTANCE_BEARER_TOKEN (secret), VM_INSTANCE_ENTRYPOINT, VM_INSTANCE_TYPE
VMware Debug As a local MCP server: PyPI package
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.VictoriaMetrics-Community/mcp-victoriametrics · 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.