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 gradedqualityDmaintenanceMCP 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.104MIT
- AlicenseAqualityDmaintenanceMCP server for managing Proxmox VE resources, VM/CT lifecycle, snapshots, backups, and clones via natural language.23MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for full Proxmox VE management - VMs, containers, storage, backups, networking.2MIT
- AlicenseNot gradedqualityBmaintenanceEnterprise MCP server for Proxmox VE, offering 298 tools to manage VMs, containers, storage, cluster, firewall, and more via natural language.37 npmMIT
TDQS
A3.5/5.0
Scored across 43 tools
Disambiguation4/5
Most tools map to a distinct resource and action, and descriptions clarify overlaps such as vm_get/vm_config and vm_stop/vm_shutdown/vm_reboot. Some broader inventory tools overlap (cluster_resources vs node_list/vm_list/ct_list), but an agent can generally distinguish intended use.
Naming Consistency4/5
Names are almost entirely snake_case with predictable resource prefixes and verb/action patterns (vm_start, ct_stop, node_list, task_status). Minor deviations like vm_list_snapshots vs vm_snapshot_create and vm_firewall_rules_list keep it from perfect consistency.
Tool Count2/5
43 tools is well beyond the 25+ threshold and includes redundant read surfaces such as cluster_resources vs individual list tools, plus backup_list overlapping storage_content. Proxmox is broad, but the set still feels over-expanded and would benefit from consolidation.
Completeness3/5
Core VM lifecycle coverage is strong (start/stop/shutdown/reboot/clone/migrate/snapshot/backup/restore/disk operations), but CT coverage is mostly limited to list/start/stop. VM creation from scratch and firewall rule write operations are absent, leaving notable lifecycle gaps.
Maintenance
ActivityActive
ResponsivenessSlow