A
licenseB
qualityD
maintenanceEnables AI assistants to manage Proxmox VE infrastructure, including VMs, containers, storage, network, high availability, replication, SDN, and node administration.
100
15 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.7/5.0
Scored across 286 tools
Disambiguation2/5
The resource/action prefixes help, but the scale creates overlapping lookalikes such as get_ha_status vs get_ha_manager_status, migrate_ha_resource vs relocate_ha_resource, and list_backup_file_restore vs list_file_restore. An agent selecting among 286 tools will frequently face ambiguous boundaries, even though many tools are individually distinct.
Naming Consistency3/5
Most tools follow a clear list_/get_/create_/update_/delete_ + resource pattern, and related CRUD groups are easy to spot. However, there are notable deviations like vm_agent_exec, proxmox_api_raw, wakeonlan_node, and startall_node/stopall_node that break the otherwise predictable convention.
Tool Count1/5
286 tools is far beyond a coherent MCP surface and exceeds any reasonable scope for fast and accurate tool selection. Even a comprehensive hypervisor API would be better served by consolidated endpoints or a smaller set of higher-level operations.
Completeness4/5
The server covers nearly every Proxmox VE domain with CRUD/lifecycle operations for VMs, containers, storage, users, HA, backups, SDN, firewall, and Ceph. Minor gaps exist, such as missing updates for some SDN/firewall alias resources and missing deletion for some Ceph objects, but the breadth and raw API fallback prevent major dead ends.
Maintenance
ActivityActive
ResponsivenessSlow