Unraid MCP server
MCP server for Unraid API — provides tools to interact with an Unraid server's GraphQL API.
131 stars430 downloads/wk
Reviews
Write oneNobody has reviewed Unraid MCP yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Unraid MCP tools (1)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
unraid
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- Code scan52 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 3 days ago15/15
- Maintainer identitynamespace and repository owner differ; GitHub account older than a year6/10
Install Unraid MCP in Claude Code, Cursor or VS Code
claude mcp add unraid-mcp -- uvx unraid-mcp
What the publisher says
From the Unraid MCP repository's README, as published. We do not edit it. Read it on GitHub
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 → unraid on 2026-07-27, and
the former standalone runraid and incus-unraid repos 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 .plg** are all still named unraid-mcp — only the repo changed.
Components
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 serverThe @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 ${userconfig.}. agents/unraid-rs wires 10 keys (endpoint, API key, TLS skip, bearer token, four OAuth vars); agents/unraid-py wires UNRAIDAPIURL and UNRAIDAPIKEY. 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-hookunraid-py quickstart (Python MCP server)
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Unraid MCP: common questions
- Is Unraid MCP server safe?
- Mostly: it is graded B (80/100). Read the Unraid MCP safety report
- How do I install Unraid MCP?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Unraid MCP need an API key?
- Yes. The registry entry asks for
UNRAID_API_KEY. - Is Unraid MCP maintained?
- The last commit was 6 days ago (2026-09-22). The latest release is v2.8.0.