Skip to main content
Glama
S1N4X

unraid-mcp

by S1N4X
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to unraid-mcp

No user-submitted related servers found.

    Related Servers

    • Unraid MCP

      lemanjo
      A
      license
      B
      quality
      A
      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

    • 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

    • graphql-mcp-server

      vogler75
      A
      license
      Not graded
      quality
      D
      maintenance
      Automatically generates MCP tools from any GraphQL API by introspecting its schema, supporting queries, mutations, and authentication.
      5
      GPL 3.0

    • truenas-mcp

      profanter-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server for TrueNAS SCALE 25.10+ that connects via JSON-RPC 2.0 WebSocket API, providing tools to inspect storage, shares, services, system info, jobs, and alerts.
      21 npm
      MIT

    • HomeLab MCP

      chip10
      F
      license
      C
      quality
      C
      maintenance
      MCP server that integrates Home Assistant, Frigate, Docker, and Proxmox via STDIO, enabling secure read and write operations with configurable confirmation.
      26
      -
    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 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

    ActivityMaintained
    ResponsivenessNo issues

    Resources