Proxmox VE MCP server
Related Servers
Alternatives to Proxmox VE MCP server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables managing a Proxmox cluster through natural language chat, including VM/container inventory, power control, configuration changes, cloning, snapshots, network/firewall visibility, and running commands or writing files inside guests.-
- FlicenseBqualityDmaintenanceEnables natural language management of Proxmox VE VMs and containers, including lifecycle, snapshots, cloud-init, and secure multi-step automation workflows.65-
- AlicenseAqualityBmaintenanceEnables natural language interaction with Proxmox VE clusters for managing VMs, containers, storage, and snapshots.2711 npm3MIT
- AlicenseCqualityDmaintenanceEnables management of Proxmox VE environments, including VMs, containers, storage, and cluster operations through natural language.7653 npmMIT
- AlicenseBqualityBmaintenanceEnables AI assistants to inspect and manage Proxmox VE clusters conversationally, including provisioning VMs and LXC containers, resizing disks, handling snapshots and backups, configuring Cloud-Init and firewall rules, and executing guest commands with mandatory confirmation safeguards.26MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Proxmox VE infrastructure, including VMs, containers, storage, and cluster operations via natural language.MIT
TDQS
Scored across 6 tools
Each tool targets a distinct concern: health triage (needs_attention), cluster-wide status (overview), guest listing (find_guests), single-guest drill-down (guest_details), power actions, and snapshots. The only mild overlaps are needs_attention vs overview (both aggregate health) and find_guests vs guest_details (list vs detail), but the descriptions make the boundaries clear enough.
All names use snake_case, but the conventions are mixed: find_guests/power_guest/snapshot_guest are verb_noun, guest_details is noun_noun, and needs_attention/overview are bare noun phrases with no verb. It remains readable, but the pattern is not predictable across the set.
Six tools is a reasonable, well-scoped set for a Proxmox monitoring/ops surface, and each tool clearly earns its place. It is on the lean side for a broad hypervisor domain, but not thin enough to be a problem.
Read paths (overview, guest listing/detail, attention scan) and two guarded write actions (power, snapshot) are covered, but major lifecycle operations are missing: create/clone/delete guest, backup job creation/run/restore, and storage or migration actions. An agent asked to provision or remove a VM, or manage backups, would hit a dead end.