RekklesNA/ProxmoxMCP-Plus
Use MCP and OpenAPI to safely control Proxmox VE VMs, LXCs, backups, and snapshots from LLMs and AI agents.
380 ★73 forksPythonUpdated 8d ago
What you need to know
A security-conscious control plane that operates Proxmox VE (VMs, LXCs, snapshots, backups, ISOs, container commands, persistent jobs) from MCP clients and OpenAPI tooling, exposing the same surface over native MCP and an OpenAPI bridge.
Install
uvx proxmox-mcp-plus (stdio, from PyPI) pip install proxmox-mcp-plus && proxmox-mcp-plus docker run --rm -p 8000:8000 -e PROXMOX_MCP_MODE=mcp-http -e MCP_TRANSPORT=STREAMABLE_HTTP -v "$(pwd)/proxmox-config/config.json:/app/proxmox-config/config.json:ro" ghcr.io/rekklesna/proxmoxmcp-plus:latest (MCP HTTP) docker run --rm -p 8811:8811 -e PROXMOX_API_KEY="$PROXMOX_API_KEY" ghcr.io/rekklesna/proxmoxmcp-plus:latest (OpenAPI bridge, default)
Usage
- •Create a Proxmox API token with only the permissions needed, then configure proxmox-config/config.json (proxmox.host/port, auth user/token name/value; optional ssh and jobs sections).
- •Connect clients: stdio config uses command "uvx" args ["proxmox-mcp-plus"] with PROXMOX_HOST/PROXMOX_USER/PROXMOX_TOKEN_NAME/PROXMOX_TOKEN_VALUE env vars.
- •Start with read-only discovery (get_nodes, get_cluster_status, get_storage, get_vms, get_containers) before mutating tools.
- •Track long-running operations with job_id tools (list_jobs, get_job, poll_job, retry_job, cancel_job); OpenAPI routes at /jobs, /health, /livez, /openapi.json.
Key features
- ✓Dual access paths: native MCP for agent workflows and OpenAPI bridge (default Docker runtime, bearer-auth) for HTTP automation, dashboards and no-code tools.
- ✓VM/LXC lifecycle, snapshot create/rollback/delete, backup/restore, ISO download/cleanup, node/storage/cluster inspection, SSH-backed container command execution with command policy.
- ✓Persistent job store (SQLite by default) wrapping async Proxmox tasks with stable job_id, Proxmox UPID tracking, polling, retry, cancel, and audit history.
- ✓Safety controls: Proxmox API tokens, OpenAPI bearer auth, approval_token gate, command_policy, TLS validation, DNS rebinding protection plus MCP Host/Origin allowlists.
Best for
Home-lab and small-team operators who want AI agents to manage Proxmox VE infrastructure with proper auth, job tracking, and safety gates.
Caveats
- ⚠Windows/other: requires a Proxmox VE host; VM command execution needs QEMU Guest Agent, LXC command execution needs SSH to the Proxmox node.
- ⚠OpenAPI mode requires an API key (PROXMOX_API_KEY) unless PROXMOX_ALLOW_NO_AUTH=true is set for local dev only.
- ⚠Read the Security Guide before exposing the server outside a trusted local environment.
Platforms: macOS · Linux · WindowsClients: Claude Desktop · Cursor · VS Code · Codex · Open WebUI · OpenCode
Documentation ↗Reviewed 2026-08-07
Topics
ai-agentautomationclaude-desktophomelabllmlxcmcpmodel-context-protocolopen-webuiopenapiproxmoxqemuvirtualization
- Stars
- 380★
- Forks
- 73
- Language
- Python
- License
- MIT
- Created
- 2025-05-23
- Last push
- 2026-07-29