MCP server and CLI for managing Proxmox VE virtual machines and containers, including lifecycle actions, snapshots, backups, storage, firewall, cluster, and HA operations. It wraps write actions in a governance harness with audit logging, policy checks, risk tiers, and undo-token recording.
From the registry: Governed Proxmox VE VM/container ops — 23 MCP tools with audit, budget, undo & risk-tier guards.
$ uv tool install proxmox-aiops$ mkdir -p ~/.proxmox-aiops$ chmod 600 ~/.proxmox-aiops/.env$ proxmox-aiops doctorPlease install the `proxmox-aiops` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install uv** — Install the uv Python tool runner/installer to install the proxmox-aiops CLI and MCP server. Run: `uv tool install proxmox-aiops`
- **Create Proxmox AIops home directory** — Create the application directory that stores configuration, secrets, and audit data. Run: `mkdir -p ~/.proxmox-aiops`
- **Create Proxmox target configuration** — Create ~/.proxmox-aiops/config.yaml with a targets list describing your Proxmox VE target(s), including host, user/token ID, node, auth_kind, and SSL verification settings.
- **Create secret file** — Create ~/.proxmox-aiops/.env containing the Proxmox API token secret for each configured target, and restrict file permissions (README suggests chmod 600). Example secret variable name follows the target name pattern shown in the README. Run: `chmod 600 ~/.proxmox-aiops/.env`
Optional prerequisites:
- Validate setup — Run the built-in doctor command to verify configuration and connectivity. Run: `proxmox-aiops doctor`
Canonical MCP server config (stdio transport):
- command: `proxmox-aiops`
- args: ["mcp"]
- optional environment variables:
- `PROXMOX_AIOPS_HOME`: Optional path to relocate the Proxmox AIops home directory that contains config, secrets, and the local SQLite audit database. (example: `<your-proxmox-aiops-home-directory>`)
Note: The README also mentions an equivalent MCP entrypoint, `proxmox-aiops-mcp`, but `proxmox-aiops mcp` is the clearest canonical stdio shape. Server operation depends on local files in ~/.proxmox-aiops by default: a config.yaml with one or more targets and a .env file containing matching Proxmox API token secrets such as PROXMOX_<TARGET_NAME>_SECRET.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.PROXMOX_PVE_LAB_SECRETrequiredStores the Proxmox API token secret used for authentication in the example configuration.Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Persistent codebase knowledge graph. Survives session restarts and context compaction.
Validate oh-my-posh configurations and segment snippets against the official schema.