Skip to main content
Glama
antonio-mello-ai

mcp-proxmox

by antonio-mello-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-proxmox

No user-submitted related servers found.

    Related Servers

    • pve-mcp

      tiancode
      A
      license
      A
      quality
      C
      maintenance
      MCP server for managing Proxmox VE resources, VM/CT lifecycle, snapshots, backups, and clones via natural language.
      23
      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

    • proxmox-mcp

      LeonRLewis
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Proxmox VE that enables AI assistants to inspect and manage LXC containers, VMs, snapshots, and resource pools via the Proxmox API.
      -

    • proxmox-mcp

      Theorvane
      A
      license
      Not graded
      quality
      A
      maintenance
      A safety-gated, local stdio MCP server for the Proxmox VE API, enabling the management of VMs, containers, storage, and tasks through natural language via MCP hosts.
      28 npm
      1
      MIT

    • Proxmox MCP Server

      Reyes-Rodriguez-Public
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for managing Proxmox VE virtualization infrastructure, providing tools for VMs, containers, snapshots, storage, cluster nodes, and tasks. Compatible with Claude Desktop, Cline, and other MCP clients via natural language.
      65 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

    A3.6/5.0

    Scored across 34 tools

    Disambiguation4/5

    Most tools are clearly separated by resource type and action (snapshot vs backup vs guest lifecycle). Minor overlap exists between list_storage_content (backup/template filters) and list_backups/list_templates, but descriptions clarify the intended use.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (list_snapshots, create_backup, delete_firewall_rule, get_guest_status). Minor abbreviations like create_vm vs create_container do not break the convention.

    Tool Count2/5

    34 tools is on the heavy side for an MCP server, exceeding the 25+ threshold. While each tool maps to a distinct Proxmox API operation, the surface area is broad and some actions (e.g., guest power operations) could be consolidated.

    Completeness4/5

    Core workflows are covered: guest lifecycle, snapshots, backups, firewall, templates, and cloud-init. Gaps include general VM/CT configuration updates beyond resize, storage provisioning, and node maintenance, but these are secondary to the main management domain.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources