pve-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| host | Yes | Proxmox VE node hostname or IP address | |
| port | Yes | Proxmox VE API port (default 8006) | |
| token_name | Yes | API token name | |
| token_user | Yes | API token user ID in the form user@realm | |
| token_secret | Yes | API token secret (UUID) |
Capabilities
Features and capabilities supported by this server
| 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_nodesA | List all nodes in the Proxmox cluster with status, memory, and uptime. |
| pve_list_vmsA | List QEMU VMs in the Proxmox cluster. Optionally filter by name (supports * wildcard) or status. |
| pve_get_vm_disksB | Get disk/storage layout for a specific VM: storage pool, path, size per disk. |
| pve_get_storageA | List storage pools with capacity info (type, total GB, free GB, used %). |
| pve_get_snapshotsA | List Proxmox-level snapshots for a VM (or all VMs if no name given). |
| pve_get_vm_configB | Full VM config: CPU type, BIOS, boot order, NIC list, disk config, tags, description. |
| pve_get_vm_statusB | Live VM metrics: CPU%, RAM used/max, PID, uptime, QMP status, lock, tags. |
| pve_get_cluster_resourcesA | All cluster resources in one bulk call: VMs, nodes, storage, LXC. Fast overview. |
| pve_list_lxcA | List LXC containers across all nodes (name, status, RAM, CPU, disk). |
| pve_get_node_statusA | Detailed node metrics: CPU%, RAM, swap, load averages, disk, kernel, PVE version. |
| pve_get_node_networkB | All NICs and bridges on a node: IP, netmask, gateway, MAC, bridge ports. |
| pve_get_node_disksA | Physical disks on a node: model, serial, size, type, S.M.A.R.T. health, wear. |
| pve_get_storage_contentA | List content of a storage pool: VM images, ISOs, backups, templates. |
| pve_get_cluster_tasksC | Cluster task history: migrations, backups, clones, snapshot operations. |
| pve_get_backup_jobsA | List configured vzdump backup jobs: schedule, storage, VMs, compression, mode. |
| pve_get_ha_statusA | HA cluster status and list of HA-managed resources. |
| pve_get_replication_jobsA | List VM replication jobs: source, target, schedule, rate, status. |
| pve_get_firewall_rulesB | Firewall rules for a node or a specific VM (pass vm_name for VM-level rules). |
| pve_get_vm_agentA | QEMU guest agent data: IP addresses, OS info, hostname. Requires agent installed inside VM. |
| pve_get_vm_rrddataB | Historical metrics for a VM: CPU, RAM, net I/O, disk I/O over time. |
| pve_get_node_rrddataC | Historical metrics for a node: CPU, RAM, net, disk over time. |
| pve_get_node_servicesA | systemd services on a node: pveproxy, pvedaemon, pve-ha-*, corosync, etc. |
| pve_get_node_pciC | PCI devices available for passthrough on a node (IOMMU groups, vendor, class). |
| pve_get_vm_pendingA | Config changes pending reboot for a VM (diff between live and stored config). |
| pve_get_node_certificatesC | TLS certificates on a node: subject, issuer, fingerprint, expiry dates. |
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/UriWise/pve-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server