mcp-server-proxmox
Related Servers
Alternatives to mcp-server-proxmox
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.-
- 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
- AlicenseAqualityDmaintenanceMCP server for managing Proxmox VE resources, VM/CT lifecycle, snapshots, backups, and clones via natural language.23MIT
- 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
- AlicenseNot gradedqualityCmaintenanceMCP 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
- AlicenseAqualityAmaintenanceAI-powered MCP server for managing Proxmox VE VMs and containers with built-in governance, audit logging, and reversibility.433MIT
TDQS
Scored across 10 tools
Most tools have clearly distinct resource+action pairs; list_vms/get_vm_status and list_nodes/get_node_status are separated by scope. The main ambiguity is between create_container and provision_stack, which both provision containers and could lead to misselection.
All tool names follow a consistent snake_case verb_noun pattern (list_*, get_*, start_*, stop_*, create_*, provision_*). Naming is predictable and readable across the entire set.
Ten tools is a well-scoped set for a Proxmox management server, covering node inspection, VM/container listing, status lookup, VM power control, and container provisioning without feeling bloated or too thin.
The set covers listing, status, VM start/stop, and container creation, but it lacks obvious lifecycle operations: no VM creation/update/delete, no container start/stop/delete, and no management of provisioned stacks. This leaves significant gaps for normal Proxmox administration workflows.