A
licenseA
qualityB
maintenanceEnables natural language interaction with Proxmox VE clusters for managing VMs, containers, storage, and snapshots.
27
10 npm
3
MIT
Proxmox VE MCP Server
by MTDEV2312
Related Servers
Alternatives to Proxmox VE MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceEnables management of Proxmox VE environments, including VMs, containers, storage, and cluster operations through natural language.7653 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Proxmox VE infrastructure, including VMs, containers, storage, and cluster operations via natural language.MIT
- 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.-
- AlicenseBqualityBmaintenanceEnables AI assistants to inspect and manage Proxmox VE clusters conversationally, including provisioning VMs and LXC containers, resizing disks, handling snapshots and backups, configuring Cloud-Init and firewall rules, and executing guest commands with mandatory confirmation safeguards.26MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to monitor and manage Proxmox VE infrastructure, including nodes, VMs, containers, storage, backups, and networking, via natural language.1MIT
TDQS
B3.2/5.0
Scored across 65 tools
Disambiguation5/5
Each tool targets a distinct action and resource type (VM, container, storage, cluster, etc.). Overlapping operations like stop_vm vs shutdown_vm vs pause_vm are clearly differentiated by their descriptions, and workflow tools are uniquely named and scoped.
Naming Consistency4/5
The majority of tools follow a consistent verb_noun pattern (e.g., create_vm, delete_vm, list_snapshots_container). However, several tools deviate with noun-first names like storage_content, task_status, and cluster_health, which mix conventions and slightly reduce predictability.
Tool Count1/5
With 65 tools, this server is extremely heavy and exceeds the typical scope for a single MCP server. Even for a complex domain like Proxmox, the number is overwhelming and would benefit from splitting into smaller, focused servers (e.g., vm_management, container_management, cluster_management).
Completeness5/5
The tool set provides comprehensive lifecycle coverage for VMs, containers, storage, cluster health, nodes, and security, including create, read, update, delete, snapshots, and operational actions. Workflow tools for provisioning, backup, and cluster checks fill higher-level gaps, leaving few obvious missing operations.
Maintenance
ActivityInactive
ResponsivenessNo recent community issues