proxmox-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PVE_BASE_URL | Yes | Proxmox VE API base URL (e.g., https://proxmox.lan:8006) | |
| PVE_PASSWORD | No | Proxmox password | |
| PVE_USERNAME | No | Proxmox username (e.g., user@pam) | |
| PVE_VERIFY_SSL | No | Whether to verify SSL certificate (true/false). Default is false for self-signed certs. | true |
| PVE_API_TOKEN_ID | No | Proxmox API token ID (e.g., user@pam!token-name) | |
| PVE_API_TOKEN_SECRET | No | Proxmox API token secret | |
| PVE_ALLOW_INSECURE_HTTP | No | Allow plain HTTP for Proxmox (true/false). Default is false. | false |
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 |
|---|---|
| pve_get_versionA | Return Proxmox VE version information. |
| pve_get_cluster_statusA | Return Proxmox cluster status. |
| pve_list_nodesA | List Proxmox nodes. |
| pve_list_resourcesB | List cluster resources, optionally filtered by type such as vm, storage, node. |
| pve_list_vmsA | List QEMU VMs and LXC containers from cluster resources. |
| pve_get_vm_statusB | Get current status for a QEMU VM or LXC container. |
| pve_get_vm_configA | Get config for a QEMU VM or LXC container. |
| pve_list_storageA | List storage globally or for a node. |
| pve_list_backupsB | List backup content for a node storage. |
| pve_get_task_statusC | Get task status by UPID. |
| pve_get_node_metricsC | Get node status and metrics. |
| pve_start_vmC | Start a VM/container. Requires confirm=true. |
| pve_shutdown_vmB | Gracefully shut down a VM/container. Requires confirm=true. |
| pve_stop_vmA | Hard stop a VM/container. Requires confirm=true. |
| pve_reboot_vmA | Reboot a VM/container. Requires confirm=true. |
| pve_suspend_vmC | Suspend a VM/container. Requires confirm=true. |
| pve_resume_vmB | Resume a VM/container. Requires confirm=true. |
| pve_create_snapshotB | Create a VM/container snapshot. Requires confirm=true. |
| pve_delete_snapshotA | Delete a VM/container snapshot. Requires confirm=true. |
| pve_rollback_snapshotC | Rollback to a snapshot. Requires confirm=true. |
| pve_migrate_vmB | Migrate a VM/container to another node. Requires confirm=true. |
| pve_clone_vmC | Clone a QEMU VM. Requires confirm=true. |
| pve_create_lxcC | Create an LXC container. Requires confirm=true. |
| pve_create_qemu_vmC | Create a QEMU VM. Requires confirm=true. |
| pve_delete_vmC | Delete a VM/container. Requires confirm=true. |
| pve_resize_diskC | Resize a QEMU VM disk. Requires confirm=true. |
| pve_set_vm_configC | Update VM/container config. Requires confirm=true. |
| pve_api_requestC | Call any Proxmox API path. GET is allowed; POST/PUT/DELETE require confirm=true. |
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 28 tools
Most tools target a distinct resource/action combination, and lifecycle verbs like start, shutdown, stop, and reboot are clear. The main ambiguity comes from the overlapping read-only listing tools (list_resources, list_vms, list_nodes, list_storage), though the descriptions help differentiate them. pve_api_request is a deliberate escape hatch rather than a source of confusion.
All tools follow a consistent pve_verb_noun snake_case pattern. Verbs are predictable: list/get for reads, create/delete/set for mutations, and explicit lifecycle verbs for VM/container actions. There are no mixed naming conventions or vague generic names.
28 tools exceeds the 25+ threshold and feels heavy for a single server. Several listing and config tools could be consolidated, and the generic pve_api_request already provides broad fallback coverage. The domain is broad but the surface is larger than necessary.
Core VM/container lifecycle, snapshot management, migration, cloning, creation, deletion, config updates, and disk resize are covered. Notable gaps like LXC clone/resize and advanced storage/network management are not directly exposed, but pve_api_request provides a workaround. The surface has no critical dead ends.