Unraid MCP MCP Server
tv.tootie/unraid-mcp
MCP server for Unraid API — interact with your Unraid server's GraphQL API from Claude and Cursor.
What is the Unraid MCP MCP server?
The Unraid MCP server provides tools to query and mutate an Unraid server via its GraphQL API. It comes in two implementations: a Python flagship server (unraid-mcp) and a Rust alternative (runraid), both exposing read and write operations for array management, VMs, Docker containers, and notifications.
This MCP server bridges Claude and Cursor to your Unraid NAS, letting you query array status, manage virtual machines and containers, control array power states, and send notifications—all through a GraphQL interface. It supports both read-only and admin-level mutations, with flexible authentication (API key, bearer token, or OAuth) and optional TLS verification for self-signed certificates.
How to install Unraid MCP
Copy-paste configuration for popular MCP clients.
UNRAID_API_URLrequiredBase URL of your Unraid server, e.g. http://192.168.1.100.
UNRAID_API_KEYrequiredsecretUnraid API key for authentication.
Tools & capabilities
Tools this server exposes to the agent.
Array queries— Query Unraid array status, disk information, and system stateVM lifecycle— Start, stop, and manage virtual machinesDocker lifecycle— Start, stop, and manage Docker containersArray control— Start and stop the Unraid arrayNotifications— Write notifications to Unraid
Use cases
- Monitor your Unraid array status and disk health from Claude
- Start or stop VMs and Docker containers remotely via natural language
- Query array configuration and system information programmatically
- Send alerts and notifications to your Unraid dashboard
- Automate array power management and container lifecycle tasks
Unraid MCP MCP server FAQ
It's an MCP server that exposes Unraid's GraphQL API to Claude and Cursor, letting you query and control your Unraid NAS—arrays, VMs, containers, and notifications—via natural language or code.
Yes, the Unraid MCP server is open-source (MIT license) and available on PyPI and as a Docker image.
Install via the Claude Code marketplace: `/plugin marketplace add dinglebear-ai/unraid` then `/plugin install unraid-mcp@unraid-mcp` (Python) or `/plugin install runraid@unraid-mcp` (Rust). Or install via PyPI: `pip install unraid-mcp` and configure in your MCP settings.
You need your Unraid GraphQL endpoint URL and an API key (x-api-key). Optionally set `UNRAID_API_SKIP_TLS_VERIFY=true` for self-signed certificates. The server also supports bearer tokens and OAuth.
No—it exposes both queries and mutations. Read actions need `unraid:read` scope; write actions (VM/container lifecycle, array control, notifications) need `unraid:admin` scope.
The Python server (unraid-mcp) is the flagship with full documentation. The Rust server (runraid) is a single static binary alternative. Both expose the same GraphQL surface.
README (reference)
Source of truth, from the repository.
Unraid
<!-- mcp-name: tv.tootie/unraid-mcp -->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.
Repo name. This repo was renamed
unraid-mcp→unraidon 2026-07-27, and the former standalonerunraidandincus-unraidrepos were merged in here. The old GitHub name still redirects, so existing plugin install/update URLs keep working. The PyPI package, the container image, the Claude plugin, and the Unraid.plgare all still namedunraid-mcp— only the repo changed.
Components
| Path | What it is | Toolchain | Build / test |
|---|---|---|---|
unraid-py/ | unraid-mcp — Python MCP server (GraphQL), the flagship. Published to PyPI as unraid-mcp. | Python / uv / hatchling | cd unraid-py && uv run pytest && uv build --wheel |
unraid-rs/ | runraid — Rust MCP server + CLI (single static binary). Crate unraid-rmcp on crates.io, plus a legacy npm wrapper of the same name. | Rust / cargo | cd unraid-rs && cargo fmt --check && cargo clippy --all-targets --features test-support -- -D warnings && cargo test |
plugins/mcp/ | Unraid OS plugin that ships the Rust runraid MCP server onto an Unraid box. | shell .plg + Rust + Vue | bash plugins/mcp/scripts/build-txz.sh <ver> <runraid-binary> |
plugins/incus/ | Unraid OS plugin running Incus system containers ("dev containers") firewalled off the LAN. Includes a NestJS/GraphQL unraid-api backend. | shell .plg + NestJS/Vue | cd plugins/incus && ./scripts/verify-classic-package.sh && ./tests/classic-contract.sh |
plugins/codex/ | Unraid OS plugin embedding a Codex chathead app-server. | shell .plg + React | cd plugins/codex && ./tests/contract.sh |
agents/unraid-py/ | Claude Code / Codex plugin (name: unraid-mcp) for the Python server. | — | — |
agents/unraid-rs/ | Claude Code / Codex plugin (name: runraid) for the Rust server. | — | — |
Install the agent plugins (one marketplace command, two manifests)
/plugin marketplace add dinglebear-ai/unraid
/plugin install unraid-mcp@unraid-mcp # Python server
/plugin install runraid@unraid-mcp # Rust server
The @unraid-mcp suffix is the marketplace name declared in
.claude-plugin/marketplace.json, not the repo name — it stays unraid-mcp even
though the repo is now dinglebear-ai/unraid.
Both plugins are published from a single repo. Claude reads
.claude-plugin/marketplace.json; Codex reads .agents/plugins/marketplace.json.
meta-ci.yml asserts the two list the same plugin set, so they cannot drift.
marketplace add accepts the owner/repo shorthand (or a full git URL / local
path). After install, Claude Code prompts for the connection settings (the
plugin's userConfig).
Plugin credentials need no manual step
The agent plugins ship no Claude Code hooks, and none are needed: both
.mcp.json files map your plugin settings into the server environment directly
via ${user_config.*}. agents/unraid-rs wires 10 keys (endpoint, API key, TLS
skip, bearer token, four OAuth vars); agents/unraid-py wires UNRAID_API_URL
and UNRAID_API_KEY. Set them in plugin settings and the server picks them up on
next launch.
Optional, for non-plugin installs (systemd, Docker) that want ~/.unraid/.env
written to disk:
runraid setup plugin-hook # or: npx -y @dinglebear/unraid setup plugin-hook
unraid-py quickstart (Python MCP server)
The Python server is the flagship. Full documentation — installation, Claude
Code / Codex / Gemini setup, configuration, authentication, guardrails, and the
tool surface — lives in unraid-py/README.md and
unraid-py/docs/. It publishes to PyPI as unraid-mcp (import
package unraid_mcp) and launches with uvx unraid-mcp.
unraid-rs quickstart (Rust MCP server + CLI)
cd unraid-rs && cargo build --release # → target/release/runraid
runraid setup plugin-hook # writes ~/.unraid/.env
runraid array # CLI
runraid serve mcp # MCP over HTTP on :40010
| Env var | Purpose |
|---|---|
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_HOST / UNRAID_RMCP_PORT | MCP bind address (default 0.0.0.0:40010) |
UNRAID_RMCP_TOKEN | Static bearer token for /mcp |
UNRAID_RMCP_AUTH_MODE | bearer (default) or oauth |
Full list and the OAuth variables: unraid-rs/CLAUDE.md.
Not read-only. The Rust server exposes both queries and mutations. Read actions
need the unraid:read scope; mutating actions (VM and Docker lifecycle, array
start/stop, notification writes) need unraid:admin.
Releases
There are two release lanes. release-please manages only unraid-py and
unraid-rs — the Python server keeps unprefixed vX.Y.Z tags (the existing
audience's scheme) and Rust uses unraid-rs-vX.Y.Z. The Incus and Codex plugins
do not use release-please: they are versioned by
.github/scripts/plugin_calver.py with fixed-width YYYYMMDD.NNN versions and
incus-v* / codex-v* tags (Unraid compares plugin versions as raw strings, so the
fixed width is mandatory).
The native MCP plugin is built from the matching unraid-rs-vX.Y.Z tag, and Community Applications reads its rolling manifest from the unraid-plugin-latest release. Plugin .txz payloads ship as GitHub release assets, never tracked in git.
License
MIT — see LICENSE.
Related MCP servers

Cortex
Syslog receiver and MCP server for homelab log intelligence.
MCP server for self-hosted Gotify push notifications and message management.
View repository →
Syslog MCP
Syslog receiver and MCP server for homelab log intelligence.
Remote MCP server for Web3TV creators — manage your account over MCP.
View repository →Turn movie/TV recommendations into playable trailer pages: permanent, free, every title plays.
