Enables comprehensive management of Proxmox VE clusters, including provisioning and lifecycle management of virtual machines and containers, snapshot and backup operations, and system monitoring.
Provides tools for managing and interacting with QEMU virtual machines, including status monitoring, configuration, and command execution via the QEMU guest agent.
mcp-proxmox
MCP server for managing Proxmox VE clusters through AI assistants like Claude, Cursor, and Cline.
Provision, manage, and monitor your entire Proxmox infrastructure through natural language. Create VMs and containers, manage snapshots, browse storage, and more.
Quick Start
# Run directly with uvx (no install needed)
uvx mcp-proxmox
# Or install with pip
pip install mcp-proxmoxConfiguration
Set these environment variables (or create a .env file):
PROXMOX_HOST=192.168.1.100 # Your Proxmox VE host
PROXMOX_TOKEN_ID=user@pam!mcp # API token ID
PROXMOX_TOKEN_SECRET=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx # API token secretOptional:
PROXMOX_PORT=8006 # Default: 8006
PROXMOX_VERIFY_SSL=false # Default: falseCreating a Proxmox API Token
Log into your Proxmox web UI
Go to Datacenter > Permissions > API Tokens
Click Add and create a token for your user
Uncheck "Privilege Separation" for full access, or assign specific permissions:
VM.Audit— read VM/CT status and configVM.PowerMgmt— start/stop/shutdown/rebootVM.Snapshot— create/rollback/delete snapshotsVM.Allocate— create/delete/clone VMs and containersVM.Clone— clone operationsDatastore.Audit— list storages and browse contentDatastore.AllocateSpace— allocate disk space for new VMs/CTsSys.Audit— read node status and tasksVM.Monitor— access QEMU monitor (for metrics)
Integration
Claude Desktop
Add to ~/.claude/claude_desktop_config.json:
{
"mcpServers": {
"proxmox": {
"command": "uvx",
"args": ["mcp-proxmox"],
"env": {
"PROXMOX_HOST": "192.168.1.100",
"PROXMOX_TOKEN_ID": "user@pam!mcp",
"PROXMOX_TOKEN_SECRET": "your-token-secret"
}
}
}
}Claude Code
Add to .claude/settings.json or ~/.claude/settings.json:
{
"mcpServers": {
"proxmox": {
"command": "uvx",
"args": ["mcp-proxmox"],
"env": {
"PROXMOX_HOST": "192.168.1.100",
"PROXMOX_TOKEN_ID": "user@pam!mcp",
"PROXMOX_TOKEN_SECRET": "your-token-secret"
}
}
}
}Cursor
Add to Cursor Settings > MCP with the same configuration as above.
Available Tools
Discovery
Tool | Description |
| List all cluster nodes with CPU, memory, and uptime |
| Detailed node info: CPU model, memory, disk, versions |
| List QEMU VMs (filter by node or status) |
| List LXC containers (filter by node or status) |
| Detailed VM/CT status by VMID (auto-detects type and node) |
Lifecycle
Tool | Description |
| Start a stopped VM or container |
| Force-stop (requires confirmation) |
| Graceful ACPI/init shutdown |
| Reboot (requires confirmation) |
Storage
Tool | Description |
| List storage pools with capacity and usage (filter by node) |
| Browse ISOs, templates, backups, and disk images |
Provisioning
Tool | Description |
| Create a QEMU VM with configurable CPU, memory, disk, ISO, and network |
| Create an LXC container from a template |
| Clone a VM or CT (full or linked clone, cross-node support) |
| Permanently delete a stopped VM or CT (requires confirmation) |
Backup & Restore
Tool | Description |
| List backup files (filter by node, storage, or VMID) |
| Create a vzdump backup (snapshot/suspend/stop modes, zstd/lzo/gzip) |
| Restore a VM or CT from a backup file (requires confirmation) |
Command Execution
Tool | Description |
| Run a command inside a QEMU VM via guest agent |
Note:
exec_commandrequiresqemu-guest-agentinstalled and running inside the VM. Not supported for LXC containers (Proxmox API limitation).
Snapshots
Tool | Description |
| List all snapshots for a VM/CT |
| Create a new snapshot |
| Rollback to a snapshot (requires confirmation) |
| Delete a snapshot (requires confirmation) |
Monitoring
Tool | Description |
| CPU, memory, network, disk I/O over time |
| Recent tasks on a node (backups, migrations, etc.) |
Safety
Destructive operations (stop_guest, reboot_guest, rollback_snapshot, delete_snapshot, delete_guest) require explicit confirm=true. The first call returns a warning describing the impact; only a second call with confirmation executes the action.
Examples
Once connected, you can ask your AI assistant:
"List all my VMs and their status"
"How much memory is VM 100 using?"
"Shut down container 105"
"Create a snapshot of VM 200 called before-upgrade"
"Show me the CPU usage of VM 100 over the last day"
"What tasks ran on node pve recently?"
"Which VMs are stopped?"
"What storage pools do I have and how full are they?"
"Show me available ISO images"
"Create a new Ubuntu VM with 4 cores and 8GB RAM"
"Clone VM 100 as a test environment"
"Create a Debian container from template"
"Delete the old test VM 999"
"Back up VM 100 to the zfs-backup-storage"
"Show me all backups for VM 200"
"Restore the latest backup of container 101"
"Run 'df -h' on VM 100"
"Check if nginx is running on VM 200"
Development
git clone https://github.com/antonio-mello-ai/mcp-proxmox.git
cd mcp-proxmox
python -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
# Run tests
pytest
# Lint
ruff check src/ tests/
ruff format src/ tests/
# Type check
mypy src/License
MIT