A
licenseNot graded
qualityC
maintenanceMCP server that lets an AI agent manage Proxmox VE in natural language, with policy-driven security, read-only mode, two-step confirmations, and audit logging.
MIT
io.github.AIops-tools/proxmox-aiops
by AIops-tools
Related Servers
Alternatives to io.github.AIops-tools/proxmox-aiops
No user-submitted related servers found.
Related Servers
- 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.-
- AlicenseBqualityCmaintenanceA Model Context Protocol (MCP) server for Proxmox Virtual Environment that enables AI assistants to manage virtual machines, containers, nodes, and resources through natural language interactions.103MIT
- AlicenseAqualityCmaintenanceMCP server for managing Proxmox VE resources, VM/CT lifecycle, snapshots, backups, and clones via natural language.23MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for full Proxmox VE management - VMs, containers, storage, backups, networking.1MIT
- AlicenseNot gradedqualityBmaintenanceEnterprise MCP server for Proxmox VE, offering 298 tools to manage VMs, containers, storage, cluster, firewall, and more via natural language.94 npmMIT
TDQS
A3.6/5.0
Scored across 43 tools
Disambiguation4/5
The tool set has many near-neighbor pairs (cluster_resources/vm_list, storage_content/backup_list, ha_status/ha_resource_list), but the descriptions consistently call out the boundaries and use prefixes (vm_, ct_, node_, cluster_) to separate resource domains. An agent can usually pick the right tool with the descriptions, though the large number of overlapping list/health views creates a small risk of misselection.
Naming Consistency3/5
Names are readable and mostly resource-prefixed, but conventions are mixed: list is sometimes a suffix (backup_list, vm_list) and sometimes infixed (vm_list_snapshots), reads use list/get/status interchangeably, and writes vary between vm_start and backup_restore / vm_snapshot_rollback. This is not chaotic, but it is inconsistent enough to slow tool selection.
Tool Count2/5
43 tools is well past the 16–25 'heavy' range and into the too-many band, even for a broad platform like Proxmox. The large surface increases navigation and selection overhead for an agent.
Completeness3/5
VM lifecycle, snapshots, backup/restore, migration, and health analysis are well covered. However there is no VM/CT create (only clone), no CT delete or reconfigure, no firewall rule writes, and no backup deletion or HA/pool/storage management, which leaves notable operational gaps.
Maintenance
ActivityActive
ResponsivenessSlow