Ext Ops Panel
Open dashboard
Comparison

KVM/libvirt VMs and backups (Fedora) vs Cursor Proxmox MCP

KVM/libvirt VMs and backups (Fedora) is an MCP server published by amineutron. Marketplaces we read that list it: 1 (Official MCP Registry). Cursor Proxmox MCP is an MCP server published by hackmods. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
MarketplaceKVM/libvirt VMs and backups (Fedora)Cursor Proxmox MCP
Official MCP Registry Listed
Version: 1.3.0
Downloads/month (npm): 867
Downloads/week (npm): 43
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.9.0
Downloads/month (PyPI): 183
Downloads/week (PyPI): 55
Forks (GitHub): 0
Stars (GitHub): 1
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

KVM/libvirt VMs and backups (Fedora) vs Cursor Proxmox MCP
FactKVM/libvirt VMs and backups (Fedora)Cursor Proxmox MCP
Marketplaces that list it11
Stars (GitHub)11
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (fedora-agents-mcp)On your machine (cursor-proxmox-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 04, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/amineutron/fedora-agentsgithub.com/hackmods/cursor-proxmox-mcp
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

KVM/libvirt VMs and backups (Fedora)

In its own words, on Official MCP Registry:

Manage local KVM/libvirt VMs and Timeshift/Borg backups on Fedora: start, stop, clone, snapshot.

Cursor Proxmox MCP

In its own words, on Official MCP Registry:

Manage Proxmox VE via Cursor: QEMU, LXC, storage, HA, firewall, access.

How to run each

KVM/libvirt VMs and backups (Fedora) As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio fedora-agents -- npx -y fedora-agents-mcp

Cursor Proxmox MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --env "PROXMOX_MCP_CONFIG=<YOUR_PROXMOX_MCP_CONFIG>" --env "PROXMOX_TOKEN_VALUE=<YOUR_PROXMOX_TOKEN_VALUE>" --transport stdio cursor-proxmox-mcp -- uvx cursor-proxmox-mcp

Requires: PROXMOX_MCP_CONFIG, PROXMOX_TOKEN_VALUE (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

Only KVM/libvirt VMs and backups (Fedora) asks for

  • MCP_AGENTS_LOG_DIR

Only Cursor Proxmox MCP asks for

  • PROXMOX_MCP_CONFIG
  • PROXMOX_MCP_LOG_LEVEL
  • PROXMOX_MCP_VERBOSE
  • PROXMOX_TOKEN_VALUE (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: KVM/libvirt VMs and backups (Fedora) · What it can do: Cursor Proxmox MCP · Compare two other plugins

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.

Where the data comes from: how the catalog is built