A
licenseNot graded
qualityD
maintenanceEnables AI assistants to manage Proxmox VE infrastructure, including VMs, containers, storage, and cluster operations via natural language.
MIT
Unofficial-Proxmox-MCP
Related Servers
Alternatives to Unofficial-Proxmox-MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to manage Proxmox VE infrastructure, including VMs, containers, storage, network, high availability, replication, SDN, and node administration.10018 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to monitor and manage Proxmox VE infrastructure, including nodes, VMs, containers, storage, backups, and networking, via natural language.1MIT
- FlicenseNot gradedqualityCmaintenanceEnables 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.-
- AlicenseCqualityDmaintenanceEnables management of Proxmox VE environments, including VMs, containers, storage, and cluster operations through natural language.7649 npmMIT
- AlicenseAqualityBmaintenanceEnables natural language interaction with Proxmox VE clusters for managing VMs, containers, storage, and snapshots.2710 npm3MIT
TDQS
B3.4/5.0
Scored across 26 tools
Disambiguation4/5
Most tools are clearly separated by resource and action, such as list_nodes vs list_systems and create_vm vs clone_system. Minor ambiguity exists between pve_get_system and pve_get_guest_network because both can return network-related information, and pve_export_terraform partially overlaps with configuration retrieval.
Naming Consistency4/5
All tools use the pve_ snake_case prefix and nearly all follow a verb_noun pattern. The main exception is pve_lifecycle, which is noun-style rather than verb-style, but the naming remains highly predictable overall.
Tool Count4/5
With 26 tools, the set is above the typical 3–15 range, but the broad Proxmox domain includes many distinct operations. Each tool generally earns its place, though the surface is slightly heavy and some specialized tools could potentially be consolidated.
Completeness3/5
The core VM/container lifecycle is well covered, including create, clone, edit, resize, lifecycle actions, destroy, snapshots, and Terraform export. However, notable gaps remain: backup restore/delete, firewall rule deletion, migration, task tracking, and node/storage network administration are missing, creating several dead ends.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues