Proxmox MCP Server
Allows management of Proxmox VE environments, including VMs, containers, storage, firewalls, backups, snapshots, and more.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Proxmox MCP Serverlist all VMs on node proxmox1"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Proxmox MCP Server
A Model Context Protocol (MCP) server for managing Proxmox VE (Virtual Environment).
Features
Status Monitoring: Get status of nodes, storage, clusters, VMs, and containers
VM Management: Create, delete, start, stop, shutdown, restart VMs
Container Management: Create, delete, start, stop, shutdown, restart containers
Console Access: Access VM console via websocket or serial
ISO Management: Download, list, and manage ISO files
VM Guest Management: SSH, set IPs, manage users (requires Proxmox guest agent)
Maintenance: Get Proxmox version, check for updates, perform upgrades
Template Management: Create and manage VM/container templates
Backup and Restore: Create and restore backups for VMs and containers
HA Management: Enable/disable High Availability for VMs and containers
Migration: Migrate VMs and containers between nodes
Snapshots: Create and manage VM/container snapshots
Resource Pools: Manage resource pools and assign VMs to them
Related MCP server: MCP PVE
n8n Compatibility
This server supports both stdio and HTTP transports, making it compatible with n8n and other MCP clients.
HTTP Transport Mode (for n8n)
To use with n8n, set the HTTP_MODE environment variable to "true":
{
"mcpServers": {
"proxmox": {
"command": "node",
"args": ["/path/to/proxmox-mcp-server/build/index.js"],
"env": {
"PROXMOX_HOST": "YOUR_PROXMOX_HOSTNAME_OR_IP",
"PROXMOX_USER": "YOUR_USERNAME@pam",
"PROXMOX_PASSWORD": "YOUR_PASSWORD",
"HTTP_MODE": "true",
"HTTP_PORT": "3333"
}
}
}
}n8n will connect to http://localhost:3333/ for MCP communication.
Prerequisites
Node.js 18 or higher
Proxmox VE 7.x or higher
An account with appropriate permissions (e.g.,
PVEAuditororPVEAdminrole)
Installation
1. Clone or navigate to the server directory
cd proxmox-mcp-server2. Install dependencies
npm install3. Build the server
npm run build4. Configure environment variables
The server requires the following environment variables:
Variable | Description | Example |
| Proxmox hostname or IP address |
|
| Proxmox username with full path |
|
| Proxmox password |
|
| (Optional) Proxmox API port (default: 8006) |
|
| (Optional) Verify SSL certificate (default: true) |
|
5. Configure MCP settings
Add the server configuration to your MCP settings file:
For Roo Code (macOS/Linux): ~/.roo-code/settings/mcp_settings.json
For Roo Code (Windows): %APPDATA%\roo-code\settings\mcp_settings.json
For Claude Desktop (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json
For Claude Desktop (Windows): %APPDATA%\Claude\claude_desktop_config.json
Example configuration:
{
"mcpServers": {
"proxmox": {
"command": "node",
"args": ["/path/to/proxmox-mcp-server/build/index.js"],
"env": {
"PROXMOX_HOST": "proxmox.example.com",
"PROXMOX_USER": "admin@pam",
"PROXMOX_PASSWORD": "your_password"
},
"disabled": false,
"alwaysAllow": [],
"disabledTools": []
}
}
}6. Restart your MCP client
Restart Roo Code or Claude Desktop to load the new MCP server configuration.
Usage
Once configured, you can use the Proxmox MCP server through your MCP client's interface. Available tools include:
Status Tools
get_node_status- Get status of Proxmox nodesget_summary- Get summary of Proxmox node resourcesget_storage_status- Get status of Proxmox storageget_cluster_status- Get Proxmox cluster statusget_vm_status- Get status of Proxmox VMsget_container_status- Get status of Proxmox containersget_running_vms- Get all running VMs and containers on a node
VM Management
create_vm- Create a new VM with cloud-init, guest agent, and network interface configurationdelete_vm- Delete a VMstart_vm- Start a VMstop_vm- Stop a VMshutdown_vm- Shutdown a VM gracefullyrestart_vm- Restart a VM
Container Management
create_container- Create a new container with OS configurationdelete_container- Delete a containerstart_container- Start a containerstop_container- Stop a containershutdown_container- Shutdown a container gracefullyrestart_container- Restart a container
Console Access
vm_console- Access VM console (websocket or serial)
ISO Management
list_isos- List ISO files on a Proxmox nodedownload_iso- Download an ISO file to a Proxmox nodedelete_iso- Delete an ISO file from a Proxmox nodeget_iso_download_status- Get status of an ISO download task
Firewall Management
enable_vm_firewall- Enable firewall for a VMdisable_vm_firewall- Disable firewall for a VMenable_container_firewall- Enable firewall for a containerdisable_container_firewall- Disable firewall for a containercreate_vm_firewall_rule- Create a firewall rule for a VMcreate_container_firewall_rule- Create a firewall rule for a containerlist_vm_firewall_rules- List firewall rules for a VMlist_container_firewall_rules- List firewall rules for a containerdelete_vm_firewall_rule- Delete a firewall rule for a VMdelete_container_firewall_rule- Delete a firewall rule for a container
VM Guest Management (requires Proxmox Guest Agent)
ssh_to_vm- SSH into a VM using qm consoleset_vm_ip- Set IP address for a VMset_vm_hostname- Set hostname for a VMcreate_vm_user- Create a new user in a VMset_vm_user_password- Set password for an existing VM userrun_vm_command- Run a command in a VMget_vm_interfaces- Get network interfaces from a VM
Maintenance
get_proxmox_version- Get Proxmox VE versionget_updates- Get available updatesupgrade_proxmox- Upgrade Proxmox VEget_task_status- Get status of running tasks
Prerequisites for VM Guest Management
The create_vm tool enables the Proxmox Guest Agent when installGuestAgent is enabled (default: true). However, you still need to install the guest agent inside the VM:
Install the Proxmox Guest Agent inside your VMs/containers
For Linux VMs:
apt install qemu-guest-agentoryum install qemu-guest-agentEnsure the guest agent service is running:
systemctl enable --now qemu-guest-agent
Note: The VM is created in a stopped state. You need to start it manually after creation.
Network Interface Configuration
The create_vm tool supports multiple network interfaces with various configuration options:
Parameter | Description | Example |
| Network interface 0 |
|
| Network interface 1 |
|
| Network interface 2 |
|
| Network interface 3 |
|
Network interface format: type=MAC_ADDRESS,bridge=BRIDGE_NAME
Supported NIC types: virtio, e1000, rtl8139, vmxnet3, ne2k_pci, pcnet
Cloud-init Configuration
The create_vm tool supports cloud-init for automated VM configuration:
Parameter | Description | Example |
| Enable cloud-init (default: true) |
|
| DNS nameserver |
|
| Search domain |
|
| IP configuration |
|
| SSH public keys |
|
| Username for cloud-init |
|
| Password for cloud-init user |
|
ISO Management
To install an OS from an ISO file:
Download the ISO:
{
"method": "proxmox/download_iso",
"params": {
"node": "pve1",
"storage": "local",
"filename": "ubuntu-22.04.iso",
"url": "https://releases.ubuntu.com/22.04/ubuntu-22.04.4-live-server-amd64.iso"
}
}List ISOs to verify the download:
{
"method": "proxmox/list_isos",
"params": {
"node": "pve1",
"storage": "local"
}
}Create a VM with the ISO as the boot device:
{
"method": "proxmox/create_vm",
"params": {
"node": "pve1",
"vmid": 100,
"name": "ubuntu-server",
"memory": 2048,
"cores": 2,
"disk": "virtio0: local:20",
"ostype": "l26",
"scsihw": "virtio-scsi-pci",
"bootdisk": "virtio0",
"net0": "virtio,bridge=vmbr0"
}
}Attach the ISO to the VM (after creation):
{
"method": "proxmox/create_vm",
"params": {
"node": "pve1",
"vmid": 100,
"name": "ubuntu-server",
"memory": 2048,
"cores": 2,
"disk": "virtio0: local:20",
"ostype": "l26",
"scsihw": "virtio-scsi-pci",
"bootdisk": "virtio0",
"net0": "virtio,bridge=vmbr0",
"ide2": "local:iso/ubuntu-22.04.iso,media=cdrom"
}
}Firewall Management
Enable firewall for a VM:
{
"method": "proxmox/enable_vm_firewall",
"params": {
"node": "pve1",
"vmid": 100
}
}Create a firewall rule:
{
"method": "proxmox/create_vm_firewall_rule",
"params": {
"node": "pve1",
"vmid": 100,
"rule": "in,REJECT,22/tcp",
"pos": 1
}
}List firewall rules:
{
"method": "proxmox/list_vm_firewall_rules",
"params": {
"node": "pve1",
"vmid": 100
}
}Development
Build
npm run buildRun directly (for testing)
PROXMOX_HOST=your-host PROXMOX_USER=your-user PROXMOX_PASSWORD=your-password npm startLicense
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jskoetsier/proxmox-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server