proxmox-mcp
Related Servers
Alternatives to proxmox-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for Proxmox VE that enables AI assistants to inspect and manage LXC containers, VMs, snapshots, and resource pools via the Proxmox API.-
- AlicenseNot gradedqualityCmaintenanceA powerful, lightweight Model Context Protocol (MCP) server built in Python that enables Artificial Intelligence assistants (Claude Desktop, Cursor, Antigravity, Claude Code, etc.) to manage and monitor your Proxmox VE cluster using natural language.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for managing Proxmox VE virtualization infrastructure, providing tools for VMs, containers, snapshots, storage, cluster nodes, and tasks. Compatible with Claude Desktop, Cline, and other MCP clients via natural language.MIT
- AlicenseAqualityBmaintenanceMCP server for managing Proxmox VE clusters — provision VMs and containers, manage snapshots and backups, execute commands, browse storage, and monitor resources through natural language37289 PyPI18MIT
- AlicenseAqualityDmaintenanceMCP server for managing Proxmox VE resources, VM/CT lifecycle, snapshots, backups, and clones via natural language.23MIT
- AlicenseAqualityBmaintenanceMinimal MCP server for Proxmox VE — 38 tools for nodes, VMs, LXC, storage, and snapshots. Read-only by default, single Docker image, multi-arch.3881 PyPI7MIT
TDQS
Scored across 156 tools
There is real surface overlap — list_guests vs list_vms vs list_containers vs list_resources, get_node_syslog vs get_node_journal, list_snapshots vs list_all_snapshots, node_status vs node_stats vs cluster_status vs capacity_report — but nearly every description explicitly states when to prefer a sibling tool (e.g. 'For VMs and containers together use proxmox_list_guests'). With 156 tools the sheer number of near-neighbours means a few misselections are likely, but boundaries are documented rather than blurred.
Every tool follows the same proxmox_<verb>_<noun> pattern with a small, predictable verb set (get, list, check, save, update, delete, apply, scan, simulate, wait_for). Domain nouns are used consistently across resources (ceph_, sdn_, firewall_, ha_, node_, vm_, container_). No camelCase or ad-hoc naming anywhere.
156 tools is far beyond what an agent can hold in context comfortably, even though the Proxmox domain is genuinely vast (nodes, VMs, containers, storage, Ceph, SDN, firewall, HA, auth, backup, replication, notifications). Most tools are non-redundant and well-scoped individually, but the flat single-level namespace offers no grouping or progressive disclosure, so discovery cost is high.
Coverage is unusually broad: full read/write lifecycles for guests, storage, Ceph, SDN, firewall, HA, users/ACLs, backups, replication and notifications, plus safety pre-checks (check_ceph_safety, check_vm_migration) and dry-runs (preview_backup_prune, get_sdn_pending_diff). Minor gaps remain — package updates explicitly cannot be installed, SDN fabrics and route policies are read-only, and there is no guest console/exec or VNC access — but these are narrow and documented rather than dead ends.