Skip to main content
Glama
BenjaminDuthe

Proxmox MCP Server

by BenjaminDuthe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Proxmox MCP Server

No user-submitted related servers found.

    Related Servers

    • drumfire-proxmox-mcp

      Drumfire01
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to manage a Proxmox cluster through chat: inventory, power control, configuration changes, VM/container creation and cloning, snapshots, network/firewall/cluster visibility, guest command execution, and file writes via the QEMU Guest Agent.
      24 npm
      MIT

    • proxmox-mcp-server

      Leander-Andersen
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to manage a Proxmox VE host through natural language, including guest lifecycle, snapshots, host status monitoring, and shell execution via a companion bridge.
      24 npm
      1
      Apache 2.0

    • ProxmoxEmCP

      PureGrain
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage Proxmox VE infrastructure, including VMs, containers, storage, and cluster operations via natural language.
      MIT

    • proxmox-mcp

      Lyncee
      A
      license
      A
      quality
      D
      maintenance
      Provides tools to manage Proxmox VE clusters via Claude Code, enabling listing nodes, VMs, templates, power actions, and creation of LXC containers and VMs through the Proxmox REST API.
      10
      24 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 37 tools

    Disambiguation4/5

    Most tools target distinct resources or actions, but the multiple exec functions (pct_exec, vm_exec, vm_exec_sync, ssh_execute) could cause confusion despite clear descriptions. Overall clear boundaries are maintained.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_vms, create_user, get_vm_details). The few exceptions like pct_exec are standard Proxmox conventions and don't break consistency.

    Tool Count4/5

    With 37 tools, the server is extensive but well-justified for covering VMs, containers, nodes, storage, users, and system maintenance. It's on the higher end but still scoped to Proxmox administration.

    Completeness3/5

    Covers most CRUD operations for VMs and containers, users, and snapshots, but lacks a create_vm tool (only clone is available) and backup/restore functionality. Notable gaps for basic VM provisioning.

    Resources