proxmox-ops-mcp
Related Servers
Alternatives to proxmox-ops-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables natural-language access to Proxmox VE clusters for checking node, VM, storage, and task status and for performing confirmed VM power, clone, snapshot, configuration, and deletion operations through MCP clients.23MIT
- FlicenseNot gradedqualityDmaintenanceProvides read-only Proxmox cluster oversight and configuration compliance checks through MCP, covering health, inventory, storage, backups, snapshots, and updates.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to manage VMs, containers, storage, backups, snapshots, networking, firewall, HA and tasks across multiple Proxmox VE hosts or clusters through the Proxmox API. Token secrets are pulled from an OS keychain, secret manager, file or command, with read-only modes, per-tool switches and confirmation before destructive actions.524 npmMIT
- 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
- AlicenseAqualityCmaintenanceEnables MCP-compatible clients like Claude Desktop, Claude Code, Codex, and local-model hosts to inspect Proxmox VE clusters, nodes, VMs, containers, storage, snapshots, and tasks, with opt-in write operations for starting, stopping, cloning, backing up, and migrating guests. Read-only by default, it supports both stdio and Streamable HTTP transports.14MIT
- AlicenseAqualityDmaintenanceEnables LLM agents to monitor and manage a Proxmox VE cluster, including cluster status, VM/container lifecycle, and node actions via MCP tools.8MIT
TDQS
Scored across 13 tools
Most tools target clearly distinct resources or diagnostic concerns: cluster, Ceph, storage, node comparison, guests, tasks, backups, placement, and evacuation. There is some overlap between cluster_health, ceph_health, and storage_health around storage fill and health checks, but descriptions mostly clarify that cluster_health is a broad first-stop while the others are focused deep dives.
All names use snake_case and are readable, but the naming convention is mixed: action-oriented names like list_nodes, compare_nodes, get_guest, recommend_placement, and plan_node_evacuation coexist with noun-based names like ceph_health, storage_health, cluster_health, backup_audit, and recent_task_failures. The inconsistency is understandable but prevents a fully predictable pattern.
Thirteen tools is well within a reasonable range for a broad Proxmox operations/diagnostics server. Each tool covers a distinct operational concern such as cluster health, storage health, backup auditing, placement, or evacuation planning, and none appears redundant.
The surface covers the main diagnostic and planning areas for Proxmox operations: cluster/node/Ceph/storage health, guest listing and inspection, task status and failures, backup auditing, maintenance status, placement recommendation, and evacuation planning. Minor gaps include network health, deeper HA state inspection, and any execution-oriented guest lifecycle operations, though the latter may be intentionally out of scope for this diagnostic/planning server.