mcp-proxmox
Related Servers
Alternatives to mcp-proxmox
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for managing Proxmox VE resources, VM/CT lifecycle, snapshots, backups, and clones via natural language.23MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server for interacting with the Proxmox Virtual Environment API, enabling management of VMs, containers, storage, and cluster resources through natural language.MIT
- 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 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.42 npm1MIT
- 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.49 npmMIT
- 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
TDQS
Scored across 37 tools
Most tools target a distinct resource/action pair, such as list_vms vs list_containers vs list_snapshots. A few boundaries are fuzzy—list_storage_content with content_type='backup' overlaps list_backups, and stop_guest (force) vs shutdown_guest (graceful) could be confused—but descriptions make the intended use clear.
The set predominantly uses verb_noun naming with list_*, get_*, create_*, and delete_* prefixes, and guest lifecycle verbs consistently use the _guest suffix. The vm_screenshot/vm_send_key/vm_send_text prefix and generic exec_command are minor deviations from the dominant pattern.
At 37 tools, the surface is heavy for a typical MCP server, but the broad Proxmox domain (guests, storage, backups, snapshots, network, firewall, console) justifies much of it. Some near-duplicate listing tools (list_storage_content vs list_backups vs list_templates) make it feel slightly larger than necessary.
The toolset covers the main guest lifecycle, snapshots, backups/restore, migration, resizing, firewall, and console workflows. Notable gaps include generic guest configuration updates beyond resize/cloud-init and backup deletion, but agents can work around these or they fall outside the core surface.