---
title: "Proxmox MCP Server — Claude Code Integration"
aliases: [proxmox-mcp, canvrno-proxmox-mcp, mcp-proxmox]
tags: [proxmox, mcp, claude-code, homelab, vm-management]
sources:
  - "daily/2026-04-18.md"
created: 2026-04-18
updated: 2026-04-18
---

# Proxmox MCP Server — Claude Code Integration

There is no official Proxmox MCP server, but several community implementations exist. The most widely adopted is `canvrno/ProxmoxMCP` — a Python-based server that allows natural-language VM management directly from Claude Code. Installing it to the global Claude Code config makes it available in every project session.

## Key Points

- **No official Proxmox MCP** — all available servers are community-built
- **`canvrno/ProxmoxMCP`** is the recommended choice: Python, 175+ GitHub stars, active maintenance, good documentation (as of 2026-04)
- **`mcp-server-proxmox`** (EricWvi) is a TypeScript alternative — less popular
- **Proxmox NLP Server** (Ik0ri4n) works via SSH rather than the Proxmox API directly
- Install to global Claude Code config (`~/.claude/settings.json`) so it's available from any project directory — same pattern as GitHub and Bitbucket MCP servers

## Details

### Available Proxmox MCP Servers

| Server | Language | Approach | Stars (2026-04) |
|--------|----------|----------|-----------------|
| `canvrno/ProxmoxMCP` | Python | Proxmox REST API | 175+ |
| `EricWvi/mcp-server-proxmox` | TypeScript | Proxmox REST API | Lower |
| `Ik0ri4n/proxmox-nlp-server` | — | SSH + pve commands | Niche |

`canvrno/ProxmoxMCP` is the practical choice: Python aligns with the rest of the homelab tooling, and the REST API approach is more robust than SSH command strings.

### Global Config Installation

Add to `~/.claude/settings.json` alongside other MCP servers:

```json
{
  "mcpServers": {
    "proxmox": {
      "command": "uvx",
      "args": ["proxmox-mcp"],
      "env": {
        "PROXMOX_HOST": "192.168.x.x",
        "PROXMOX_USER": "root@pam",
        "PROXMOX_PASSWORD": "your-password",
        "PROXMOX_NODE": "pve"
      }
    }
  }
}
```

After editing, restart Claude Code for the server to connect. The MCP tools appear under the `proxmox__*` namespace.

### What It Enables

With the Proxmox MCP installed, Claude Code can:
- Create, start, stop, and delete VMs by natural language
- Query VM status and resource usage
- Manage containers (LXC)
- Execute tasks that would otherwise require SSH into the Proxmox host or the web UI

This complements but does not replace the Proxmox web UI — complex storage and network configuration is still easier in the UI.

### Kali Linux Context (2026-04-18)

The Proxmox MCP was installed in the context of setting up a Kali Linux VM for authorized penetration testing of the user's own infrastructure. The Kali VM was created manually via SSH + `qm` commands before the MCP was added; future VMs can be created directly from Claude Code.

## Related Concepts

- [[wiki/concepts/proxmox-vm-management-methods]] — all approaches for Proxmox VM management (API, Terraform, Ansible, SSH+qm)
- [[wiki/concepts/bitbucket-mcp-atlassian]] — same global config installation pattern for Bitbucket and GitHub MCP servers
- [[wiki/homelab/_index]] — Proxmox install, IOMMU, hypervisor setup articles

## Sources

- [[daily/2026-04-18.md]] — User asked about Proxmox MCP; `canvrno/ProxmoxMCP` selected over TypeScript and SSH alternatives; added to global Claude Code config; Kali VM context for authorized server pentesting
