MCP server for full management of a Proxmox VE hypervisor, with local safety barriers
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"proxmox-model-context-protocol","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# proxmox-model-context-protocol An MCP (Model Context Protocol) server that lets an AI assistant such as Claude manage a Proxmox VE hypervisor. It has 118 tools for guests, snapshots, backups, storage, networking, firewall, SDN, users and ACLs, node administration and commands inside guests. `pve_api_call` reaches any other API endpoint. The server starts read-only. **Status: alpha.** Tool names, parameters and configuration may change between releases. Tested on single-node Proxmox VE 9.1 and 9.2. The server uses an API token with full privileges. Proxmox VE does not limit what the model can do with it; all safeguards described below run locally in this server. Keep clients read-only unless they need to change things, and review `critical.env`. ## Contents - [Features](#features) - [Safety model](#safety-model) - [Requirements](#requirements) - [Quick start](#quick-start) - [Connecting an MCP client](#connecting-an-mcp-client) - [Write mode and critical operations](#write-mode-and-critical-operations) - [Commands inside guests and on the node](#commands-inside-guests-and-on-the-node) - [Configuration reference](#configuration-reference) - [Command line](#command-line) - [Limitations](#limitations) - [Security and license](#security-and-license) ## Features | Area | Examples | |---|---| | Inventory and monitoring | cluster resources, guest and node status, metrics, tasks and task logs, node journal | | Guests | create a VM or container, clone, start, shut down, stop, reboot, delete, convert to a template | | Configuration | guest config, disk resize and move, migration, pending changes | | Snapshots and backups | snapshots, rollback, backups, backup jobs and schedules, restore, retention, guests without a backup | | Storage | storage definitions, content, download from a URL, upload, appliance templates, volume protection | | Networking | node interfaces with a review of pending changes, firewall rules, aliases and IP sets, SDN zones, VNets and subnets | |…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.