Skip to main content
Glama
Proxmox SSH MCP Server

Proxmox SSH MCP Server

by Zaptimist

Proxmox SSH MCP Server

A Model Context Protocol (MCP) server that enables AI assistants to execute commands on a Proxmox host via SSH.

Features

  • SSH key-based authentication (no passwords in code)

  • Built-in security: dangerous commands are blocked

  • Single tool: proxmox_run_host_command

Related MCP server: SSH MCP Server

Prerequisites

  • Node.js 18+

  • SSH key pair (~/.ssh/id_ed25519)

  • Public key added to Proxmox server's ~/.ssh/authorized_keys

Installation

git clone https://github.com/Zaptimist/mcp-proxmox.git
cd mcp-proxmox
npm install

Configuration

Set your Proxmox host via environment variables or edit index.js:

Option 1: Environment variables (recommended)

export PROXMOX_HOST=192.168.1.100
export PROXMOX_USER=root
export PROXMOX_PORT=22
export PROXMOX_KEY_PATH=~/.ssh/id_ed25519

Option 2: Edit index.js directly

const sshConfig = {
  host: process.env.PROXMOX_HOST || '192.168.1.100',  // Your Proxmox IP
  username: process.env.PROXMOX_USER || 'root',
  port: parseInt(process.env.PROXMOX_PORT) || 22,
  privateKeyPath: process.env.PROXMOX_KEY_PATH || path.join(os.homedir(), '.ssh', 'id_ed25519')
};

SSH Key Setup

The MCP server will automatically detect if SSH keys are missing or not configured and provide setup instructions. But here's the manual process:

  1. Generate a key (if you don't have one):

    ssh-keygen -t ed25519
  2. Copy public key to Proxmox:

    Windows (PowerShell):

    type $env:USERPROFILE\.ssh\id_ed25519.pub | ssh root@YOUR_PROXMOX_IP "mkdir -p ~/.ssh && chmod 700 ~/.ssh && cat >> ~/.ssh/authorized_keys && chmod 600 ~/.ssh/authorized_keys"

    Linux/Mac:

    ssh-copy-id root@YOUR_PROXMOX_IP
  3. Test the connection:

    ssh root@YOUR_PROXMOX_IP "echo 'SSH key auth works!'"

If you haven't set up SSH keys yet, the MCP server will return helpful instructions when you try to use it.

MCP Client Configuration

Add to your MCP client config (e.g., ~/.kiro/settings/mcp.json):

{
  "mcpServers": {
    "proxmox": {
      "command": "node",
      "args": ["/path/to/mcp-proxmox/index.js"],
      "env": {
        "PROXMOX_HOST": "192.168.1.100"
      },
      "disabled": false,
      "autoApprove": ["proxmox_run_host_command"]
    }
  }
}

Usage

The server exposes one tool:

proxmox_run_host_command

Execute a command on the Proxmox host.

Input:

  • command (string, required): The command to execute

Example:

{
  "command": "qm list"
}

Response:

{
  "success": true,
  "command": "qm list",
  "host": "192.168.1.100",
  "exitCode": 0,
  "stdout": "VMID NAME STATUS MEM(MB) ...",
  "stderr": ""
}

Security

The following commands are blocked for safety:

  • VM/Container deletion (qm destroy, pct destroy)

  • File operations (rm, rmdir, dd)

  • System operations (shutdown, reboot, halt)

  • Package removal (apt remove, apt purge)

  • Service management (systemctl stop)

  • Storage deletion (zfs destroy, lvremove)

Destructive actions must be performed manually via the Proxmox web interface.

License

MIT

Available Tools

1 tool
proxmox_run_host_commandC

Execute a command on the Proxmox host via SSH

Inputs: command (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as executing commands on the Proxmox host via SSH, leaving no room for confusion with other tools.

    Naming Consistency5/5

    Since there is only one tool, naming consistency is inherently perfect. The tool name 'proxmox_run_host_command' follows a clear verb_noun pattern, and with no other tools to compare, there are no inconsistencies in naming conventions.

    Tool Count2/5

    A single tool is too few for a server named 'Proxmox SSH MCP Server', which implies broader functionality for managing Proxmox environments via SSH. This minimal toolset feels thin and under-scoped for the apparent domain, limiting agents to only command execution without other common operations.

    Completeness1/5

    The tool surface is severely incomplete for Proxmox management via SSH. It lacks basic operations such as listing VMs/containers, managing resources, or performing configuration tasks, which are essential for this domain. Agents will face significant gaps and likely fail to accomplish typical Proxmox-related workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to securely execute remote SSH commands, perform file transfers, and monitor system status through a standardized interface. It features robust security controls including command whitelisting, blacklisting, and credential isolation to prevent unauthorized operations.
      10
      23 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to securely execute commands, transfer files, and manage port forwarding on remote servers via SSH.
      164 npm
      38
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI to execute commands on remote hosts via SSH, supporting password and key authentication.
      -
    • F
      license
      A
      quality
      D
      maintenance
      Enables an AI assistant to fully navigate a single-node Proxmox VE host over SSH, with modes for read-only inspection, safe operations, and full control including provisioning and destruction.
      34
      -