A
licenseB
qualityD
maintenanceEnables AI assistants to manage Proxmox VE infrastructure, including VMs, containers, storage, network, high availability, replication, SDN, and node administration.
100
2 npm
MIT
Proxmox MCP Server
Related Servers
Alternatives to Proxmox MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Proxmox VE virtual machines via MCP and OpenAPI, supporting operations like start, stop, clone, and snapshot.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to monitor and analyze Proxmox VE virtualization environments via the MCP protocol.MIT
- 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 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
TDQS
C2.9/5.0
Scored across 286 tools
Disambiguation3/5
Most tools have distinct resource/action names, but the 286-tool surface creates real overlap: e.g. list_vms vs. get_cluster_resources(type='vm'), list_storage vs. list_node_storage, and multiple firewall/HA/backup listing tools. Descriptions usually clarify the intended boundary, but agents will still face selection ambiguity at scale.
Naming Consistency4/5
The set is overwhelmingly snake_case and follows predictable verb_noun patterns such as list_vms, get_vm_status, create_container, and delete_ha_group. There are minor deviations like proxmox_api_raw, startall_node, and several vm_agent_* resource-first names, but the convention remains readable and mostly consistent.
Tool Count1/5
286 tools is an extreme mismatch for a single MCP server, even for a broad platform like Proxmox VE. The surface is effectively a raw API wrapper split into hundreds of endpoints, which makes tool discovery and selection impractical without strong grouping or routing.
Completeness4/5
Coverage is very broad across VMs, containers, nodes, storage, SDN, firewall, HA, Ceph, backup, users, ACLs, ACME, replication, tasks, and guest agents. Some secondary CRUD operations are missing or uneven, but the proxmox_api_raw fallback mitigates most dead ends.
Maintenance
ActivityActive
ResponsivenessSlow