# ProxmoxMCP-Plus MCP server

> Manage Proxmox VE virtual machines, LXC containers, snapshots, backups, storage and cluster state from an AI assistant.

- Listing: https://mcp.tc/i/proxmoxmcp-plus
- Connect: this is a local (stdio) server; install it on your machine (see Install). The listing link is a page, not an MCP endpoint.
- Type: local (stdio)
- Auth: API key
- Category: [Cloud & DevOps](https://mcp.tc/c/cloud-devops)
- Vendor: RekklesNA
- Docs: <https://github.com/RekklesNA/ProxmoxMCP-Plus>
- Repository: <https://github.com/RekklesNA/ProxmoxMCP-Plus>
- Package: pypi `proxmox-mcp-plus`

## About

ProxmoxMCP-Plus connects to a Proxmox VE cluster through its API and exposes VM and LXC lifecycle actions, snapshots, backups, ISO management, storage and cluster inspection, log reading, and persistent tracking of long-running tasks. It can also run guarded shell commands in guests and on nodes.

It runs locally over stdio with uvx proxmox-mcp-plus, or as a Streamable HTTP server in Docker that requires a bearer key. Access needs a Proxmox API token (host, user, token name and token value), set through environment variables or a JSON config file. Tool allowlists and denylists can limit what is exposed.

## What it can do

- List nodes, VMs, containers, storage and cluster status
- Create, clone, start, stop and delete VMs and LXC containers
- Create, roll back and delete snapshots
- Create, restore and delete backups
- Run commands in VMs, containers and nodes
- Track, poll, cancel and retry long-running jobs
- Read syslog, task, cluster and firewall logs

## Tools (68)

- `list_targets`: List configured Proxmox targets without exposing credentials
- `get_nodes`: List all nodes in the cluster
- `get_node_status`: Get detailed status of a node
- `get_node_time`: Read node clock and timezone for authentication skew diagnostics
- `get_node_diagnostics`: Read per-node CPU, memory, storage and recent disk/network metrics
- `get_vms`: List all virtual machines across the cluster
- `preflight_vm_migration`: Read-only QEMU migration safety assessment
- `migrate_vm`: Guarded offline QEMU VM migration with local disks
- `configure_vm_serial_console`: Enable a socket-backed serial console for a stopped VM
- `import_cloud_image`: Import existing disk image from import-enabled Proxmox storage
- `get_vm_config`: Get full configuration of a QEMU VM
- `set_vm_description`: Set the Notes description of a QEMU VM
- `update_vm_config`: Update VM sizing and cloud-init settings
- `get_vm_ip_addresses`: Get VM network interfaces and IPs via guest agent
- `get_next_vmid`: Get the next free VM/container ID
- `create_vm`: Create a new virtual machine
- `clone_vm`: Clone an existing virtual machine
- `execute_vm_command`: Run a shell command in a VM via QEMU Guest Agent
- `start_vm`: Start a virtual machine
- `stop_vm`: Force stop a virtual machine
- `shutdown_vm`: Gracefully shut down a virtual machine
- `reset_vm`: Reset (restart) a virtual machine
- `delete_vm`: Completely delete a virtual machine
- `get_storage`: List available storage pools
- `get_node_storage`: Read node-specific capacity, status and content capability of storage pools
- `get_cluster_status`: Get cluster status and health
- `get_cluster_join_info`: Read cluster join information and certificate fingerprint with credential redaction
- `list_jobs`: List persistent Proxmox task jobs
- `get_job`: Get a persistent job by ID
- `poll_job`: Poll a task job for current status
- `cancel_job`: Request cancellation of a task job
- `retry_job`: Retry an eligible failed or cancelled job
- `get_containers`: List all LXC containers
- `preflight_container_migration`: Read-only, fail-closed preflight checks for LXC migration
- `start_container`: Start LXC containers
- `stop_container`: Stop LXC containers
- `restart_container`: Restart LXC containers
- `update_container_resources`: Update CPU, memory or disk of an LXC container
- `create_container`: Create a new LXC container
- `delete_container`: Delete LXC containers
- `migrate_container`: Submit an explicitly confirmed LXC migration and track its task
- `execute_container_command`: Run a shell command in an LXC container via SSH
- `execute_node_command`: Run an authorized shell command on a node via SSH
- `update_container_ssh_keys`: Update root authorized\_keys in an LXC container
- `get_container_config`: Get full configuration of an LXC container
- `set_container_description`: Set the Notes description of an LXC container
- `get_container_ip`: Get current IP information for an LXC container
- `list_snapshots`: List snapshots for a VM or container
- `create_snapshot`: Create a new snapshot
- `delete_snapshot`: Delete a specific snapshot
- `rollback_snapshot`: Rollback to a specific snapshot
- `list_isos`: List available ISO images
- `list_templates`: List available LXC templates
- `download_iso`: Download an ISO image
- `download_template`: Download an LXC template archive to Proxmox storage
- `delete_iso`: Delete an ISO or template
- `list_backups`: List available backups
- `create_backup`: Create a backup of a VM or container
- `restore_backup`: Restore from a backup
- `delete_backup`: Delete a specific backup
- `get_node_syslog`: Read syslog entries from a Proxmox node
- `get_task_log`: Get the log output of a specific Proxmox task by its UPID
- `get_cluster_log`: Read recent cluster-wide log entries
- `get_node_firewall_log`: Read the host firewall log of a Proxmox node
- `get_guest_firewall_log`: Read the firewall log of a VM (qemu) or container (lxc)
- `update_container_network`: Update an existing LXC network interface, preserving unspecified NIC settings.
- `list_bridges`: List Linux/OVS bridges and permitted SDN VNets on a selected node.
- `reconcile_job`: Reconcile an uncertain retry with a verified task UPID or explicit confirmation that no task was submitted.

## Example prompts

- "List all VMs in my Proxmox cluster and their status"
- "Create a snapshot of VM 102 before I upgrade it"
- "Show the IP address of LXC container 205"
- "Back up container 110 and tell me when the job finishes"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport stdio proxmoxmcp-plus --env "PROXMOX_HOST=<YOUR_PROXMOX_HOST>" --env "PROXMOX_USER=<YOUR_PROXMOX_USER>" --env "PROXMOX_TOKEN_NAME=<YOUR_PROXMOX_TOKEN_NAME>" --env "PROXMOX_TOKEN_VALUE=<YOUR_PROXMOX_TOKEN_VALUE>" -- uvx proxmox-mcp-plus
```

2. Start Claude Code and type `/mcp`. **proxmoxmcp-plus** should show as connected.

Add `--scope user` to make it available in every project. Replace the placeholders with your own values.

### Claude Desktop

1. Open **Settings → Developer → Edit Config**. It opens `claude_desktop_config.json`. Add:

`claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "proxmoxmcp-plus": {
      "command": "uvx",
      "args": [
        "proxmox-mcp-plus"
      ],
      "env": {
        "PROXMOX_HOST": "<YOUR_PROXMOX_HOST>",
        "PROXMOX_USER": "<YOUR_PROXMOX_USER>",
        "PROXMOX_TOKEN_NAME": "<YOUR_PROXMOX_TOKEN_NAME>",
        "PROXMOX_TOKEN_VALUE": "<YOUR_PROXMOX_TOKEN_VALUE>"
      }
    }
  }
}
```

2. Save the file and restart Claude Desktop. Replace the placeholders with your own values.

Needs uv (Python) on your computer. The file lives in `~/Library/Application Support/Claude/` on macOS and `%APPDATA%\Claude\` on Windows.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=proxmoxmcp-plus&config=eyJjb21tYW5kIjoidXZ4IiwiYXJncyI6WyJwcm94bW94LW1jcC1wbHVzIl0sImVudiI6eyJQUk9YTU9YX0hPU1QiOiI8WU9VUl9QUk9YTU9YX0hPU1Q%2BIiwiUFJPWE1PWF9VU0VSIjoiPFlPVVJfUFJPWE1PWF9VU0VSPiIsIlBST1hNT1hfVE9LRU5fTkFNRSI6IjxZT1VSX1BST1hNT1hfVE9LRU5fTkFNRT4iLCJQUk9YTU9YX1RPS0VOX1ZBTFVFIjoiPFlPVVJfUFJPWE1PWF9UT0tFTl9WQUxVRT4ifX0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "proxmoxmcp-plus": {
      "command": "uvx",
      "args": [
        "proxmox-mcp-plus"
      ],
      "env": {
        "PROXMOX_HOST": "<YOUR_PROXMOX_HOST>",
        "PROXMOX_USER": "<YOUR_PROXMOX_USER>",
        "PROXMOX_TOKEN_NAME": "<YOUR_PROXMOX_TOKEN_NAME>",
        "PROXMOX_TOKEN_VALUE": "<YOUR_PROXMOX_TOKEN_VALUE>"
      }
    }
  }
}
```

