Skip to main content
Glama
UriWise

pve-mcp-server

by UriWise
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to pve-mcp-server

No user-submitted related servers found.

    Related Servers

    • Proxmox VE MCP

      nite-crawler
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP-compatible clients like Claude Desktop, Claude Code, Codex, and local-model hosts to inspect Proxmox VE clusters, nodes, VMs, containers, storage, snapshots, and tasks, with opt-in write operations for starting, stopping, cloning, backing up, and migrating guests. Read-only by default, it supports both stdio and Streamable HTTP transports.
      14
      MIT

    • Proxmox MCP Server

      NightSquawk
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Proxmox VE and Proxmox Datacenter Manager, covering every API endpoint via six consolidated tools for list, describe, and call operations with a read-only safety gate.
      6
      39 npm
      2
      AGPL 3.0

    • proxmox-mcp

      akmalovaa
      A
      license
      A
      quality
      A
      maintenance
      Minimal MCP server for Proxmox VE — 38 tools for nodes, VMs, LXC, storage, and snapshots. Read-only by default, single Docker image, multi-arch.
      38
      38 PyPI
      3
      MIT

    • proxmox-mcp

      edymol
      A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server for Proxmox VE that provides AI assistants with structured visibility into cluster nodes, guests, storage, and Docker workloads. It is designed to prevent any mutating operations by construction.
      12
      MIT

    • proxmox-monitor

      JohnGilligan2
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only Proxmox cluster oversight and configuration compliance checks through MCP, covering health, inventory, storage, backups, snapshots, and updates.
      -
    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

    B3.3/5.0

    Scored across 25 tools

    Disambiguation5/5

    Every tool targets a distinct resource and aspect, such as node status vs. node network vs. node PCI devices. Even similar-sounding tools like pve_get_node_disks and pve_get_node_pci are clearly separated by described hardware type.

    Naming Consistency4/5

    All tools share the pve_ prefix and use lowercase with underscores, but two tools use 'list_' (pve_list_vms, pve_list_lxc) while the rest use 'get_', creating a minor inconsistency in verb choice.

    Tool Count3/5

    With 25 tools, the server sits at the heavy end of the borderline range. The count is reasonable for a comprehensive read-only monitoring surface, but it feels ample and lacks any action-oriented tools to balance it.

    Completeness1/5

    The toolset is entirely read-only, offering no ability to create, start, stop, delete, or modify virtual machines or containers. This leaves major management workflows completely unsupported, making it severely incomplete for a Proxmox VE server.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources