Skip to main content
Glama
Proxmox VE MCP server

Proxmox VE MCP server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PVE_URLYesThe URL of your Proxmox VE REST API.
PVE_SAMPLENoSet to 0 when using your own Proxmox VE instead of the bundled SAMPLE guests.
PVE_TOKEN_IDYesThe Proxmox API token ID in the form user@realm!name.
PVE_VERIFY_TLSNoSet to 0 to disable TLS certificate verification for the self-signed local certificate. Keep TLS verification enabled for a real installation.
PVE_TOKEN_SECRETYesThe Proxmox API token secret.

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
overviewB

Nodes (CPU, memory, uptime), storage use, how many guests run or are stopped, and the backup jobs.

find_guestsC

VMs and containers with status, tags, CPU and memory in use now, and uptime.

guest_detailsB

One guest: status and use, cores and disks, notes, its snapshots, its last backup and whether a backup job covers it, and its recent tasks from Proxmox's task log (who did what, when).

needs_attentionB

Guests no backup job covers, overdue backups, production guests that are stopped, old snapshots, storage filling up, and guests short of memory.

power_guestA

Start, cleanly shut down, or reboot a VM or container. The first call changes nothing and returns a summary and a confirmation code; it happens only on a second call with the code, after the user has said yes.

snapshot_guestA

Take a snapshot of a VM or container (it keeps running). The first call changes nothing and returns a summary and a confirmation code; the snapshot is taken only on a second call with the code, after the user has said yes.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 6 tools

Disambiguation4/5

Each tool targets a distinct concern: health triage (needs_attention), cluster-wide status (overview), guest listing (find_guests), single-guest drill-down (guest_details), power actions, and snapshots. The only mild overlaps are needs_attention vs overview (both aggregate health) and find_guests vs guest_details (list vs detail), but the descriptions make the boundaries clear enough.

Naming Consistency3/5

All names use snake_case, but the conventions are mixed: find_guests/power_guest/snapshot_guest are verb_noun, guest_details is noun_noun, and needs_attention/overview are bare noun phrases with no verb. It remains readable, but the pattern is not predictable across the set.

Tool Count4/5

Six tools is a reasonable, well-scoped set for a Proxmox monitoring/ops surface, and each tool clearly earns its place. It is on the lean side for a broad hypervisor domain, but not thin enough to be a problem.

Completeness3/5

Read paths (overview, guest listing/detail, attention scan) and two guarded write actions (power, snapshot) are covered, but major lifecycle operations are missing: create/clone/delete guest, backup job creation/run/restore, and storage or migration actions. An agent asked to provision or remove a VM, or manage backups, would hit a dead end.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues