Proxmox VE vs Axcient x360Recover
Proxmox VE is an MCP server published by GethosTheWalrus. Marketplaces we read that list it: 1 (Docker MCP Catalog). Axcient x360Recover is an MCP server published by WYRE-AI. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:6e30b4d837b2 Forks (GitHub): 15 Pulls (Docker Hub): 33 961 Stars (Docker Hub): 3 Stars (GitHub): 210 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.4 Forks (GitHub): 0 Stars (GitHub): 0 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 | Axcient x360Recover |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 210 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 33 961 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 15 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | On your machine (mcp/proxmox) | On your machine (ghcr.io/wyre-ai/axcient-mcp:v1.0.4) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 286 | Not published |
| Environment variables it asks for (differs) | 8, secrets among them: 2 | 4, secrets among them: 1 |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/gethosthewalrus/proxmox-mcp | github.com/wyre-ai/axcient-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| 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
Proxmox VE
Manage Proxmox VE infrastructure including virtual machines, containers, storage, networking, firewall rules, high availability, and more.
Axcient x360Recover
MCP server for Axcient x360Recover — BCDR clients, devices, jobs, vaults, and appliances.
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/proxmox
Requires: PROXMOX_PASSWORD (secret), PROXMOX_TOKEN_VALUE (secret)
Axcient x360Recover As a local MCP server: Docker image
claude mcp add --env "AXCIENT_API_KEY=<YOUR_AXCIENT_API_KEY>" --transport stdio axcient-mcp -- docker run -i --rm -e AXCIENT_API_KEY ghcr.io/wyre-ai/axcient-mcp:v1.0.4
Requires: AXCIENT_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Axcient x360Recover publish no list of tools, so we do not compare tools.
Settings each asks for
Only Proxmox VE asks for
PROXMOX_HOSTPROXMOX_PASSWORD (secret)PROXMOX_PORTPROXMOX_TIMEOUTPROXMOX_TOKEN_NAMEPROXMOX_TOKEN_VALUE (secret)PROXMOX_USERPROXMOX_VERIFY_SSL
Only Axcient x360Recover asks for
AUTH_MODEAXCIENT_API_KEY (secret)LOG_LEVELMCP_TRANSPORT
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Proxmox VE · What it can do: Axcient x360Recover · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.