Proxmox VE MCP Server
Wire Claude Code or Cursor to your Proxmox cluster so agents can inspect nodes, VMs, and storage without opening the web UI.
Overview
Proxmox VE MCP Server is a MCP server for the Operate phase that lets AI assistants manage Proxmox VE clusters through authenticated API tokens.
What is this MCP server?
- Connects via stdio MCP with npm package @samik081/mcp-pve v0.6.0 or OCI image ghcr.io/samik081/mcp-pve:0.6.0
- Requires PVE_BASE_URL plus API token ID and secret (PVE_TOKEN_ID, PVE_TOKEN_SECRET)
- Lets AI assistants manage Proxmox VE nodes and guests through the official API
- Targets self-hosted and indie builders running VMs and LXC on their own hardware
- Runtime hint Node for npm; Docker registry path for containerized stdio transport
- Server version 0.6.0
- 2 published packages: npm @samik081/mcp-pve and OCI ghcr.io/samik081/mcp-pve:0.6.0
- 3 required environment variables: PVE_BASE_URL, PVE_TOKEN_ID, PVE_TOKEN_SECRET
Community signal: 8 GitHub stars.
What problem does it solve?
Switching between your editor and the Proxmox web UI breaks flow when you only need quick guest or node operations during infra work.
Who is it for?
Solo builders and small teams who already run Proxmox VE and want MCP-driven VM and LXC operations from Claude Code or Cursor.
Skip if: Builders on managed cloud-only stacks with no Proxmox cluster, or anyone unwilling to create and rotate API tokens on the hypervisor.
What do I get? / Deliverables
After you register the server with your agent, Proxmox changes and status checks can be requested in natural language from your coding environment.
- MCP tools callable by your agent against your Proxmox cluster API
- Stdio MCP registration snippet for your agent client
- Repeatable token-based access without sharing root SSH to the host
Recommended MCP Servers
Journey fit
Proxmox administration is ongoing production homelab and VPS work after you have already shipped workloads onto the hypervisor. Infra is the canonical shelf for hypervisor API bridges that start, stop, migrate, and monitor guests on real metal.
How it compares
Proxmox API MCP bridge, not a Terraform provisioner or a generic SSH skill.
Common Questions / FAQ
Who is Proxmox VE MCP Server for?
It is for developers and homelab operators who manage Proxmox VE and want their AI coding agent to call the cluster API safely via token auth.
When should I use Proxmox VE MCP Server?
Use it during operate and infra tasks when you need guest lifecycle, node visibility, or troubleshooting helpers without leaving the agent session.
How do I add Proxmox VE MCP Server to my agent?
Install @samik081/mcp-pve from npm or run the ghcr.io OCI image, set PVE_BASE_URL, PVE_TOKEN_ID, and PVE_TOKEN_SECRET, then add the stdio MCP entry in Claude Code, Cursor, or your MCP client config.