Proxmox MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PDM_HOST | No | Proxmox Datacenter Manager hostname (expands to https://<host>:8443/api2/json) | |
| PVE_HOST | No | Proxmox VE hostname (expands to https://<host>:8006/api2/json) | |
| PDM_AUTH_SEP | No | Override the default '=' separator in the auth header | |
| PDM_BASE_URL | No | Full Proxmox Datacenter Manager API base URL (alternative to PDM_HOST) | |
| PDM_TOKEN_ID | No | Proxmox Datacenter Manager API token ID | |
| PVE_AUTH_SEP | No | Override the default '=' separator in the auth header | |
| PVE_BASE_URL | No | Full Proxmox VE API base URL (alternative to PVE_HOST) | |
| PVE_TOKEN_ID | No | Proxmox VE API token ID (e.g., root@pam!mcp) | |
| PDM_AUTH_SCHEME | No | Override the default PDMAPIToken authentication scheme | |
| PVE_AUTH_SCHEME | No | Override the default PVEAPIToken authentication scheme | |
| PDM_ALLOW_WRITES | No | Set to 'true' to enable write operations for PDM surface | |
| PDM_TOKEN_SECRET | No | Proxmox Datacenter Manager API token secret | |
| PVE_ALLOW_WRITES | No | Set to 'true' to enable write operations for PVE surface | |
| PVE_TOKEN_SECRET | No | Proxmox VE API token secret (UUID) | |
| PROXMOX_ALLOW_WRITES | No | Set to 'true' to enable write operations for all surfaces | |
| PDM_TLS_REJECT_UNAUTHORIZED | No | Set to 'false' to accept self-signed certificates (default 'true') | |
| PVE_TLS_REJECT_UNAUTHORIZED | No | Set to 'false' to accept self-signed certificates (default 'true') |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pve_list_endpointsA | List Proxmox VE API endpoints (operationId, method, path, category, description, read/write, destructive). Filter by category, resource, method, reads/writes, or search. Use this to discover an endpoint, then pve_describe_endpoint for its parameters and pve_call_endpoint to execute it. |
| pve_describe_endpointA | Get the full spec for one Proxmox VE endpoint: method, path, path params, query/body params (with types, formats, enums, constraints), the response schema, required permissions, and a request sample. Call before pve_call_endpoint so you send exactly the right params. |
| pve_call_endpointA | Call a Proxmox VE API endpoint and return its JSON response. Validates the operationId and required path params against the catalog, enforces the read-only write gate, then executes. Reads (GET) always run; writes (POST/PUT/DELETE) run only when enabled via PROXMOX_ALLOW_WRITES=true (all surfaces) or PVE_ALLOW_WRITES=true (this surface only). Use pve_describe_endpoint first to learn the exact params. |
| pdm_list_endpointsA | List Proxmox Datacenter Manager API endpoints (operationId, method, path, category, description, read/write, destructive). Filter by category, resource, method, reads/writes, or search. Use this to discover an endpoint, then pdm_describe_endpoint for its parameters and pdm_call_endpoint to execute it. |
| pdm_describe_endpointA | Get the full spec for one Proxmox Datacenter Manager endpoint: method, path, path params, query/body params (with types, formats, enums, constraints), the response schema, required permissions, and a request sample. Call before pdm_call_endpoint so you send exactly the right params. |
| pdm_call_endpointA | Call a Proxmox Datacenter Manager API endpoint and return its JSON response. Validates the operationId and required path params against the catalog, enforces the read-only write gate, then executes. Reads (GET) always run; writes (POST/PUT/DELETE) run only when enabled via PROXMOX_ALLOW_WRITES=true (all surfaces) or PDM_ALLOW_WRITES=true (this surface only). Use pdm_describe_endpoint first to learn the exact params. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- 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