Skip to main content
Glama
tiancode

pve-mcp

by tiancode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to pve-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • mcp-proxmox

      antonio-mello-ai
      A
      license
      A
      quality
      B
      maintenance
      MCP server for managing Proxmox VE clusters — provision VMs and containers, manage snapshots and backups, execute commands, browse storage, and monitor resources through natural language
      34
      16
      MIT

    • proxmox-mcp

      LeonRLewis
      F
      license
      Not graded
      quality
      D
      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.
      -

    • mcp-server-proxmox

      heybearc
      A
      license
      B
      quality
      C
      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.
      10
      3
      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.
      81 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

    A4.4/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear boundaries between backup, snapshot, VM, node, and storage operations. Even tools with similar names like pve_vm_config and pve_vm_set_config are clearly differentiated as get vs set.

    Naming Consistency5/5

    All tools follow the consistent pattern pve_<resource>_<action>, using snake_case. Actions include create, delete, list, set, get, etc., and resources are always in the plural or singular as appropriate. No mixing of styles.

    Tool Count5/5

    23 tools is appropriate for a Proxmox VE management server, covering essential operations on VMs, containers, snapshots, backups, nodes, storage, and tasks. Each tool serves a distinct purpose without redundancy.

    Completeness4/5

    The tool surface covers most lifecycle operations for VMs/containers, snapshots, and backups. A minor gap is the lack of a tool to create a new VM from scratch (e.g., from an ISO), but cloning and configuration tools cover common provisioning workflows.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources