Official description2 sourcesMCP servers2d ago
AIops-tools/Proxmox-AIops
Governed Proxmox VE ope
View on GitHub ↗Direct link · no redirect page
Config template (adjust for your client)
claude mcp add proxmox-aiops -- npx -y proxmox-aiops
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
- Star count
- 3 ★ · AIops-tools/Proxmox-AIops · read from the GitHub search API · (checked 2026-10-16 20:00:20)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-15 · last seen 2026-10-16 · seen 2× · listed by 2 sources
- Score
- score 203 · 3 ★ · 2 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
AIops-tools/Proxmox-AIops；first catalogued 2026-10-15；last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.Third-party quality signals
Proxmox AIops
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
> **Disclaimer**: Community-maintained open-source project. **Not affiliated with, endorsed by, or sponsored by Proxmox Server Solutions GmbH.** "Proxmox" is a trademark of its owner. MIT licensed.
AI-powered Proxmox VE VM and container lifecycle operations with a **built-in
governance harness** — unified audit log, token/runaway budget
guard, undo-token recording, and descriptive risk-tier labels. Self-contained:
no external dependencies beyond proxmoxer and the MCP SDK. Coverage is not
yet exhaustive across every Proxmox operation.
> **Verification status**: live-verified against real Proxmox VE 8.4.19 across
> three rounds — read-only surfaces, the QEMU write surface, and a two-node
> cluster (quorum, live migration, move-disk, a backup that actually
> succeeded). Rounds 2 and 3 each found a real bug the mocks could not see. See
> docs/VERIFICATION.md for exactly what was proven and
> what is still uncovered.
What works
- **CLI** (proxmox-aiops ...): vm list/get/config/start/stop/shutdown/reboot/reconfigure/clone/delete/migrate, vm resize-disk/move-disk/agent-ping, vm snapshot-create/snapshot-delete/snapshot-list/snapshot-rollback, backup create/list/restore, ct list/start/stop, cluster nodes/status/task-status/resources/node-status/task-log/next-vmid, ha status/resources, pool list/members, firewall vm-rules/cluster-status, storage list/content, diagnose node-pressure/guest-health, undo list/apply, init, secret set/list/rm/migrate/rotate-password, doctor, mcp.
- **MCP server** (proxmox-aiops mcp or proxmox-aiops-mcp): **43 tools**, every one wrapped with the bundled @governed_tool harness.
- **Diagnostics / RCA** (read-only): diagnose node-pressure ranks cluster nodes by CPU/memory/root-fs pressure; diagnose guest-health scans VMs/containers for stopped guests, memory saturation, and disks near full. Every finding cites the measured number that tripped it and a concrete action — transparent heuristics, not a black-box verdict.
- **Credentials**: proxmox-aiops init (onboarding wizard) and proxmox-aiops secret ... manage an encrypted secret store — no plaintext passwords in config.yaml.
- **Reversibility**: write ops with a clean inverse (start/stop/shutdown/reconfigure/clone/migrate/snapshot-create/move-disk, container start/stop, and restore-into-a-free-vmid) record an inverse undo descriptor; irreversible ops (delete, snapshot-rollback, forced restore) declare none and are tagged high risk. Disk resize is grow-only (shrink refused).
- **Async tasks**: Proxmox writes return a task UPID — poll completion with cluster task-status / read lines with cluster task-log (the runaway budget guard prevents poll loops from running away).
What this tool does, and does not, decide
It delivers Proxmox VE operations — reads and writes — accurately and
efficiently, and records every one of them. It does **not** decide whether a write is allowed to
happen. That is the agent's judgement, or the permission of the account you connect it with:
use a Proxmox VE user or API token granted only read privileges (no VM.*/Datastore.* write roles),
AI-powered Proxmox VE VM and container lifecycle operations with a **built-in
governance harness** — unified audit log, token/runaway budget
guard, undo-token recording, and descriptive risk-tier labels. Self-contained:
no external dependencies beyond proxmoxer and the MCP SDK. Coverage is not
yet exhaustive across every Proxmox operation.
> **Verification status**: live-verified against real Proxmox VE 8.4.19 across
> three rounds — read-only surfaces, the QEMU write surface, and a two-node
> cluster (quorum, live migration, move-disk, a backup that actually
> succeeded). Rounds 2 and 3 each found a real bug the mocks could not see. See
> docs/VERIFICATION.md for exactly what was proven and
> what is still uncovered.
What works
- **CLI** (proxmox-aiops ...): vm list/get/config/start/stop/shutdown/reboot/reconfigure/clone/delete/migrate, vm resize-disk/move-disk/agent-ping, vm snapshot-create/snapshot-delete/snapshot-list/snapshot-rollback, backup create/list/restore, ct list/start/stop, cluster nodes/status/task-status/resources/node-status/task-log/next-vmid, ha status/resources, pool list/members, firewall vm-rules/cluster-status, storage list/content, diagnose node-pressure/guest-health, undo list/apply, init, secret set/list/rm/migrate/rotate-password, doctor, mcp.
- **MCP server** (proxmox-aiops mcp or proxmox-aiops-mcp): **43 tools**, every one wrapped with the bundled @governed_tool harness.
- **Diagnostics / RCA** (read-only): diagnose node-pressure ranks cluster nodes by CPU/memory/root-fs pressure; diagnose guest-health scans VMs/containers for stopped guests, memory saturation, and disks near full. Every finding cites the measured number that tripped it and a concrete action — transparent heuristics, not a black-box verdict.
- **Credentials**: proxmox-aiops init (onboarding wizard) and proxmox-aiops secret ... manage an encrypted secret store — no plaintext passwords in config.yaml.
- **Reversibility**: write ops with a clean inverse (start/stop/shutdown/reconfigure/clone/migrate/snapshot-create/move-disk, container start/stop, and restore-into-a-free-vmid) record an inverse undo descriptor; irreversible ops (delete, snapshot-rollback, forced restore) declare none and are tagged high risk. Disk resize is grow-only (shrink refused).
- **Async tasks**: Proxmox writes return a task UPID — poll completion with cluster task-status / read lines with cluster task-log (the runaway budget guard prevents poll loops from running away).
What this tool does, and does not, decide
It delivers Proxmox VE operations — reads and writes — accurately and
efficiently, and records every one of them. It does **not** decide whether a write is allowed to
happen. That is the agent's judgement, or the permission of the account you connect it with:
use a Proxmox VE user or API token granted only read privileges (no VM.*/Datastore.* write roles),
- Source
- awesome · https://github.com/AIops-tools/Proxmox-AIops
- Browse by field
- MCP servers
- Traction
- 3 ★
- added
- yesterday
More in MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.