Skip to main content
Glama
bakhshb

@bakhshb/proxmox-mcp-openapi

by bakhshb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @bakhshb/proxmox-mcp-openapi

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

      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.
      18 npm
      1
      MIT

    • ProxmoxMCP-Plus

      davidpius95
      A
      license
      Not graded
      quality
      C
      maintenance
      Enhanced MCP server for managing Proxmox virtualization platforms with complete VM lifecycle management, LXC container support, and OpenAPI integration. Enables natural language VM creation, power management, and comprehensive cluster monitoring through secure API access.
      1
      MIT

    • proxmox-mcp

      ManciDRaffy
      A
      license
      A
      quality
      C
      maintenance
      Enables LLM agents to monitor and manage a Proxmox VE cluster, including cluster status, VM/container lifecycle, and node actions via MCP tools.
      8
      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/5.0

    Scored across 4 tools

    Disambiguation4/5

    The schema-discovery and generic execution tools are clearly separated, and the two command tools are distinguished by target (LXC container vs QEMU VM). There is mild overlap because proxmox-api could invoke the same guest-agent endpoints that proxmox-execute-vm-command wraps, but the descriptions make the intended use clear.

    Naming Consistency3/5

    All tools share the proxmox- prefix and use lowercase hyphenated names, but the API tools are noun-style (proxmox-api, proxmox-api-schema) while the command tools are verb-noun-style (proxmox-execute-...-command). This is readable and grouped, yet the verb/noun convention is not consistent across the set.

    Tool Count5/5

    Four tools is within the ideal range. The schema-discovery plus generic-execution pair makes the full Proxmox API available without requiring dozens of endpoint-specific tools, and the two command-execution tools add distinct practical guest operations.

    Completeness5/5

    Because proxmox-api can execute any operation from the OpenAPI spec, the tool set covers the entire Proxmox management API surface. The schema tool provides the necessary discovery loop, and the container/VM command tools cover common guest execution workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources