Skip to main content
Glama
rafaelgaspar

longhorn-mcp

by rafaelgaspar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to longhorn-mcp

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

    • rancher-mcp

      Jasonrve
      A
      license
      Not graded
      quality
      D
      maintenance
      A standalone MCP server that exposes Rancher-side tools, forwards Authorization headers or uses configured credentials, and supports HTTP and stdio transports.
      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
      16 npm
      2
      AGPL 3.0
    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/5.0

    Scored across 104 tools

    Disambiguation2/5

    Multiple tool groups are explicit duplicates or near-duplicates: volume_snapshot_create is described as 'equivalent to' volume_snapshot_cr_create, and there are three snapshot-list paths (snapshot_list, volume_snapshot_list, volume_snapshot_cr_list) plus duplicate backup getters (backup_get vs backupvolume_backup_get). An agent must read fine-print warnings about write-access requirements to avoid selecting the wrong accessor.

    Naming Consistency4/5

    The dominant resource_action pattern (volume_list, node_get, setting_update, backuptarget_create) is consistent and predictable. Deviations are mostly the longhorn_* meta tools (longhorn_list_tags, longhorn_raw_request) which place the verb in the middle rather than the end, plus minor oddities like volume_recurring_job_add using 'add' instead of 'create'.

    Tool Count1/5

    104 tools is extreme by any standard, placing this far beyond the 50+ threshold. While Longhorn is a genuinely broad system, much of the bloat comes from redundant surface variants (volume-scoped vs global vs CRD-backed accessors for the same snapshot/backup data) rather than distinct capabilities, and the presence of a raw_request escape hatch further suggests the set is uncurated.

    Completeness4/5

    Coverage of the Longhorn domain is remarkably deep: full lifecycle for volumes, snapshots, backups, backing images, engine images, recurring jobs, system backup/restore, nodes, and settings. Notable gaps exist though — there is no restore-backup-to-volume tool and support bundles only have list/get (no create) — but the longhorn_raw_request escape hatch mitigates these dead ends.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources