Skip to main content
Glama
lemanjo

Unraid MCP

by lemanjo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Unraid MCP

No user-submitted related servers found.

    Related Servers

    • mcp-graphql

      launchthatbrand
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables LLMs to interact with GraphQL APIs by providing schema introspection and query execution capabilities.
      1,360 npm
      3
      MIT

    • unraid-code-mode-mcp

      jmpijll
      A
      license
      A
      quality
      D
      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

    • unraid-mcp

      S1N4X
      A
      license
      B
      quality
      B
      maintenance
      Enables querying and managing an Unraid server through its official GraphQL API, exposing system, array, Docker, VM, share, notification, metrics, logs, and health actions via a single MCP tool. Write operations are gated by two independent locks and confirmation, with read-only behavior by default.
      1
      MIT

    • Advanced Hasura GraphQL MCP

      husamabusafa
      F
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI agents to dynamically interact with Hasura GraphQL endpoints through natural language, supporting schema discovery, data querying/manipulation, and aggregations.
      9
      23
      -
    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 88 tools

    Disambiguation2/5

    There is significant overlap between the generic get/list tools (e.g., unraid_get_metrics, unraid_list_shares, unraid_get_array) and the v4371_query counterparts (e.g., unraid_v4371_query_metrics, unraid_v4371_query_shares, unraid_v4371_query_array). The twelve 'next_' subscription tools also share nearly identical descriptions, differing only by payload name, which makes it easy for an agent to select the wrong one.

    Naming Consistency3/5

    All tool names use the unraid_ prefix and snake_case, but the verb conventions are mixed: get/list/read for high-level tools, query for the v4371 read-only family, and next for subscriptions. This creates two parallel naming schemes that are internally consistent but not unified across the set.

    Tool Count1/5

    88 tools is far beyond a practical MCP surface and will cause context bloat and selection difficulty. While the Unraid API is broad, exposing nearly every query variant plus multiple overlapping legacy wrappers is excessive for an agent-facing tool set.

    Completeness2/5

    The tool set is almost entirely read-only: it queries system state, metrics, logs, disks, containers, VMs, UPS, notifications, and configuration, but provides no create, update, delete, start, stop, or other mutating operations. There are also dead ends like exposing API-key creation form schemas without any tool to actually create an API key.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources