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) |
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_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 | |
TDQS
Scored across 25 tools
Every tool targets a distinct resource and aspect, such as node status vs. node network vs. node PCI devices. Even similar-sounding tools like pve_get_node_disks and pve_get_node_pci are clearly separated by described hardware type.
All tools share the pve_ prefix and use lowercase with underscores, but two tools use 'list_' (pve_list_vms, pve_list_lxc) while the rest use 'get_', creating a minor inconsistency in verb choice.
With 25 tools, the server sits at the heavy end of the borderline range. The count is reasonable for a comprehensive read-only monitoring surface, but it feels ample and lacks any action-oriented tools to balance it.
The toolset is entirely read-only, offering no ability to create, start, stop, delete, or modify virtual machines or containers. This leaves major management workflows completely unsupported, making it severely incomplete for a Proxmox VE server.