Proxmox Manager MCP Server

Manage Proxmox hypervisors through a Model Context Protocol server, providing a clean interface for nodes, VMs, and containers. Exposed over MCP by the proxmox manager mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Its toolset

Everything the assistant can do here goes through one of these:

• Prerequisites — Before starting, ensure you have: - [ ] Proxmox server hostname or IP - [ ] Proxmox API token (see API Token Setup) - [ ]
• get_nodes — 🖥️ pve-compute-01 • Status: ONLINE • Uptime: ⏳ 156d 12h • CPU Cores: 64 • Memory: 186.5 GB / 512.0 GB (36.4%)
• get_node_status — The get_node_status tool exposed by this server
• get_vms — 🗃️ prod-db-master (ID: 100) • Status: RUNNING • Node: pve-compute-01 • CPU Cores: 16 • Memory: 92.3 GB / 128.0 GB (72.1%)
• get_storage — The get_storage tool exposed by this server
• get_cluster_status — • Name: enterprise-cloud • Status: HEALTHY • Quorum: OK • Nodes: 4 ONLINE • Version: 8.1.3 • HA Status: ACTIVE • Resources: - Total CPU Cores: 192 -
• execute_vm_command — Output: ● nginx.service - A high performance web server and a reverse proxy server Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor

Configuration

You will need 8 environment variables: PYTHONPATH, PROXMOX_MCP_CONFIG, PROXMOX_HOST, PROXMOX_USER, PROXMOX_TOKEN_NAME, PROXMOX_TOKEN_VALUE, PROXMOX_PORT, PROXMOX_VERIFY_SSL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• UV package manager (recommended) - Python 3.10 or higher - Git - Access to a Proxmox server with API token credentials Before starting, ensure you have: - [ ] Proxmox server hostname or IP - [ ] Proxmox API token (see API Token Setup) - [ ] UV installed (pip install uv)

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the proxmox manager mcp server does with a few real requests.

When to reach for it

Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Proxmox Manager's toolset — Prerequisites, get_nodes, get_node_status and 4 more — is a fair guide to whether it matches your workflow. It is maintained by canvrno; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.