Proxmox VE MCP Server

MCP PVE

MCP server for Proxmox VE. Manage virtual machines, containers, storage, networking, and clusters through natural language in Cursor, Claude Code, and Claude Desktop.

Features

• 122 tools across 12 categories covering the Proxmox VE REST API
• Three access tiers (read-only, read-execute, full) for granular control
• Category filtering via PVE_CATEGORIES to expose only the tools you need
• Zero HTTP dependencies -- uses native fetch (Node 22+)
• Self-signed cert support via PVE_VERIFY_SSL=false
• Docker images for linux/amd64 and linux/arm64 on GHCR
• Remote MCP via HTTP transport (MCP_TRANSPORT=http) using the Streamable HTTP protocol
• TypeScript/ESM with full type safety

API Compatibility

Tested with Proxmox VE 9.2.4.

Quick Start

Run the server directly with npx:

PVE_BASE_URL="https://pve.example.com:8006" \

PVE_TOKEN_ID="root@pam!mcp" \ PVE_TOKEN_SECRET="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" \ npx -y @samik081/mcp-pve

The server validates your PVE connection on startup and fails immediately with a clear error if credentials are missing or invalid.

Docker

Run with Docker (stdio transport, same as npx):

docker run --rm -i \

-e PVE_BASE_URL=https://pve.example.com:8006 \ -e PVE_TOKEN_ID=root@pam!mcp \ -e PVE_TOKEN_SECRET=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx \ -e PVE_VERIFY_SSL=false \ ghcr.io/samik081/mcp-pve

To run as a remote MCP server with HTTP transport:

docker run -d -p 3000:3000 \

-e MCP_TRANSPORT=http \ -e PVE_BASE_URL=https://pve.example.com:8006 \ -e PVE_TOKEN_ID=root@pam!mcp \ -e PVE_TOKEN_SECRET=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx \ -e PVE_VERIFY_SSL=false \ ghcr.io/samik081/mcp-pve

The MCP endpoint is available at http://localhost:3000 and a health check at http://localhost:3000/health.

Configuration

Claude Code CLI (recommended):

# Using npx

claude mcp add --transport stdio pve \ --env PVE_BASE_URL=https://pve.example.com:8006 \ --env PVE_TOKEN_ID=root@pam!mcp \ --env PVE_TOKEN_SECRET=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx \ --env PVE_VERIFY_SSL=false \ -- npx -y @samik081/mcp-pve

Using Docker

claude mcp add --transport stdio pve \ --env PVE_BASE_URL=https://pve.example.com:8006 \ --env PVE_TOKEN_ID=root@pam!mcp \ --env PVE_TOKEN_SECRET=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx \ --env PVE_VERIFY_SSL=false \ -- docker run --rm -i ghcr.io/samik081/mcp-pve

Using remote HTTP (connect to a running Docker container or HTTP server)

claude mcp add --transport http pve http://localhost:3000

JSON config (works with Claude Code .mcp.json, Claude Desktop claude_desktop_config.json, Cursor .cursor/mcp.json):

{

"mcpServers": { "pve": { "command": "npx", "args": ["-y", "@samik081/mcp-pve"], "env": { "PVE_BASE_URL": "https://pve.example.com:8006", "PVE_TOKEN_ID": "root@pam!mcp", "PVE_TOKEN_SECRET": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "PVE_VERIFY_SSL": "false" } } } }

Docker (stdio):

{

"mcpServers": { "pve": { "command": "docker", "args": ["run", "--rm", "-i", "-e", "PVE_BASE_URL=https://pve.example.com:8006", "-e", "PVE_TOKEN_ID=root@pam!mcp", "-e", "PVE_TOKEN_SECRET=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "-e", "PVE_VERIFY_SSL=false", "ghcr.io/samik081/mcp-pve" ] } } }

Remote MCP (connect to a running Docker container or HTTP server):

{

"mcpServers": { "pve": { "type": "streamable-http", "url": "http://localhost:3000" } } }

Access Tiers

Control which tools are available using the PVE_ACCESS_TIER environment variable:

Tier details:

• full: All 122 tools. Includes creating/deleting VMs, containers, storage, users, firewall rules, and more.
• read-execute: 77 tools. All read tools plus power actions (start, stop, migrate), bulk guest actions, OCI image pull, backup execution, and task management.
• read-only: 55 tools. List, get, status, and log tools only. No state changes.

Tools that are not available in your tier are not registered with the MCP server. They will not appear in your AI tool's tool list, keeping the context clean.

Environment Variables

Create API tokens in the PVE UI under Datacenter > Permissions > API Tokens. Make sure to uncheck "Privilege Separation" if you want the token to inherit the user's full permissions.

Available Categories

nodes, qemu, lxc, storage, cluster, access, pools, network, firewall, backup, tasks, ha

Tools

mcp-pve provides 122 tools organized by category. Each tool's Access column shows the minimum tier required: read-only (available in all tiers), read-execute (requires read-execute or full), or full (requires full tier only). The Hints column shows tool behavior: read-only (no state changes), destructive (modifies existing state), idempotent (same result if called twice).

Nodes (9 tools)

QEMU Virtual Machines (20 tools)

LXC Containers (18 tools)

| pve_delete_lxc_snapshot | Dele