Unraid MCP Server

MCP Server for Unraid API - provides tools to interact with an Unraid server's GraphQL API

Local serverstdioPython

What is the Unraid MCP server?

MCP Server for Unraid API - provides tools to interact with an Unraid server's GraphQL API. Exposed over MCP by the unraid mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

A monorepo of Unraid tooling: two MCP servers (Python and Rust) and three Unraid OS plugins, plus the Claude/Codex agent integrations that surface them.

Its toolset

Everything the assistant can do here goes through one of these:

  • Path — What it is
  • UNRAID_API_URL — Unraid GraphQL endpoint (required)
  • UNRAID_API_KEY — x-api-key for the Unraid API (required)
  • UNRAID_API_SKIP_TLS_VERIFY — Accept a self-signed Unraid cert (default false)
  • UNRAID_RMCP_TOKEN — Static bearer token for /mcp
  • UNRAID_RMCP_AUTH_MODE — bearer (default) or oauth

Configuration

You will need 4 environment variables: UNRAID_API_URL, UNRAID_API_KEY, UNRAID_RMCP_HOST, UNRAID_RMCP_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at unraid-mcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Unraid's toolset — Path, UNRAID_API_URL, UNRAID_API_KEY and 3 more — is a fair guide to whether it matches your workflow.

This entry was verified against Unraid's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the unraid mcp server does with a few real requests.

Available tools

ToolWhat it does
PathWhat it is
UNRAID_API_URLUnraid GraphQL endpoint (required)
UNRAID_API_KEYx-api-key for the Unraid API (required)
UNRAID_API_SKIP_TLS_VERIFYAccept a self-signed Unraid cert (default false)
UNRAID_RMCP_TOKENStatic bearer token for /mcp
UNRAID_RMCP_AUTH_MODEbearer (default) or oauth

How to install the Unraid MCP server

{
  "mcpServers": {
    "unraid": {
      "command": "uvx",
      "args": ["unraid-mcp"],
      "env": {
        "UNRAID_API_URL": "your-value",
        "UNRAID_API_KEY": "your-value",
        "UNRAID_RMCP_HOST": "your-value",
        "UNRAID_RMCP_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
UNRAID_API_URLEndpoint or connection string the server talks to.Yes
UNRAID_API_KEYCredential the server authenticates with.Yes
UNRAID_RMCP_HOSTEndpoint or connection string the server talks to.Optional
UNRAID_RMCP_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Unraid to Path.
  • Use Unraid to UNRAID API URL.
  • Use Unraid to UNRAID API KEY.

Frequently asked questions

It connects Unraid to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (Path, UNRAID_API_URL, UNRAID_API_KEY, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Unraid directly.