Skip to main content
Glama

Related Servers

Alternatives to unraid-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      A Model Context Protocol server that enables AI clients to inspect and manage an Unraid server via its GraphQL API, with read-only defaults and optional enabled mutations.
      88
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A code-mode MCP server for the Unraid 7.2+ GraphQL API that exposes search and execute tools, allowing LLM agents to introspect and call any GraphQL field via sandboxed JavaScript.
      2
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables monitoring and management of an Unraid server in plain English from any MCP client, covering array, parity, disks, Docker, VMs, ZFS, shares, logs, UPS, notifications, and more, with destructive actions gated behind explicit confirmation and an optional read-only mode.
      67
      795 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A Python-based server that enables AI assistants to interact with an Unraid server through the official Unraid GraphQL API, providing read-only access to system information, Docker containers, VMs, storage, and more.
      153
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to query homelab infrastructure such as Proxmox VE, NetBox, systemd services, Grafana, InfluxDB, AdGuard Home, ping logs, and configured HTTP JSON endpoints through read-only tools.
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables callers to route Unraid server operations through a single validated tool covering system, array, disk, Docker, VMs, notifications, keys, plugins, rclone, settings, connect, and customization actions with confirmation gating for destructive operations.
      58 npm
      MIT

    TDQS

    B3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion between tools. The tool is a single entry point, so all operations funnel through it, but that is an intra-tool concern rather than inter-tool ambiguity.

    Naming Consistency4/5

    The lone tool is named 'unraid', which is trivially consistent since there is no other name to conflict with. However, it does not follow a descriptive verb_noun convention, making it slightly less predictable than ideal.

    Tool Count2/5

    One tool for an entire Unraid management server is far too few. The domain typically involves discrete operations for array, disk, Docker, VM, and share management, and a single catch-all tool is a poor fit for that scope.

    Completeness4/5

    The tool claims to be a single entry point for all Unraid operations with capability discovery, suggesting broad coverage. The opaque surface and lack of explicit operations is a minor gap, but the design intends complete access.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues