Summary

This project provides a security-conscious control plane for managing Proxmox VE VMs, LXCs, backups, and snapshots. It targets engineers and power users integrating Proxmox operations with AI agents via MCP or automating workflows using OpenAPI, offering a unified interface that abstracts complex API calls and custom scripting.

How It Works

ProxmoxMCP-Plus acts as an intermediary, exposing Proxmox VE's operational surface via two paths: native MCP for AI clients (Claude Desktop, Cursor, VS Code) and OpenAPI for HTTP automation. It handles VM/LXC lifecycle, snapshots, backups, ISOs, node inspection, and secure container commands. Key is persistent job tracking for async Proxmox tasks, providing stable job_ids, UPID monitoring, polling, retry, cancellation, and audit history for long-running operations.

Quick Start & Requirements

Installation options include pip install proxmox-mcp-plus (MCP stdio) or Docker Compose (MCP HTTP/OpenAPI). Source checkout requires pip install -e ".[dev]". A Proxmox API token with minimal permissions is mandatory, configured via proxmox-config/config.json. Optional SSH config is needed for container commands. Docker is required for Docker runtimes. Links to detailed guides for client setup, integrations, and API references are available within the repository.

Highlighted Details

• Dual access paths: Native MCP for AI agents, OpenAPI for HTTP automation.
• Proxmox-centric operations: VM/LXC lifecycle, snapshots, backups, ISOs, cluster inspection.
• Robust long-running operations: Persistent job tracking (job_id), UPID monitoring, poll, retry, cancel.
• Security-focused: Proxmox API tokens, OpenAPI bearer auth, command policies, approval tokens, TLS, host/origin controls.
• Integrated validation: Unit, integration, Docker/OpenAPI, and live Proxmox e2e tests.

Maintenance & Community

The README does not detail specific contributors, sponsorships, or community channels beyond the GitHub repository itself.

Licensing & Compatibility

Released under the MIT license, permitting commercial use and integration with closed-source applications.

Limitations & Caveats

ProxmoxMCP-Plus is an access layer, not a replacement for Proxmox RBAC, network security, or client-side approval prompts. Secure operation depends on correct Proxmox API token and policy configuration. VM command execution requires QEMU Guest Agent; container commands need SSH access to the Proxmox node.