A
licenseB
qualityC
maintenanceEnables AI assistants to manage Proxmox VE infrastructure, including VMs, containers, storage, network, high availability, replication, SDN, and node administration.
100
16 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 gradedqualityCmaintenanceMCP server for Proxmox VE that enables AI assistants to inspect and manage LXC containers, VMs, snapshots, and resource pools via the Proxmox API.-
- AlicenseNot gradedqualityCmaintenanceEnables 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.6/5.0
Scored across 286 tools
Disambiguation2/5
With 286 tools, several near-duplicates exist: get_ha_status vs get_ha_manager_status, migrate_ha_resource vs relocate_ha_resource, get_cluster_config vs get_cluster_config_nodes/totem/join_info, and list_backup_file_restore vs list_file_restore. Descriptions help for many reads, but the boundaries between several tool families are unclear enough to cause misselection.
Naming Consistency2/5
Most tools follow a verb_noun pattern, but conventions are mixed: set_* vs update_*, list_* vs get_* are used inconsistently, vm_agent_* tools invert the verb placement, and oddities like get_node_apt_update, create_vzdump, and proxmox_api_raw break the pattern. The naming is mostly readable but not predictable enough for a set this large.
Tool Count1/5
286 tools is an extreme count for any MCP server and will overwhelm context and tool selection. Many operations could be consolidated, and the included raw API suggests the surface could have been much smaller.
Completeness3/5
Core VM, container, storage, backup, user, and HA workflows are well covered, but several subdomains have notable gaps: no update for replication jobs, no CRUD for node firewall rules, no update/delete for SDN subnets, no delete for Ceph OSDs/pools, and partial ACME/metric/realm management. The proxmox_api_raw tool provides a workaround, but it is not a first-class replacement for missing lifecycle operations.
Maintenance
ActivityActive
ResponsivenessWithin a week