proxmox-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROXMOX_TOKEN | Yes | API token in the form user@realm!tokenid=uuid. | |
| PROXMOX_API_URL | Yes | Base URL of the Proxmox VE API, including the port, e.g. https://proxmox.example.com:8006. | |
| PROXMOX_VERIFY_SSL | No | Set to false to skip TLS verification (self-signed certs). Any other value keeps it on. | true |
| PROXMOX_CLUSTER_CACHE_SECONDS | No | TTL for cached cluster snapshots. 0 disables caching. | 30 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| proxmox_statusA | Return the current state of the Proxmox cluster: nodes, VMs, containers, and storage. |
| proxmox_findA | Find a VM or container by name (partial matches are supported). Returns the vmid, node, and type — useful before running admin actions. |
| proxmox_task_statusB | Check the status of a running or completed Proxmox task by its UPID. |
| proxmox_vm_actionB | Run a lifecycle action on a VM. action: start | stop | shutdown | reset | suspend | resume |
| proxmox_delete_vmA | Permanently delete a VM (the VM must be stopped first). Returns the task UPID — use proxmox_task_status to check whether it finished. |
| proxmox_container_actionB | Run a lifecycle action on a container. action: start | stop | shutdown | reboot | suspend | resume |
| proxmox_delete_containerA | Permanently delete a container (the container must be stopped first). Returns the task UPID — use proxmox_task_status to check whether it finished. |
| proxmox_node_actionC | Run an action on a Proxmox node. action: reboot | shutdown |
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 8 tools
Each tool targets a distinct resource (container, VM, node, cluster status) or action (delete, find, task status). No overlap in purpose.
All tool names start with 'proxmox_', but the second part varies between 'noun_action' (container_action, vm_action), 'delete_noun' (delete_container), and standalone nouns (status, find). Mostly consistent with minor deviations.
8 tools cover core lifecycle actions, deletion, finding, and cluster status without being excessive or sparse.
The set lacks creation tools for VMs and containers, which is a notable gap for a complete lifecycle surface. Basic operations are covered, but creation is missing.