Proxmox VE MCP
Related Servers
Alternatives to Proxmox VE MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for managing Proxmox VE virtualization infrastructure, providing tools for VMs, containers, snapshots, storage, cluster nodes, and tasks. Compatible with Claude Desktop, Cline, and other MCP clients via natural language.70 npmMIT
- AlicenseNot gradedqualityAmaintenanceA safety-gated, local stdio MCP server for the Proxmox VE API, enabling the management of VMs, containers, storage, and tasks through natural language via MCP hosts.18 npm1MIT
- FlicenseNot gradedqualityBmaintenancePolicy-aware MCP server for Proxmox VE that maps the official API schema to MCP tools, enabling node health, disk, network, journal, updates, guest configuration, snapshots, backups, consoles, task lifecycle, service, command, and file-transfer operations with role-based access control.1-
- 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.-
- AlicenseNot gradedqualityCmaintenanceA powerful, lightweight Model Context Protocol (MCP) server built in Python that enables Artificial Intelligence assistants (Claude Desktop, Cursor, Antigravity, Claude Code, etc.) to manage and monitor your Proxmox VE cluster using natural language.MIT
- AlicenseAqualityBmaintenanceMCP server for managing Proxmox VE clusters — provision VMs and containers, manage snapshots and backups, execute commands, browse storage, and monitor resources through natural language3494 PyPI16MIT
TDQS
Scored across 14 tools
Most tools target distinct resources such as version, cluster, nodes, storage, guests, and tasks. The only potential confusion is list_nodes versus get_node_status, which both expose node CPU/memory/uptime, but the added detail and singular/plural distinction are clarified in the descriptions.
All tools follow a consistent list_ and get_ convention: list_ prefixes for collections and get_ prefixes for singular resources or statuses. There are no mixed naming styles or vague verbs.
14 tools sits within the ideal well-scoped range and each one serves a clear monitoring or query purpose. No redundant or trivial tools are present.
Read-only coverage is solid: cluster, nodes, storage, guests, snapshots, and tasks are all queryable. However, there are no lifecycle operations to create, modify, delete, start, or stop guests, and get_next_vmid strongly implies provisioning without a corresponding create tool, creating a dead-end.