No user-submitted related servers found.
Scored across 166 tools
The tools are highly specific and well-differentiated by resource type (VM, container, node, storage, etc.) and action (create, get, list, update, delete). Overlap is minimal, with clear distinctions like pve_get_vm_config vs pve_get_vm_status, and pve_list_vms vs pve_list_containers. The sheer number of tools might cause some confusion, but each serves a distinct purpose within the Proxmox domain.
Naming is exceptionally consistent throughout the entire set. Every tool follows the pattern pve_<action>_<resource> or pve_<action>_<resource>_<subresource>, using snake_case uniformly. Verbs like create, get, list, update, delete are applied predictably across resources, making the toolset highly readable and systematic.
With 166 tools, the count is excessive for an MCP server, far beyond the typical well-scoped range of 3-15 tools. While Proxmox is a complex system, this many tools will overwhelm agents, increase cognitive load, and likely lead to misselection or inefficiency. The scope feels more like a direct API mapping than a curated tool surface.
The toolset provides comprehensive coverage of the Proxmox VE domain, including full CRUD operations for VMs, containers, storage, users, groups, firewall rules, backups, replication, HA, and node management. It supports lifecycle actions (start, stop, migrate, snapshot) and administrative tasks (network, certificates, services), leaving no obvious gaps for core workflows.