proxmox-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level: debug, info, warn, error (default info) | info |
| PROXMOX_HOST | Yes | Full base URL of the Proxmox server, e.g. https://pve.local:8006 | |
| PVE_READONLY | No | Set to 'true' (default) to register only read-only tools; 'false' enables write tools | true |
| PROXMOX_TOKEN_ID | Yes | API token ID in the format USER@REALM!TOKENID | |
| PVE_NODE_ALLOWLIST | No | Optional comma-separated list of node names to restrict operations | |
| PVE_VMID_ALLOWLIST | No | Optional comma-separated list of guest IDs to restrict operations | |
| PVE_TASK_TIMEOUT_MS | No | Timeout for waiting for asynchronous tasks in milliseconds (default 600000) | 600000 |
| PROXMOX_INSECURE_TLS | No | Set to 'true' to accept self-signed certificates (only for labs) | false |
| PROXMOX_TOKEN_SECRET | Yes | API token secret (UUID) | |
| PROXMOX_REQUEST_TIMEOUT_MS | No | Per-request timeout in milliseconds (default 30000) | 30000 |
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_versionA | Proxmox VE version of the connected node (version, release, repository id). Tells you which version-gated features are available. |
| pve_list_nodesA | List all nodes in the Proxmox cluster with their online status and load. |
| pve_node_statusA | Detailed status of a single node: CPU, memory, uptime, kernel and PVE version. |
| pve_cluster_resourcesA | Single combined view of cluster resources (VMs, containers, storage, nodes). Use the type filter to narrow the result. |
| pve_list_tasksA | Recent task log for a node, including UPID, type, status and exit status. Useful to check on a long-running operation that may have outlived a tool call timeout. |
| pve_list_vmsA | List QEMU VMs. With a node, lists that node directly; without one, returns every VM in the cluster from the resource index. |
| pve_vm_statusA | Current runtime status of a VM (running/stopped, CPU, memory, uptime). |
| pve_vm_configA | Full configuration of a VM (cores, memory, disks, network, boot order). |
| pve_list_containersA | List LXC containers. With a node, lists that node directly; without one, returns every container in the cluster from the resource index. |
| pve_lxc_statusA | Current runtime status of a container (running/stopped, CPU, memory, uptime). |
| pve_lxc_configA | Full configuration of a container (cores, memory, rootfs, network, features). |
| pve_list_snapshotsA | List snapshots of a VM or container, including the "current" pseudo-snapshot. |
| pve_list_storageA | List storages visible from a node, with type, enabled content and free space. |
| pve_storage_contentA | List the volumes on a storage: ISO images, container templates, disk images or backups. Use the content filter to narrow the listing. |
| pve_list_networkA | List network interfaces on a node (bridges, bonds, physical NICs, VLANs). Pending, not-yet-applied changes are included. |
| pve_list_backupsB | List backup archives stored on a storage. |
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
- 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/k-krawczyk/proxmox-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server