MCP Proxmox Server
Enables comprehensive management of Proxmox virtualization infrastructure through natural language, supporting VM/LXC lifecycle operations, networking, snapshots, backups, metrics monitoring, and cluster orchestration. Provides full access to Proxmox API functionality including resource discovery, cloud-init configuration, and automated deployment workflows.
README
MCP Proxmox Server
Advanced Proxmox Model Context Protocol (MCP) server in Python exposing rich Proxmox utilities for discovery, lifecycle, networking, snapshots/backups, metrics, pools/permissions, and orchestration.
- Guide reference: MCP Quickstart (Python)
- Structure mirrors:
bsahane/mcp-ansible
Quick start
git clone https://github.com/bsahane/mcp-proxmox.git
cd mcp-proxmox
python3 -m venv .venv
source .venv/bin/activate
python -m pip install -U pip
pip install -r requirements.txt
# (Optional) install the package locally
pip install -e .
.env configuration
- Copy
.env.exampleto.envand edit values:
cp .env.example .env
.env keys:
PROXMOX_API_URL="https://proxmox.example.com:8006"
PROXMOX_TOKEN_ID="root@pam!mcp-proxmox"
PROXMOX_TOKEN_SECRET="<secret>"
PROXMOX_VERIFY="true"
PROXMOX_DEFAULT_NODE="pve"
PROXMOX_DEFAULT_STORAGE="local-lvm"
PROXMOX_DEFAULT_BRIDGE="vmbr0"
Notes:
- Use an API token with appropriate ACLs; for discovery,
PVEAuditorat/is sufficient; for lifecycle, grant narrower roles (e.g.,PVEVMAdmin) on a pool. - Using
.envavoids zsh history expansion issues with!in token IDs.
Run the MCP server (stdio)
Preferred (module form):
source .venv/bin/activate
python -m proxmox_mcp.server
Or installed console script:
source .venv/bin/activate
proxmox-mcp
Configure in Cursor
Edit ~/.cursor/mcp.json (portable example):
{
"mcpServers": {
"proxmox-mcp": {
"command": "python",
"args": ["-m", "proxmox_mcp.server"]
}
}
}
Configure in Claude for Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"proxmox-mcp": {
"command": "python",
"args": ["-m", "proxmox_mcp.server"]
}
}
}
Tools reference
All tools are available via MCP. Destructive tools accept confirm, and most write operations support dry_run, wait, timeout, poll_interval.
Format below per tool:
- Description
- Example question → Possible answer (shape)
Core discovery
proxmox-list-nodes- List cluster nodes (name, status, CPU/RAM/disk summary)
- Example: "List cluster nodes"
- Answer:
[ { "node": "pve", "status": "online", ... } ]
proxmox-node-status- Detailed node health (load, uptime, versions)
- Example:
{ "node": "pve" } - Answer:
{ "kversion": "...", "uptime": 123456, ... }
proxmox-list-vms- List VMs (filter by node, status, name substring)
- Example:
{ "node": "pve", "status": "running" } - Answer:
[ { "vmid": 100, "name": "web01", ... } ]
proxmox-vm-info- Get VM details by
vmidorname(+optional node), includes config - Example:
{ "name": "web01" } - Answer:
{ "selector": {...}, "config": {...} }
- Get VM details by
proxmox-list-lxc- List LXC containers (filterable)
- Example:
{ "node": "pve" } - Answer:
[ { "vmid": 50001, "name": "ct01", ... } ]
proxmox-lxc-info- Get LXC details by
vmidorname(+optional node) - Example:
{ "vmid": 50001 } - Answer:
{ "selector": {...}, "config": {...} }
- Get LXC details by
proxmox-list-storage- List storages (types, free/used)
- Example:
{} - Answer:
[ { "storage": "local-lvm", "type": "lvmthin", ... } ]
proxmox-storage-content- List storage content (ISOs, templates, images)
- Example:
{ "node": "pve", "storage": "local" } - Answer:
[ { "volid": "local:iso/foo.iso", ... } ]
proxmox-list-bridges- List node bridges (vmbr...)
- Example:
{ "node": "pve" } - Answer:
[ { "iface": "vmbr0", ... } ]
proxmox-list-tasks- Recent tasks (filter by node, user)
- Example:
{ "node": "pve", "limit": 20 } - Answer:
[ { "upid": "UPID:...", "status": "OK" }, ... ]
proxmox-task-status- Check a task status
- Example:
{ "upid": "UPID:..." } - Answer:
{ "status": "stopped", "exitstatus": "OK" }
VM lifecycle
proxmox-clone-vm- Clone template VM to new VMID/name (supports target node, storage)
- Example:
{ "source_vmid": 101, "new_vmid": 50009, "name": "web01", "storage": "local-lvm", "confirm": true, "wait": true } - Answer:
{ "upid": "UPID:...", "status": {...} }
proxmox-create-vm- Create new VM from ISO/template (minimal config)
- Example:
{ "node": "pve", "vmid": 200, "name": "web02", "iso": "debian.iso", "confirm": true } - Answer:
{ "upid": "UPID:..." }
proxmox-delete-vm- Delete VM (confirm, purge)
- Example:
{ "name": "web01", "purge": true, "confirm": true } - Answer:
{ "upid": "UPID:..." }
proxmox-start-vm/proxmox-stop-vm/proxmox-reboot-vm/proxmox-shutdown-vm- Manage power state (stop supports hard and timeout)
- Example:
{ "name": "web01", "wait": true } - Answer:
{ "upid": "UPID:...", "status": {...} }
proxmox-migrate-vm- Live/offline migrate to another node
- Example:
{ "name": "web01", "target_node": "pve2", "live": true } - Answer:
{ "upid": "UPID:..." }
proxmox-resize-vm-disk- Grow disk (GB) on target disk (e.g., scsi0)
- Example:
{ "name": "web01", "disk": "scsi0", "grow_gb": 10, "confirm": true, "wait": true } - Answer:
{ "upid": "UPID:...", "status": {...} }
proxmox-configure-vm- Set whitelisted params (cores, memory, balloon, netX, agent, etc.)
- Example:
{ "name": "web01", "params": { "memory": 4096, "cores": 4 }, "confirm": true } - Answer:
{ "upid": "UPID:..." }or{ "result": null }
LXC lifecycle
proxmox-create-lxc- Create container from template (CPU/mem, rootfs size, net, storage)
- Example:
{ "node": "pve", "vmid": 50050, "hostname": "ct01", "ostemplate": "debian-12.tar.zst", "confirm": true } - Answer:
{ "upid": "UPID:..." }
proxmox-delete-lxc/proxmox-start-lxc/proxmox-stop-lxc/proxmox-configure-lxc- Manage container lifecycle and config
Cloud-init & networking
proxmox-cloudinit-set- Set CI params (ipconfig0, sshkeys, ciuser/cipassword)
- Example:
{ "name": "web01", "ipconfig0": "ip=192.168.1.50/24,gw=192.168.1.1", "confirm": true } - Answer:
{ "upid": "UPID:..." }or{ "result": null }
proxmox-vm-nic-add/proxmox-vm-nic-remove- Add/remove NICs (bridge, model, VLAN)
proxmox-vm-firewall-get/proxmox-vm-firewall-set- Get/set per-VM firewall state and rules
Images, templates, snapshots, backups
proxmox-upload-iso/proxmox-upload-template- Upload ISO or LXC template to storage
proxmox-template-vm- Convert VM to template
proxmox-list-snapshots/proxmox-create-snapshot/proxmox-delete-snapshot/proxmox-rollback-snapshot- Manage snapshots; rollback supports
wait
- Manage snapshots; rollback supports
proxmox-backup-vm/proxmox-restore-vm- Run vzdump and restore archives
Metrics and monitoring
proxmox-vm-metrics- RRD metrics for VM (timeframe, cf)
proxmox-node-metrics- RRD metrics for node
Pools, users, permissions
proxmox-list-pools/proxmox-create-pool/proxmox-delete-pool/proxmox-pool-add/proxmox-pool-removeproxmox-list-users/proxmox-list-roles/proxmox-assign-permission
Orchestration helpers
proxmox-wait-task- Poll a task until done/timeout
proxmox-register-vm-as-host- Emit JSON/INI snippet for Ansible inventory (hostname, IP, SSH user/key)
proxmox-guest-exec(optional)- Run a command via QEMU Guest Agent (requires agent in guest)
Examples
- List nodes:
{}forproxmox-list-nodes - VMs on node
pve:{ "node": "pve" }forproxmox-list-vms - Clone a template:
{ "source_vmid": 101, "new_vmid": 50009, "name": "web01", "storage": "local-lvm", "confirm": true, "wait": true } - Configure Cloud-init IP:
{ "name": "web01", "ipconfig0": "ip=192.168.1.50/24,gw=192.168.1.1", "confirm": true }
Notes
- Server uses stdio transport; prints only MCP protocol to stdout. Logs go to stderr.
- Authentication uses your environment variables and/or
.envfile. - Name collisions across nodes return clear errors unless you specify
node.
Development
# Lint/type-check as needed (not included by default)
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。