Skip to main content
Glama
edymol

proxmox-mcp

by edymol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to proxmox-mcp

No user-submitted related servers found.

    Related Servers

    • 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

      m3m0ng
      F
      license
      B
      quality
      C
      maintenance
      A Python MCP server for Proxmox VE that lets AI agents read cluster status, power guests on/off, and provision new VMs/containers through natural language, while preventing any destructive actions.
      29
      -

    • Parallels RAS MCP Server

      RMITBLOG
      A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server that provides visibility into Parallels Remote Application Server infrastructure, policies, and sessions through the RAS REST API. It enables AI assistants to query site settings, published applications, and license status without performing any modifications.
      41
      2
      MIT

    • pve-mcp-server

      UriWise
      F
      license
      B
      quality
      C
      maintenance
      Read-only Proxmox VE MCP server providing 25 tools for VM, LXC, node, storage, and cluster inspection via stdio transport.
      25
      -

    • mcp-server-proxmox

      heybearc
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for Proxmox Virtual Environment that enables AI assistants to manage virtual machines, containers, nodes, and resources through natural language interactions.
      3
      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

    A4.3/5.0

    Scored across 12 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action: configuration vs status, snapshots vs backups, guests vs containers, node listing vs capacity. The consolidated health summary explicitly positions itself as a higher-level read, not a duplicate. There is no real overlap or risk of misselection.

    Naming Consistency4/5

    Eleven tools follow a consistent verb_noun snake_case pattern (list_*, get_*, check_*, inspect_*), with verbs semantically appropriate to each operation. The one exception is 'guest_health_summary', which is a noun phrase and breaks the pattern, but it is a single minor deviation.

    Tool Count5/5

    Twelve tools is squarely in the well-scoped range (3-15) for a Proxmox introspection server. Each tool covers a meaningful read-only aspect of the cluster, and there is no redundancy or bloat. The count aligns with the apparent domain and purpose.

    Completeness4/5

    The surface covers the core read-only workflows: guest listing/status/config, node capacity, storage, snapshots, backups, container inspection, and IP availability. Minor gaps exist (e.g., no node network info, no task history), but these are not critical for the evident purpose of a monitoring/introspection MCP server.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources