Skip to main content
Glama
Bldg-7

Proxmox MCP Server

by Bldg-7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Proxmox MCP Server

No user-submitted related servers found.

    Related Servers

    • proxmox-mcp

      nrohozen
      A
      license
      B
      quality
      C
      maintenance
      An MCP server that exposes Proxmox VE node/cluster as tools for MCP clients, enabling management of VMs and containers including power control, resource reconfiguration, snapshots, and backups.
      20
      MIT

    • Proxmox MCP Server

      raymatos
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for interacting with the Proxmox Virtual Environment API, enabling management of VMs, containers, storage, and cluster resources through natural language.
      MIT

    • nandi-proxmox-mcp

      NANDI-Services
      A
      license
      Not graded
      quality
      A
      maintenance
      An open-source MCP server for managing Proxmox environments, including nodes, virtual machines, and containers. It enables users to perform inventory checks, status monitoring, and control operations directly through MCP-compatible tools.
      115 npm
      MIT

    • proxmox-mcp

      plgonzalezrx8
      A
      license
      B
      quality
      D
      maintenance
      An MCP server for Proxmox VE that enables read-only cluster inspection, VM/container lifecycle operations, snapshots, migration, and provisioning with safe confirmation gates.
      28
      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

    C2.8/5.0

    Scored across 92 tools

    Disambiguation2/5

    Multiple tool boundaries are unclear: proxmox_guest_resize (CPU/memory) vs proxmox_guest_disk_resize (storage) are easily confused, and node queries are split across proxmox_node, proxmox_node_info, and proxmox_node_config with overlapping network/DNS actions. Disk operations are also scattered across proxmox_vm_disk and proxmox_guest_disk_*, creating ambiguous choices.

    Naming Consistency3/5

    Most tools follow a proxmox_<resource>_<action> snake_case pattern, but the set mixes action-in-tool-name (proxmox_guest_start) with action-parameter designs (proxmox_node, proxmox_cluster). There are also outliers like proxmox_create_vm/proxmox_create_lxc (versus the generic proxmox_guest_* Family) and proxmox_get_next_vmid which breaks the resource-first convention.

    Tool Count1/5

    With 92 tools, this server is far beyond an effective scope and will overwhelm agent tool selection. Even for a full hypervisor-management API, grouping related operations would make the set far more usable.

    Completeness4/5

    The tool surface is impressively broad and covers most core Proxmox domains: guest lifecycle (creation, start/stop, clone, migrate, template), snapshots, backups, storage, Ceph, SDN, users/ACLs, firewall, HA, and node administration. Minor gaps exist (e.g., no explicit guest rename, backup restore lacks granular options), but common workflows are essentially fully covered.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources