Proxmox VE MCP server for VMs, LXCs, snapshots, backups, storage, and cluster operations.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-rekklesna-proxmox-mcp-plus": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Proxmox VE MCP server for VMs, LXCs, snapshots, backups, storage, and cluster operations.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Hash-verified file editing MCP server with token efficiency hook. 11 tools for AI coding agents.
MCP Security Weekly
Get CVE alerts and security updates for io.github.RekklesNA/proxmox-mcp-plus and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Control Proxmox VE from LLMs, AI agents, MCP clients, and OpenAPI tooling with one safer interface for VMs, LXCs, backups, snapshots, ISOs, and container commands.
Quick Start | Demo | Capabilities | Scenarios | Docs | Wiki
ProxmoxMCP-Plus provides a unified Proxmox VE control surface in two forms:
MCP for Claude Desktop, Open WebUI, and other LLM or AI agent clientsOpenAPI for HTTP automation, dashboards, internal tools, and no-code workflowsInstead of stitching together raw Proxmox API calls, shell scripts, and custom glue code, the project consolidates core operational workflows in one interface:
ProxmoxMCP-Plus is designed for the gap between low-level Proxmox primitives and production-facing workflows that need to be usable from both LLM-native clients and standard automation systems.
Dual-surface architecture: MCP for conversational workflows, OpenAPI for standard automationOperator-oriented scope: focused on day-2 tasks, not just raw low-level endpointsSafer-by-default execution: auth, command policy, and explicit execution pathsOperationally grounded: documented workflows are backed by live-environment verificationRead the official Proxmox docs first if you are setting up a fresh lab:
At minimum, proxmox-config/config.json needs:
proxmox.hostproxmox.portauth.userauth.token_nameauth.token_valueAdd an ssh section as well if you want container command execution.
uvx proxmox-mcp-plus
Or install it first:
pip install proxmox-mcp-plus
proxmox-mcp-plus
docker run --rm -p 8811:8811 \
-v "$(pwd)/proxmox-config/config.json:/app/proxmox-config/config.json:ro" \
ghcr.io/rekklesna/proxmoxmcp-plus:latest
git clone https://github.com/RekklesNA/ProxmoxMCP-Plus.git
cd ProxmoxMCP-Plus
uv venv
uv pip install -e ".[dev]"
python main.py