mcp-server-proxmox
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROXMOX_HOST | Yes | Proxmox server hostname or IP | |
| PROXMOX_PORT | No | Proxmox API port (default: 8006) | 8006 |
| PROXMOX_REALM | No | Authentication realm (default: pam) | pam |
| PROXMOX_TOKEN | No | Proxmox API token ID | |
| PROXMOX_PASSWORD | No | Proxmox password | |
| PROXMOX_USERNAME | Yes | Proxmox username (e.g., root) | |
| PROXMOX_TOKEN_NAME | No | Proxmox API token name | |
| PROXMOX_VERIFY_SSL | No | Verify SSL certificate (true/false) | true |
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 Proxmox nodes in the cluster |
| list_vmsA | List virtual machines on a specific node or all nodes |
| list_containersA | List LXC containers on a specific node or all nodes |
| get_vm_statusC | Get detailed status information for a specific VM |
| start_vmC | Start a virtual machine |
| stop_vmB | Stop a virtual machine |
| get_node_statusC | Get detailed status information for a Proxmox node |
| create_containerB | Create and provision a new LXC container with full automation (Netbox, NPM, DNS, monitoring, backups) |
| provision_stackC | Provision a pre-configured container stack (template) with common settings |
| get_available_ctidA | Get next available CTID in a specific function range |
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
Most tools have clearly distinct resource+action pairs; list_vms/get_vm_status and list_nodes/get_node_status are separated by scope. The main ambiguity is between create_container and provision_stack, which both provision containers and could lead to misselection.
All tool names follow a consistent snake_case verb_noun pattern (list_*, get_*, start_*, stop_*, create_*, provision_*). Naming is predictable and readable across the entire set.
Ten tools is a well-scoped set for a Proxmox management server, covering node inspection, VM/container listing, status lookup, VM power control, and container provisioning without feeling bloated or too thin.
The set covers listing, status, VM start/stop, and container creation, but it lacks obvious lifecycle operations: no VM creation/update/delete, no container start/stop/delete, and no management of provisioned stacks. This leaves significant gaps for normal Proxmox administration workflows.