Proxmox SSH MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROXMOX_HOST | No | The Proxmox host IP address | 192.168.1.100 |
| PROXMOX_PORT | No | The SSH port for the Proxmox host | 22 |
| PROXMOX_USER | No | The Proxmox username | root |
| PROXMOX_KEY_PATH | No | The path to the private SSH key used for authentication | ~/.ssh/id_ed25519 |
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 |
|---|---|
| proxmox_run_host_commandC | Execute a command on the Proxmox host via SSH |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as executing commands on the Proxmox host via SSH, leaving no room for confusion with other tools.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'proxmox_run_host_command' follows a clear verb_noun pattern, and with no other tools to compare, there are no inconsistencies in naming conventions.
A single tool is too few for a server named 'Proxmox SSH MCP Server', which implies broader functionality for managing Proxmox environments via SSH. This minimal toolset feels thin and under-scoped for the apparent domain, limiting agents to only command execution without other common operations.
The tool surface is severely incomplete for Proxmox management via SSH. It lacks basic operations such as listing VMs/containers, managing resources, or performing configuration tasks, which are essential for this domain. Agents will face significant gaps and likely fail to accomplish typical Proxmox-related workflows.