Proxmox VE
Monitor and manage Proxmox VE clusters, guests, storage and backups, read-only by default
- Pricing
- Open source
- Platforms
- self-hosted, macOS, Windows
- Runs
- Locally
- Version
- 0.6.0
- Listing updated
- 2 days ago
About Proxmox VE
Proxmox VE is an open-source MCP server for cloud and infrastructure. It runs locally on your machine and is started by your AI client.
With 314 tools in 19 toolsets, this open-source server is a very wide wrapper around the Proxmox VE API for version 8 and 9, on one node or many. Tool counts split into 155 read, 107 write, 45 delete and 7 exec. Toolsets cover QEMU VMs, LXC containers, the guest agent, snapshots, storage including SMART and ZFS, vzdump backups, tasks, access control, firewall, high availability, SDN, Ceph, pools, replication, notifications and hardware.
Writes, deletes and running commands inside guests are three separate switches, and unavailable tools are not registered at all. Write tools take dry_run, an audit log can record changes, and long operations run as Proxmox tasks that the tool waits on. Guests are addressed by VMID so single nodes need no node names. The README recommends a dedicated API token with Proxmox's own roles.
Install
Run in a terminal
claude mcp add proxmox-mcp --env PROXMOX_URL='<PROXMOX_URL>' --env PROXMOX_API_TOKEN='<PROXMOX_API_TOKEN>' --env PROXMOX_PASSWORD='<PROXMOX_PASSWORD>' -- docker run -i --rm -e PROXMOX_URL -e PROXMOX_API_TOKEN -e PROXMOX_PASSWORD ghcr.io/mattoddie/proxmox-mcp:0.6.0Add to claude_desktop_config.json
{
"mcpServers": {
"proxmox-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PROXMOX_URL",
"-e",
"PROXMOX_API_TOKEN",
"-e",
"PROXMOX_PASSWORD",
"ghcr.io/mattoddie/proxmox-mcp:0.6.0"
],
"env": {
"PROXMOX_URL": "<PROXMOX_URL>",
"PROXMOX_API_TOKEN": "<PROXMOX_API_TOKEN>",
"PROXMOX_PASSWORD": "<PROXMOX_PASSWORD>"
}
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"proxmox-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PROXMOX_URL",
"-e",
"PROXMOX_API_TOKEN",
"-e",
"PROXMOX_PASSWORD",
"ghcr.io/mattoddie/proxmox-mcp:0.6.0"
],
"env": {
"PROXMOX_URL": "<PROXMOX_URL>",
"PROXMOX_API_TOKEN": "<PROXMOX_API_TOKEN>",
"PROXMOX_PASSWORD": "<PROXMOX_PASSWORD>"
}
}
}
}Add to .vscode/mcp.json
{
"servers": {
"proxmox-mcp": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PROXMOX_URL",
"-e",
"PROXMOX_API_TOKEN",
"-e",
"PROXMOX_PASSWORD",
"ghcr.io/mattoddie/proxmox-mcp:0.6.0"
],
"env": {
"PROXMOX_URL": "<PROXMOX_URL>",
"PROXMOX_API_TOKEN": "<PROXMOX_API_TOKEN>",
"PROXMOX_PASSWORD": "<PROXMOX_PASSWORD>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"proxmox-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PROXMOX_URL",
"-e",
"PROXMOX_API_TOKEN",
"-e",
"PROXMOX_PASSWORD",
"ghcr.io/mattoddie/proxmox-mcp:0.6.0"
],
"env": {
"PROXMOX_URL": "<PROXMOX_URL>",
"PROXMOX_API_TOKEN": "<PROXMOX_API_TOKEN>",
"PROXMOX_PASSWORD": "<PROXMOX_PASSWORD>"
}
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"proxmox-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PROXMOX_URL",
"-e",
"PROXMOX_API_TOKEN",
"-e",
"PROXMOX_PASSWORD",
"ghcr.io/mattoddie/proxmox-mcp:0.6.0"
],
"env": {
"PROXMOX_URL": "<PROXMOX_URL>",
"PROXMOX_API_TOKEN": "<PROXMOX_API_TOKEN>",
"PROXMOX_PASSWORD": "<PROXMOX_PASSWORD>"
}
}
}
}Configuration
MCP_TRANSPORTRuns the server over stdio. The image defaults to HTTP.PROXMOX_URLAddress of any node in the cluster, with the port.RequiredPROXMOX_API_TOKENRecommended. The whole API token as user@realm!tokenid=secret. Leave empty to use a username and password.PROXMOX_USERNAMEUsed instead of an API token, as user@realm (e.g. mcp@pve).PROXMOX_PASSWORDThe user's password, used with the username.PROXMOX_TLS_FINGERPRINTRecommended for Proxmox's self-signed certificate: its SHA-256 fingerprint. An https URL needs this or PROXMOX_VERIFY_SSL.PROXMOX_VERIFY_SSLLeave empty when you set a fingerprint. true: the certificate is publicly trusted. false: skip the check (insecure).PROXMOX_DEFAULT_NODENode used when a request doesn't name one. Not needed on a single-node install.PROXMOX_ALLOW_WRITESAllow changes: start and stop guests, edit configuration, create VMs, snapshots and backups.PROXMOX_ALLOW_DELETESAlso allow deleting guests, volumes, snapshots, backups and configuration. Needs writes.PROXMOX_ALLOW_EXECAlso allow commands and file access inside VMs through the guest agent. Needs writes.PROXMOX_TOOLSETSOptional comma-separated toolsets, to expose fewer tools. Empty means all (except raw).PROXMOX_DENY_TOOLSOptional comma-separated tool names never to offer. An unknown name stops the server from starting.PROXMOX_AUDIT_LOGOptional. stderr, or a file path inside the container, to log every change as a JSON line.
What it does
- 19 toolsets
- Cluster, nodes, VMs, containers, storage, backups, firewall, HA, SDN, Ceph and more.
- Three safety switches
- Writes, deletes and in-guest exec are enabled separately.
- Task-aware operations
- Waits for Proxmox tasks and returns the end of the log.
- Dry-run and audit
- Preview changes and log every one as JSON.
- VMID addressing
- Finds the node for a guest automatically.
Good for
- Health-check a cluster
- Find guests with no recent backup
- List snapshots older than 30 days
- Clone a template into a new VM
- Review users and API tokens for risky permissions
Pricing
Open source
MIT licence
Prices change. Check proxmox-mcp.mattoddie.dev before you buy.
Proxmox VE FAQ
Which Proxmox versions work?
Proxmox VE 8 and 9.
How do I limit what it can do?
Use a scoped API token, leave writes off and expose only chosen toolsets.
How is it installed?
A Docker image for amd64 and arm64, plain binaries, or a Claude Desktop bundle.
What licence?
MIT.
Is Proxmox VE free?
Yes. Proxmox VE is open source, so you can use and self-host it for free.
How do I add Proxmox VE to Claude Code?
Run this command in your terminal: claude mcp add proxmox-mcp --env PROXMOX_URL='<PROXMOX_URL>' --env PROXMOX_API_TOKEN='<PROXMOX_API_TOKEN>' --env PROXMOX_PASSWORD='<PROXMOX_PASSWORD>' -- docker run -i --rm -e PROXMOX_URL -e PROXMOX_API_TOKEN -e PROXMOX_PASSWORD ghcr.io/mattoddie/proxmox-mcp:0.6.0
What are the best alternatives to Proxmox VE?
The closest alternatives to Proxmox VE are Agent Yurt, Proofline, filex, MagicWP MCP and Kubana Cloud Domains.
Alternatives to Proxmox VE

Agent Yurt
MCP serverBack up agent memory, files and dashboards, then recover from a reviewed snapshot
Not checked yet- Remote
- Free
- Knowledge and memory

Proofline
MCP serverProduction-aware review of changes against your AWS or Google Cloud setup, via MCP
- Remote
- Freemium
- Developer tools

filex
MCP serverSelf-hosted file manager in one Go binary with a built-in MCP server for agents
Not checked yet- Remote
- Open source
- Files and documents

MagicWP MCP
MCP serverRun WordPress hosting from an assistant: backups, staging, updates, PHP and domains
- Remote
- Free trial
- Cloud and infrastructure

Kubana Cloud Domains
MCP serverSearch, register and renew domains and set nameservers at Kubana Cloud from an assistant
Not checked yet- 3 tools
- Remote
- Paid
- Cloud and infrastructure

Kubana Cloud DNS Management
MCP serverCreate DNS zones, edit records and check nameserver delegation on Kubana Cloud
Not checked yet- 5 tools
- Remote
- Free
- Cloud and infrastructure