proxmox-mcps
Related Servers
Alternatives to proxmox-mcps
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Proxmox VE infrastructure, including VMs, containers, storage, and cluster operations via natural language.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to monitor and manage Proxmox VE infrastructure, including nodes, VMs, containers, storage, backups, and networking, via natural language.1MIT
- AlicenseCqualityDmaintenanceEnables management of Proxmox VE environments, including VMs, containers, storage, and cluster operations through natural language.7658 npmMIT
- AlicenseAqualityBmaintenanceEnables natural language interaction with Proxmox VE clusters for managing VMs, containers, storage, and snapshots.279 npm3MIT
- AlicenseCqualityAmaintenanceEnables AI assistants and MCP clients to manage Proxmox VE infrastructure, including virtual machines, containers, storage, networking, and high availability through a standardized interface.286287 PyPI205Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to monitor and analyze Proxmox VE virtualization environments via the MCP protocol.MIT
TDQS
Scored across 195 tools
Most tools have distinct purposes, but there are some close pairs like get_container_rrd vs get_container_rrddata and get_vm_rrd vs get_vm_rrddata that could cause confusion. The aliasing of list_storages to get_storage adds minor ambiguity. Overall, the descriptions help disambiguate most tools.
All tool names follow a consistent snake_case verb_noun or noun_verb pattern. The naming is predictable and organized by resource type (e.g., get_vm_*, create_container_*, update_storage_*). There are no deviations from the pattern.
With 195 tools, the server is excessively large. While Proxmox is a complex system, the tool count far exceeds the typical well-scoped range (3-15). It would be overwhelming for agents and would benefit from splitting into smaller, focused servers.
The tool set covers virtually all aspects of Proxmox management: VMs, containers, storage, SDN, HA, backups, snapshots, replication, node management, firewall, and QEMU guest agent. There are no obvious gaps in lifecycle coverage for the domain addressed.