proxmox-mcp
A PROXMOX implementation containing 152 tools covering QEMU VMs, LXC, unified guest power, storage admin, cluster/tasks, snapshots, backups (incl. scheduled jobs), migration, HA, firewall (incl. IPSet CIDRs), access control, replication, SDN (read), ACME (read), pools, and console tickets.
README
cursor-proxmox-mcp
Formal Cursor ↔ Proxmox VE MCP integration — 171 tools covering QEMU VMs (incl. guest-agent network/file push + qm_set_vm), LXC (incl. provision_lxc, bootstrap_docker_lxc, crun Path B, DNS/SSH helpers, deploy_node_app), unified guest power, storage admin, cluster/tasks, snapshots, backups (incl. scheduled jobs), migration, HA, firewall (incl. IPSet CIDRs), access control, replication, SDN (read), ACME (read), pools, and console tickets. v1.5.1 adds deploy_node_app and CT111 tip/timeout/quorum hygiene (r14).
Repo: hackmods/cursor-proxmox-mcp
Docs: Setup guide · Wiki (docs/wiki/) · Publishing · Security · Contributing · API coverage · Changelog
<!-- mcp-name: io.github.hackmods/cursor-proxmox-mcp -->
MCP tools
Registered via tools/register.py (called from ProxmoxMCPServer._setup_tools()) — inventory locked by tools/inventory.py / tests/expected_tools.py (CI fails on drift).
| Domain | Tools |
|---|---|
| Nodes | get_nodes, get_node_status, list_node_networks, get_node_subscription, list_node_certificates, get_node_report, list_node_services, get_node_time, wake_node |
| Cluster / tasks | get_cluster_status, get_next_vmid, get_task_status, list_tasks, wait_for_task, get_version, get_mcp_capabilities, get_cluster_resources, get_cluster_log, get_cluster_options |
| QEMU | lifecycle + config (ISO/cloud-init/net/onboot/tags/description; optional wait=true) + get_vm_network / push_to_vm / pull_from_vm (guest agent) + qm_set_vm (allowlisted host set) + get_vm_status, get_vm_rrd_data, console tickets |
| LXC | lifecycle + config + suspend/resume (CRIU warn) + get_lxc_status / get_lxc_network / get_lxc_rrd_data + VNC/SPICE/termproxy; ssh_public_keys / docker_ready / nameserver / wait / onboot / description / tags on create; provision_lxc (one-shot create→start→IP→SSH) / bootstrap_docker_lxc / prepare_lxc_for_docker (`docker_mode=auto |
| Guest (unified) | start/stop/shutdown/reboot/delete_guest, get_guest_status, get_guest_pending, move_guest_disk (guest_type) |
| Snapshots / Backups | snapshot CRUD/rollback; one-shot backup CRUD; scheduled list/create/delete_backup_job |
| Storage | list, content, list_os_templates, list_isos, download-url, definition CRUD |
| Migrate / HA | migrate_guest; HA groups + resources CRUD |
| Firewall | cluster + guest rules/options; aliases; IP sets + CIDR members; macros |
| Access | users, groups, roles, ACL, tokens, get_permissions, get_token_permissions |
| Replication | list/status/run/create/update/delete jobs |
| SDN | list zones/vnets/controllers/ipams/dns + apply_sdn |
| ACME | list plugins/accounts/directories (read) |
| Pools | list/get/create/update/delete |
Suggested agent flow
get_next_vmid→list_os_templates/list_isos→list_node_networksprovision_lxc(preferred one-shot) orcreate_lxc/create_vm→wait_for_task→ startcreate_snapshotbefore risky changes →update_*_config→get_guest_pending→ reboot if neededmigrate_guest/ HA / firewall / access / replication as needed
Guest type unknown? Prefer unified tools (start_guest, stop_guest, shutdown_guest, reboot_guest, delete_guest, get_guest_status) with guest_type=qemu|lxc. Parallel *_vm / *_lxc names stay for existing prompts.
Installation
Prerequisites
- uv (recommended) or Python 3.10+
- Proxmox API token
Path 1 — uvx (recommended)
PyPI package name is cursor-proxmox-mcp (console scripts: cursor-proxmox-mcp, plus aliases proxmox-mcp-server / proxmox-mcp).
Note: The unrelated PyPI project
proxmox-mcp-serveris a different codebase. Always installcursor-proxmox-mcp.
# Install uv if needed: pip install uv OR winget install astral-sh.uv
# After PyPI publish (GitHub Release → publish.yml):
uvx cursor-proxmox-mcp
# From a local checkout (dev / before first publish):
uvx --from . cursor-proxmox-mcp
Cursor MCP (published package — no checkout):
{
"mcpServers": {
"proxmox": {
"command": "uvx",
"args": ["cursor-proxmox-mcp"],
"env": {
"PROXMOX_MCP_CONFIG": "C:/Users/YOU/proxmox-config/config.json"
}
}
}
}
From a local checkout, use "args": ["--from", "C:/Users/YOU/Projects/cursor-proxmox-mcp", "cursor-proxmox-mcp"] instead.
Why uvx: it resolves dependencies into an isolated ephemeral env so Cursor does not depend on a hand-managed venv/PYTHONPATH.
Path 2 — uv from source
git clone https://github.com/hackmods/cursor-proxmox-mcp.git
cd cursor-proxmox-mcp
uv venv
# Windows: .\.venv\Scripts\Activate.ps1
# Linux/macOS: source .venv/bin/activate
uv pip install -e ".[dev]"
cp proxmox-config/config.example.json proxmox-config/config.json
# Edit host + token, then:
uv run cursor-proxmox-mcp
Path 3 — pip fallback
python -m venv .venv
# activate venv
pip install -e ".[dev]"
# optional OpenAPI bridge: pip install -e ".[openapi]"
$env:PROXMOX_MCP_CONFIG="proxmox-config\config.json" # PowerShell
python -m proxmox_mcp.server
Cursor MCP (direct Python — use absolute paths):
{
"mcpServers": {
"proxmox": {
"command": "python",
"args": ["-m", "proxmox_mcp.server"],
"cwd": "C:/Users/YOU/Projects/cursor-proxmox-mcp",
"env": {
"PROXMOX_MCP_CONFIG": "C:/Users/YOU/Projects/cursor-proxmox-mcp/proxmox-config/config.json",
"PYTHONPATH": "C:/Users/YOU/Projects/cursor-proxmox-mcp/src"
}
}
}
}
Restart the proxmox MCP server in Cursor after pulling new tools. Manual launchers: start.bat (Windows) / start.sh (Unix) — prefer uvx cursor-proxmox-mcp in mcp.json.
Verify / local CI
.\scripts\ci-local.ps1
./scripts/ci-local.sh
Runs: editable install → entrypoint smoke → ruff → pytest → inventory floor (≥100 tools).
Troubleshooting
| Symptom | Fix |
|---|---|
spawn uvx ENOENT |
Install uv (pip install uv or winget install astral-sh.uv), then restart Cursor |
ModuleNotFoundError: proxmox_mcp |
Use uvx/uv run, or set PYTHONPATH=.../src for plain python |
PROXMOX_MCP_CONFIG ... must be set |
Point env at proxmox-config/config.json (absolute path) |
| Auth OK but empty data / odd 403 | Privilege Separation Yes without token ACL — see SETUP.md |
403 on HA / firewall / keyctl |
Token needs elevated role; prefer scoped mcp@pve over root@pam when possible |
| Tools missing in Cursor | Restart MCP server after git pull |
First-time cluster wiring (token, privsep, Cursor JSON, example prompts): SETUP.md. LXC shell / runtime IP needs opt-in host SSH (authorized_keys, optional host_overrides, reload MCP): SETUP.md — SSH for LXC exec.
Configuration
Example proxmox-config/config.json:
{
"proxmox": {
"host": "PROXMOX_HOST",
"port": 8006,
"verify_ssl": false,
"service": "PVE"
},
"auth": {
"user": "USER@pve",
"token_name": "TOKEN_NAME",
"token_value": "TOKEN_VALUE"
},
"logging": {
"level": "INFO",
"format": "%(asctime)s - %(name)s - %(levelname)s - %(message)s",
"file": "proxmox_mcp.log"
}
}
Create the token in Proxmox UI: Datacenter → Permissions → API Tokens. See SETUP.md — API token & Privilege Separation for the full walkthrough.
Privilege Separation: leave Yes (default) and grant ACLs to the token (user@realm!tokenid). Setting it to No makes the token inherit the user’s full permissions (common lab shortcut; larger blast radius if leaked). Grant roles matching the tools you use (PVEAuditor, PVEVMAdmin, Datastore.*, Sys.Audit/Sys.Modify for HA/firewall/access).
Prefer "token_value": "${PROXMOX_TOKEN_VALUE}" in config and set the env var in Cursor MCP config so secrets stay out of the JSON file.
Security
This server can create/delete guests, change firewall/ACL, and run guest commands. Treat the API token like production infra credentials. Full policy: SECURITY.md.
Features
- Token auth via proxmoxer (JSON config + optional
${ENV}secret interpolation) - Full guest lifecycle, snapshots, vzdump backups
- Storage content + definition CRUD + URL download
- Cluster HA, firewall (rules/aliases/ipsets), access/ACL/tokens
- Replication jobs, SDN read + apply, ACME read, pools
- Console ticket mint only (VNC/SPICE/termproxy) — no websocket proxy
- uvx / uv / pip / Docker (GHCR) install paths; optional
.[openapi]for mcpo - Local + GitHub CI (
ruff+pytest+ coverage + inventory + design invariants)
Planned (not implemented yet)
Phase C — heavy: SDN write CRUD, ACME order/renew, Ceph OSD/MON admin, cluster join/bootstrap, full VNC/SPICE websocket proxy, PBS direct admin, node reboot/shutdown — see coverage matrix and next-expansion.md.
Development
.\scripts\ci-local.ps1
After adding a tool: update definitions.py, README table, .cursor/research/proxmox-api-coverage.md, .cursor/research/next-expansion.md (if closing a planned row), and tests/expected_tools.py.
Status
- [x] Formal multi-domain Proxmox API coverage (171 tools)
- [x] Phase B + Phase D agent QOL tools
- [x] Phase F LXC day-2 + Phase F.1 VM network/push + create wait opt-in
- [x] v1.0 security hardening, code-design audit, full test suite
- [x] uvx
cursor-proxmox-mcp+ PyPI/GHCR release workflow - [x] Local + GitHub CI with coverage + design invariants
- [ ] Phase C heavy/dangerous endpoints (documented only)
License
MIT
Acknowledgments
Based on ProxmoxMCP / canvrno/ProxmoxMCP. Extended for Cursor IDE as a formal Proxmox VE integration.
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。