Proxmox VE vs @xen-orchestra/mcp
Proxmox VE is an MCP server published by GethosTheWalrus. Marketplaces we read that list it: 2 (Docker MCP Catalog, PyPI (MCP servers)). @xen-orchestra/mcp is an MCP server published by @xen-orchestra. Marketplaces we read that list it: 1 (npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. 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 |   Proxmox VE | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:6e30b4d837b2 Forks (GitHub): 18 Pulls (Docker Hub): 41 456 Stars (Docker Hub): 3 Stars (GitHub): 232 Not marked · First seen |
Not listed |
| PyPI (MCP servers) | Listed Version: 1.4.4 Downloads/month (PyPI): 2 017 Downloads/week (PyPI): 457 Forks (GitHub): 18 Stars (GitHub): 232 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Not listed | Listed Version: 1.4.3 Downloads/month (npm): 6 569 Downloads/week (npm): 2 004 Forks (GitHub): 330 Stars (GitHub): 996 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 | Proxmox VE | @xen-orchestra/mcp |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 232 (worse) | 996 (better) |
| Pulls (Docker Hub) (differs) | 41 456 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 18 (worse) | 330 (better) |
| Last release (differs) | 2026-10-19 | Not published |
| Where it runs (differs) | On your machine (mcp/proxmox) | On your machine (@xen-orchestra/mcp) |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 286 | Not published |
| Environment variables it asks for (differs) | 8, secrets among them: 2 | Not published |
| Licence (differs) | NOASSERTION | AGPL-3.0-or-later |
| Repository (differs) | github.com/gethosthewalrus/proxmox-mcp | github.com/vatesfr/xen-orchestra |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
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
Proxmox VE
Manage Proxmox VE infrastructure including virtual machines, containers, storage, networking, firewall rules, high availability, and more.
@xen-orchestra/mcp
MCP server for Xen Orchestra — allows AI assistants to query and manage XO infrastructure
How to run each
Proxmox VE As a local MCP server: Docker image
claude mcp add --env "PROXMOX_PASSWORD=<YOUR_PROXMOX_PASSWORD>" --env "PROXMOX_TOKEN_VALUE=<YOUR_PROXMOX_TOKEN_VALUE>" --transport stdio proxmox -- docker run -i --rm -e PROXMOX_PASSWORD -e PROXMOX_TOKEN_VALUE mcp/proxmoxRequires: PROXMOX_PASSWORD (secret), PROXMOX_TOKEN_VALUE (secret)
@xen-orchestra/mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of @xen-orchestra/mcp publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of @xen-orchestra/mcp publish no settings it asks for, so we do not compare settings.
What it can do: Proxmox VE · What it can do: @xen-orchestra/mcp · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the Python Package Index (pypi.org). Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.