Proxmox MCP Server
Provides tools to manage Proxmox VE and Proxmox Datacenter Manager, enabling operations on nodes, VMs, containers, storage, and more via their API.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Proxmox MCP Serverlist all VMs on node pve1"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Proxmox MCP Server
MCP server for Proxmox VE and Proxmox Datacenter Manager (PDM), covering every API endpoint: 993 operations total behind 6 consolidated catalog-backed tools rather than one tool per endpoint.
Surface | Endpoints | Read (GET) | Write (POST/PUT/DELETE) | Tools |
PVE ( | 675 | 340 | 335 |
|
PDM ( | 318 | 199 | 119 |
|
Every endpoint is mapped, documented, and available via the catalog. Reads execute by default; writes are blocked unless explicitly enabled via an environment variable (read-only safety gate). Destructive operations require an additional per-call confirm:true.
Each surface has its own catalog (src/catalog-pve/, src/catalog-pdm/) and its own credentials. Configure one or both.
How it works
The catalog is the single source of truth, generated deterministically from Proxmox's own published API schema (apidoc.js): no field loss, no hand-maintenance.
scripts/extract.mjs <pve|pdm>flattensapidoc.js'sapiSchematree into one faithful raw spec per(method, path)endpoint.scripts/assemble-catalog.mjs <pve|pdm>derivesresource,category,destructiveflag, required-param flags, param routing (query vs body), and a request sample; writes the shippablesrc/catalog-<surface>/endpoints/<operationId>.json+index.json.
The six tools follow discover, describe, call:
Tool | Purpose |
| Discover endpoints (operationId, method, path, category, read/write, destructive). |
| Full spec: path params, query/body params (types, formats, enums, constraints), response schema, required permissions, request sample, and any enrichment. |
| Validates operationId + required path params, enforces the write gate, then executes. |
operationId = <method>_<path> lowercased with {placeholders}/punctuation collapsed to _ (e.g. get_nodes, post_nodes_node_qemu, delete_nodes_node_qemu_vmid_snapshot_snapname). Unique across each surface (zero collisions).
Related MCP server: proxmox-mcp
Setup
Quick start (npx)
Add to your MCP client config (.mcp.json for Claude Code, claude_desktop_config.json for Claude Desktop):
{
"mcpServers": {
"proxmox": {
"command": "npx",
"args": ["-y", "@nightsquawktech/proxmox-mcp-server"],
"env": {
"PVE_HOST": "pve.example.com",
"PVE_TOKEN_ID": "root@pam!mcp",
"PVE_TOKEN_SECRET": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"PVE_TLS_REJECT_UNAUTHORIZED": "false"
}
}
}
}Add the PDM_* equivalents to also configure a Proxmox Datacenter Manager instance. See .mcp.example.json for a full example.
From source
npm install
npm run buildThen configure credentials (see .env.example) and point your MCP client at dist/index.js.
Authentication
Create a Proxmox API token (Datacenter > Permissions > API Tokens). The PVE auth header is PVEAPIToken=USER@REALM!TOKENID=SECRET.
Variable | Surface | Notes |
| PVE |
|
| PVE | e.g. |
| PVE | The token UUID |
| PVE |
|
| PVE | Override the |
| PDM | Same keys with |
PDM note: PDM is newer and its token scheme/separator may differ from PVE. If PDM auth fails, adjust
PDM_AUTH_SCHEME/PDM_AUTH_SEP(or set the fullPDM_BASE_URL), no code change required.
Write gate (read-only by default)
Writes (POST/PUT/DELETE) are blocked unless enabled:
PROXMOX_ALLOW_WRITES=trueenables writes for all surfaces, orPVE_ALLOW_WRITES=true/PDM_ALLOW_WRITES=trueper surface.
Even with writes enabled, endpoints flagged destructive (delete, stop, reset, reboot, suspend, rollback, destroy, wipe, migrate) require confirm:true on the call to execute.
Regenerating the catalog
The shipped catalog lives committed under src/catalog-pve/ and src/catalog-pdm/. The raw Proxmox API dumps under _source/ are gitignored: they are re-downloadable inputs, regenerated via npm run regen. To refresh from a new Proxmox release:
# 1. Download the schema (or copy /usr/share/pve-docs/api-viewer/apidoc.js off a host)
# PVE: https://pve.proxmox.com/pve-docs/api-viewer/apidoc.js -> _source/pve-apidoc.js
# PDM: https://pdm.proxmox.com/docs/api-viewer/apidoc.js -> _source/pdm-apidoc.js
# 2. Regenerate
npm run regen # = extract + assemble for both surfaces
npm run buildOptional enrichment layer
src/catalog-<surface>/enrichment/<operationId>.json may add additive-only documentation (usageNotes, examples, destructiveReason, tips, relatedOperations) merged into describe_endpoint output. It never alters the authoritative structural fields (params/types/returns), which come straight from Proxmox.
Architecture
Built on NightSquawk's catalog-backed meta-tool pattern (same as @nightsquawktech/appfolio-mcp-server): consolidated list/describe/call tools over a generated JSON catalog keep tool count tiny while indexing the entire API. TypeScript + @modelcontextprotocol/sdk, stdio transport, undici for TLS-configurable fetch.
License
Licensed under the GNU AGPL v3.0. Free for personal and open-source use.
Organizations that cannot comply with the AGPL can purchase a commercial license. See COMMERCIAL.md or contact hello@nightsquawk.tech.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/NightSquawk/proxmox-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server