A
licenseNot graded
qualityA
maintenanceA powerful and flexible Kubernetes MCP server implementation with support for OpenShift.
2,208
Go
Apache 2.0
proxmox-mcp
by akmalovaa
Related Servers
Alternatives to proxmox-mcp
- FlicenseAqualityDmaintenanceProvides tools to manage Proxmox VE clusters via Claude Code, enabling listing nodes, VMs, templates, power actions, and creation of LXC containers and VMs through the Proxmox REST API.1027 npm-
- AlicenseNot gradedqualityDmaintenanceMCP server for full Proxmox VE management - VMs, containers, storage, backups, networking.2MIT
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for Proxmox VE: monitor and manage your cluster, VMs, containers, storage and backups from Claude and other AI assisInstants. Runs in docker.1MIT
- AlicenseNot gradedqualityAmaintenanceAn open-source MCP server for managing Proxmox environments, including nodes, virtual machines, and containers. It enables users to perform inventory checks, status monitoring, and control operations directly through MCP-compatible tools.306 npm1MIT
- AlicenseBqualityCmaintenanceComprehensive MCP server for Proxmox VE with 68 tools and 4 resources covering VMs, containers, storage, networking, clusters, HA, backups, firewall, and access control.6827 npmMIT
- AlicenseCqualityCmaintenanceA comprehensive MCP server providing 92 tools for managing Proxmox Virtual Environment, including QEMU VMs and LXC containers.9264 npm6MIT
- AlicenseBqualityCmaintenanceAn MCP server that exposes Proxmox VE node/cluster as tools for MCP clients, enabling management of VMs and containers including power control, resource reconfiguration, snapshots, and backups.20MIT
- AlicenseAqualityBmaintenanceMCP server for Proxmox VE and Proxmox Datacenter Manager, covering every API endpoint via six consolidated tools for list, describe, and call operations with a read-only safety gate.616 npm2AGPL 3.0
TDQS
A3.8/5.0
Scored across 38 tools
Disambiguation5/5
Each tool targets a distinct resource type (VM, container, node, storage, cluster) and action, with no overlap. For example, VM operations are separate from container operations, and snapshot operations are distinct from lifecycle operations.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern using snake_case, e.g., list_vms, get_vm_config, start_container. The naming is predictable and mirrors each other for VMs and containers.
Tool Count4/5
38 tools is on the higher end but justified for a comprehensive Proxmox management server covering VMs, containers, snapshots, cluster, nodes, storage, and tasks. Minor redundancy exists (e.g., separate get and list for VMs and containers) but overall scope is appropriate.
Completeness2/5
The tool set lacks essential CRUD operations: there is no create VM or container (only clone_vm exists), no delete VM or container, and no update/configure tools. This leaves significant gaps in managing the full lifecycle of resources.
Maintenance
ActivitySlowing
ResponsivenessNo issues