@bakhshb/proxmox-mcp-openapi
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROXMOX_URL | Yes | Base URL including /api2/json, e.g., https://pve.example.com:8006/api2/json | |
| PROXMOX_TIMEOUT | No | Request timeout in ms | 30000 |
| PROXMOX_INSECURE | No | Skip TLS cert verification (for self-signed certs) | false |
| PROXMOX_SSH_PORT | No | SSH port | 22 |
| PROXMOX_SSH_USER | No | SSH username | root |
| PROXMOX_API_TOKEN | Yes | Token in user@realm!tokenid=secret format | |
| PROXMOX_SSH_KEY_PATH | No | Path to SSH private key | ~/.ssh/proxmox_mcp |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| proxmox-apiA | Execute any Proxmox VE API operation. Specify the path from the OpenAPI spec (e.g. /nodes/{node}/qemu) and optional path params, query params, or body. HTTP method is auto-detected from the spec. Use proxmox-api-schema to discover paths and parameters. |
| proxmox-api-schemaA | Discover Proxmox VE API operations and their parameters from the OpenAPI spec. Call with no args for a tag summary, with tag to list operations, or with path for full parameter details. |
| proxmox-execute-container-commandA | Execute a shell command inside a running LXC container via SSH + pct exec. Uses SSH key to connect to the Proxmox node and runs 'pct exec -- ' inside the container. Requires the container to be running. Configure SSH via PROXMOX_SSH_KEY_PATH, PROXMOX_SSH_USER, PROXMOX_SSH_PORT environment variables. |
| proxmox-execute-vm-commandA | Execute a command inside a running VM via QEMU guest agent. The VM must have the QEMU guest agent installed and running. Pass |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The schema-discovery and generic execution tools are clearly separated, and the two command tools are distinguished by target (LXC container vs QEMU VM). There is mild overlap because proxmox-api could invoke the same guest-agent endpoints that proxmox-execute-vm-command wraps, but the descriptions make the intended use clear.
All tools share the proxmox- prefix and use lowercase hyphenated names, but the API tools are noun-style (proxmox-api, proxmox-api-schema) while the command tools are verb-noun-style (proxmox-execute-...-command). This is readable and grouped, yet the verb/noun convention is not consistent across the set.
Four tools is within the ideal range. The schema-discovery plus generic-execution pair makes the full Proxmox API available without requiring dozens of endpoint-specific tools, and the two command-execution tools add distinct practical guest operations.
Because proxmox-api can execute any operation from the OpenAPI spec, the tool set covers the entire Proxmox management API surface. The schema tool provides the necessary discovery loop, and the container/VM command tools cover common guest execution workflows.