proxmox-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROXMOX_HOST | Yes | The URL of your Proxmox node (e.g., https://192.168.100.10:8006) | |
| PROXMOX_TOKEN_ID | Yes | The Proxmox API token ID (e.g., mcp@pve!mcp-token) | |
| PROXMOX_TLS_INSECURE | No | Set to 'true' to disable TLS certificate verification (use for self-signed certs) | true |
| PROXMOX_TOKEN_SECRET | Yes | The Proxmox 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_nodesA | List all nodes in the Proxmox cluster with their status. |
| get_node_statusA | Get detailed status (CPU, memory, uptime) for a specific node. |
| list_storageB | List storage pools available on a node. |
| list_resourcesA | List all VMs (qemu) and containers (lxc) on a node with their current status. |
| list_templatesA | List available CT templates and ISO images on a node's storage. |
| get_resource_statusB | Get current status (running/stopped, resource usage) of a specific VM or container. |
| power_actionB | Start, stop, shutdown, or reboot a VM or container. |
| create_lxcA | Create a new LXC container from a template. Requires confirming the configuration with the user before calling. |
| create_vmB | Create a new QEMU VM (empty, optionally with an ISO attached for OS installation). Requires confirming the configuration with the user before calling. |
| clone_resourceB | Clone an existing VM or container template to create a new one. Requires confirming the configuration with the user before calling. |
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 10 tools
Each tool has a clear, distinct purpose: creation, cloning, status queries, listing, and power actions. No two tools overlap in functionality, minimizing confusion for an agent.
All tools follow a consistent snake_case verb_noun pattern (e.g., create_vm, list_nodes), making the naming predictable and easy to navigate.
With 10 tools, the server is well-scoped for Proxmox management, covering essential operations without unnecessary bloat or deficit.
Core CRUD-like operations are present: create, read (list/status), update (power action), but delete functionality is missing. This minor gap prevents full lifecycle management.