Manage Proxmox VE clusters through AI assistants — VMs, containers, and more
MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Manage Proxmox VE clusters through AI assistants — VMs, containers, and more.
MCP server for managing Proxmox VE clusters through AI assistants like Claude, Cursor, and Cline.
Once MCP is connected, these are the calls the assistant has available:
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.Config.Disk — resize disksVM.Config.CPU — change CPU allocationVM.Config.Memory — change memory allocationVM.Monitor — access QEMU monitor (for metrics)You will need 3 environment variables: PROXMOX_HOST, PROXMOX_TOKEN_ID, PROXMOX_TOKEN_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at mcp-proxmox on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — VM.Audit, VM.PowerMgmt, VM.Snapshot and 11 more — is a fair guide to whether it matches your workflow. It is maintained by antonio-mello-ai; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| VM.Audit | read VM/CT status and config |
| VM.PowerMgmt | start/stop/shutdown/reboot |
| VM.Snapshot | create/rollback/delete snapshots |
| VM.Allocate | create/delete/clone VMs and containers |
| VM.Clone | clone operations |
| Datastore.Audit | list storages and browse content |
| Datastore.AllocateSpace | allocate disk space for new VMs/CTs |
| Sys.Audit | read node status and tasks |
| VM.Config.Disk | resize disks |
| VM.Config.CPU | change CPU allocation |
| VM.Config.Memory | change memory allocation |
| VM.Monitor | access QEMU monitor (for metrics) |
| VM.Migrate | migrate VMs/CTs between nodes |
| Sys.Modify | manage firewall rules |
{
"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"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PROXMOX_HOST | Endpoint or connection string the server talks to. | Optional |
| PROXMOX_TOKEN_ID | Credential the server authenticates with. | Yes |
| PROXMOX_TOKEN_SECRET | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.