Proxmox Mcp
About
Minimal Proxmox VE MCP server for Claude — 38 tools, one Docker command, read-only by default
Details
- Author
- akmalovaa
- Downloads
- 438
- Categories
- Other
Jump to
- Single multi-arch Docker image (amd64 + arm64)
- Configuration via environment variables only, no files or database
- Read-only by default; destructive operations require an explicit risk level
- Tiny codebase: pure stdio MCP over the Proxmoxer library
- Raw JSON output, no formatting or emoji, optimized for LLM consumption
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Proxmox McpCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Run the server as a single Docker container: docker run ghcr.io/akmalovaa/proxmox-mcp:latest. Pass authentication as environment variables (PROXMOX_HOST, PROXMOX_USER, plus password or token). Add an entry to your Claude configuration (claude_desktop_config.json or ~/.claude/settings.json) to register the MCP server.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"proxmox mcp": {
"proxmox": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PROXMOX_HOST",
"-e",
"PROXMOX_USER",
"-e",
"PROXMOX_PASSWORD",
"ghcr.io/akmalovaa/proxmox-mcp:latest"
]
}
}
}
}McpServers
{
"proxmox": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PROXMOX_HOST",
"-e",
"PROXMOX_USER",
"-e",
"PROXMOX_PASSWORD",
"ghcr.io/akmalovaa/proxmox-mcp:latest"
]
}
}Simple Proxmox MCP
MCP server for managing Proxmox VE
38 tools — nodes, QEMU VMs, LXC containers, storage, cluster, snapshots.
Why this one?
- One image, multi-arch —
docker run ghcr.io/akmalovaa/proxmox-mcp:latest and you're done- Just env vars — no config files, no database, no state
- Read-only by default — destructive ops are gated behind an explicit
PROXMOX_RISK_LEVEL- Tiny codebase — pure stdio MCP over Proxmoxer, no HTTP server, no auth layer, no extras
- Raw JSON out — no formatting, no emoji; LLM gets clean data
Quick start
Image:
ghcr.io/akmalovaa/proxmox-mcp:latest (multi-arch: amd64 + arm64).1. Export credentials in your shell profile (
~/.zprofile, ~/.zshrc or ~/.bashrc):``
bash
base environment:
export PROXMOX_HOST=192.168.1.100
export PROXMOX_USER=root@pam
export PROXMOX_PASSWORD=your-password
or use token auth (recommended):
export PROXMOX_TOKEN_NAME=mcp
export PROXMOX_TOKEN_VALUE=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
optional:
export PROXMOX_RISK_LEVEL=read
`
Reload: (or restart the shell).
2. Add to ~/.claude/settings.json (Claude Code) or claude_desktop_config.json (Claude Desktop):
`json
{
"mcpServers": {
"proxmox": {
"command": "docker",
"args": ["run", "-i", "--rm",
"-e", "PROXMOX_HOST",
"-e", "PROXMOX_USER",
"-e", "PROXMOX_PASSWORD",
"ghcr.io/akmalovaa/proxmox-mcp:latest"]
}
}
}
`
or token auth:
json
{
"mcpServers": {
"proxmox": {
"command": "docker",
"args": ["run", "-i", "--rm",
"-e", "PROXMOX_HOST",
"-e", "PROXMOX_USER",
"-e", "PROXMOX_TOKEN_NAME",
"-e", "PROXMOX_TOKEN_VALUE",
"ghcr.io/akmalovaa/proxmox-mcp:latest"]
}
}
}
``Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