Needs uv (Python) on your computer. Replace the placeholders with your own values.

### VS Code

Add it to `.vscode/mcp.json`. VS Code asks for the secret the first time and stores it securely:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "proxmoxmcp-plus": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "proxmox-mcp-plus"
      ],
      "env": {
        "PROXMOX_HOST": "<YOUR_PROXMOX_HOST>",
        "PROXMOX_USER": "<YOUR_PROXMOX_USER>",
        "PROXMOX_TOKEN_NAME": "${input:proxmox-token-name}",
        "PROXMOX_TOKEN_VALUE": "${input:proxmox-token-value}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "proxmox-token-name",
      "description": "PROXMOX_TOKEN_NAME",
      "password": true
    },
    {
      "type": "promptString",
      "id": "proxmox-token-value",
      "description": "PROXMOX_TOKEN_VALUE",
      "password": true
    }
  ]
}
```

Needs uv (Python) on your computer.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "proxmoxmcp-plus": {
      "command": "uvx",
      "args": [
        "proxmox-mcp-plus"
      ],
      "env": {
        "PROXMOX_HOST": "<YOUR_PROXMOX_HOST>",
        "PROXMOX_USER": "<YOUR_PROXMOX_USER>",
        "PROXMOX_TOKEN_NAME": "<YOUR_PROXMOX_TOKEN_NAME>",
        "PROXMOX_TOKEN_VALUE": "<YOUR_PROXMOX_TOKEN_VALUE>"
      }
    }
  }
}
```

2. Refresh the MCP server list in Cascade. Replace the placeholders with your own values.

Devin Desktop is the new name for Windsurf.

### Codex

```bash
codex mcp add proxmoxmcp-plus --env "PROXMOX_HOST=<YOUR_PROXMOX_HOST>" --env "PROXMOX_USER=<YOUR_PROXMOX_USER>" --env "PROXMOX_TOKEN_NAME=<YOUR_PROXMOX_TOKEN_NAME>" --env "PROXMOX_TOKEN_VALUE=<YOUR_PROXMOX_TOKEN_VALUE>" -- uvx proxmox-mcp-plus
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.proxmoxmcp-plus]
command = "uvx"
args = ["proxmox-mcp-plus"]
env = { PROXMOX_HOST = "<YOUR_PROXMOX_HOST>", PROXMOX_USER = "<YOUR_PROXMOX_USER>", PROXMOX_TOKEN_NAME = "<YOUR_PROXMOX_TOKEN_NAME>", PROXMOX_TOKEN_VALUE = "<YOUR_PROXMOX_TOKEN_VALUE>" }
```

Needs uv (Python) on your computer. Replace the placeholders with your own values.

### Gemini CLI

```bash
gemini mcp add -e "PROXMOX_HOST=<YOUR_PROXMOX_HOST>" -e "PROXMOX_USER=<YOUR_PROXMOX_USER>" -e "PROXMOX_TOKEN_NAME=<YOUR_PROXMOX_TOKEN_NAME>" -e "PROXMOX_TOKEN_VALUE=<YOUR_PROXMOX_TOKEN_VALUE>" proxmoxmcp-plus uvx proxmox-mcp-plus
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients that start local servers accept this shape:

```json
{
  "mcpServers": {
    "proxmoxmcp-plus": {
      "command": "uvx",
      "args": [
        "proxmox-mcp-plus"
      ],
      "env": {
        "PROXMOX_HOST": "<YOUR_PROXMOX_HOST>",
        "PROXMOX_USER": "<YOUR_PROXMOX_USER>",
        "PROXMOX_TOKEN_NAME": "<YOUR_PROXMOX_TOKEN_NAME>",
        "PROXMOX_TOKEN_VALUE": "<YOUR_PROXMOX_TOKEN_VALUE>"
      }
    }
  }
}
```

Zed puts servers under `context_servers` in its settings, with the same `command`, `args` and `env` fields.

Needs uv (Python) on your computer. Replace the placeholders with your own values.

## Recent changes

- 2026-11-16 02:32 UTC: New version 0.7.1 (was 0.7.0), read from PyPI. Source: automatic check.
- 2026-11-14 02:27 UTC: New version 0.7.0 (was 0.6.10), read from PyPI. Source: automatic check.
- 2026-11-10 23:25 UTC: New version 0.6.10 (was 0.6.9), read from PyPI. Source: automatic check.
- 2026-11-04 02:28 UTC: New version 0.6.9 (was 0.6.8), read from PyPI. Source: automatic check.
- 2026-10-29 17:30 UTC: New version 0.6.8 (was 0.6.7), read from PyPI. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/proxmoxmcp-plus#history (Atom feed: https://mcp.tc/i/proxmoxmcp-plus/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 0.7.1
- Last checked: 2026-10-12
- Listed: 2026-10-12
- Updated: 2026-10-19

---
Source: https://mcp.tc/i/proxmoxmcp-plus (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
