Skip to main content
Glama
bgauger

proxmox-safe-mcp

by bgauger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to proxmox-safe-mcp

No user-submitted related servers found.

    Related Servers

    • proxmox-mcp

      ssan9876
      F
      license
      A
      quality
      C
      maintenance
      Enables an AI assistant to fully navigate a single-node Proxmox VE host over SSH, with modes for read-only inspection, safe operations, and full control including provisioning and destruction.
      34
      -

    • Proximo

      john-broadway
      A
      license
      A
      quality
      A
      maintenance
      Enables management of Proxmox VE infrastructure via its REST API and execution of commands inside LXC containers via SSH, with built-in trust layers for planning, audit, undo, and diagnosis.
      7
      506 PyPI
      44
      Apache 2.0

    • ProxmoxMCP-Plus

      rodaddy
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables comprehensive management of Proxmox virtualization environments, including VM and container lifecycle, snapshots, backups, monitoring, and OpenAPI integration.
      14
      MIT

    • Proxxx

      fabriziosalmi
      A
      license
      Not graded
      quality
      A
      maintenance
      Terminal cockpit, CLI, and MCP server for Proxmox VE & PBS with 25 typed tools, pre-flight safety gates, Telegram HITL approval for destructive operations, and stdio/HTTP SSE transports.
      26
      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

    D1.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of the Proxmox environment: cluster status, node status, guest listing, guest power control, and guest snapshotting. There is no overlap in purposes, making selection unambiguous.

    Naming Consistency3/5

    The names mix noun-initial patterns (cluster_status, node_status, guest_power) with verb-initial patterns (list_guests, snapshot_guest). This inconsistency is noticeable but still readable and predictable overall.

    Tool Count5/5

    With only 5 tools, the server is tightly scoped and each tool serves a clear purpose. This is well-balanced for a specialized MCP server focused on monitoring and safe guest operations.

    Completeness3/5

    The set covers status, listing, power, and snapshot operations but lacks lifecycle management (create, update, delete guests). While potentially intentional for a 'safe' server, it leaves notable gaps for full Proxmox administration.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources