mcp -proxmox

Model Context Protocol (MCP) server for Proxmox Virtual Environment - manage VMs, containers, nodes, and resources through AI assistants

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

View docs

Command

claude mcp add --transport stdio heybearc-mcp-server-proxmox node /path/to/mcp-server-proxmox/dist/index.js \
  --env PROXMOX_HOST="your-proxmox-host.com" \
  --env PROXMOX_PORT="8006" \
  --env PROXMOX_REALM="pam" \
  --env PROXMOX_TOKEN="your-api-token" \
  --env PROXMOX_PASSWORD="your-password" \
  --env PROXMOX_USERNAME="root" \
  --env PROXMOX_TOKEN_NAME="your-token-name" \
  --env PROXMOX_VERIFY_SSL="true"

How to use

This MCP server provides a programmable interface to manage Proxmox VE resources through natural language and automated scripts. It exposes tools to list and monitor cluster nodes, VMs, and LXC containers, and to perform start/stop operations on VMs. Authentication can be done via password or API token, and multi-node deployments are supported. Clients can query status, retrieve lists by node, and issue lifecycle actions using MCP-compatible messages. The server communicates over stdio following the MCP protocol, making it compatible with the MCP client ecosystem and tools such as Claude Desktop and other MCP clients.

How to install

Prerequisites:

Node.js 18.0.0 or higher
npm (comes with Node.js)
Proxmox VE 7.0+ with API access
Proxmox credentials (username/password or API token)

From Source:

git clone https://github.com/heybearc/mcp-server-proxmox.git
cd mcp-server-proxmox
npm install
npm run build

From NPM (Coming Soon):

npm install -g mcp-server-proxmox

Run the server (example):

# Ensure environment variables are set (see Configuration section)
npx none
node dist/index.js

Configure environment and client connections as described in the MCP client docs and the included example configuration.

Additional notes

Tips:

Ensure PROXMOX_VERIFY_SSL reflects your SSL setup; set to false only in trusted environments.
Use API tokens for production workflows; restrict token permissions to VM management and read-only status where appropriate.
When running in multi-node environments, provide host/credentials that cover all targeted nodes; consider using a single token with cluster-wide scope.
If the MCP client cannot connect, verify that the server process has access to the Proxmox host network and that firewall rules allow the API port (default 8006).
For Claude Desktop or other clients, configure the mcpServers section with the correct path to the built index.js and export the same environment variables used by the server.

Related MCP Servers

zen

1.1k

Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage

MCP -Deepseek_R1

A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)

mcp-fhir

A Model Context Protocol implementation for FHIR

mcp

Inkdrop Model Context Protocol Server

mcp-appium-gestures

This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..

dubco -npm

The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.