alpacon-mcp vs Proxmox Ops
alpacon-mcp is an MCP server published by alpacax. Marketplaces we read that list it: 1 (PyPI (MCP servers)). Proxmox Ops is an MCP server published by derdennis1012. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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 |  alpacon-mcp |  Proxmox Ops |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 1.25.0 Downloads/month (PyPI): 2 602 Downloads/week (PyPI): 601 Forks (GitHub): 1 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 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 | alpacon-mcp | Proxmox Ops |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release (differs) | 2026-11-07 | Not published |
| Where it runs (differs) | On your machine (alpacon-mcp) | On your machine (proxmox-ops-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 6, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/alpacax/alpacon-mcp | github.com/derdennis1012/proxmox-ops-mcp |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-28 |
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
alpacon-mcp
Let AI agents operate your infrastructure under your control. An MCP server that connects agents to Alpacon, which checks each command at runtime, holds risky ones for human approval, and records them for audit.
Proxmox Ops
Proxmox VE diagnostics, backup audits, maintenance planning and guarded VM operations.
How to run each
alpacon-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Proxmox Ops As a local MCP server: PyPI package
claude mcp add --env "PROXMOX_HOST=<YOUR_PROXMOX_HOST>" --env "PROXMOX_TOKEN_ID=<YOUR_PROXMOX_TOKEN_ID>" --env "PROXMOX_TOKEN_SECRET=<YOUR_PROXMOX_TOKEN_SECRET>" --transport stdio proxmox-ops-mcp -- uvx proxmox-ops-mcpRequires: PROXMOX_HOST, PROXMOX_TOKEN_ID, PROXMOX_TOKEN_SECRET (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of alpacon-mcp publish no settings it asks for, so we do not compare settings.
What it can do: alpacon-mcp · What it can do: Proxmox Ops · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). 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.