Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server for Unraid API — provides tools to interact with an Unraid server's GraphQL API.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
UNRAID_API_URL, UNRAID_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"unraid": {
"command": "uvx",
"args": [
"unraid-mcp"
],
"env": {
"UNRAID_API_URL": "your-value",
"UNRAID_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add unraid --env UNRAID_API_URL=your-value --env UNRAID_API_KEY=your-value -- uvx unraid-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"unraid": {
"command": "uvx",
"args": [
"unraid-mcp"
],
"env": {
"UNRAID_API_URL": "your-value",
"UNRAID_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"unraid": {
"type": "stdio",
"command": "uvx",
"args": [
"unraid-mcp"
],
"env": {
"UNRAID_API_URL": "your-value",
"UNRAID_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain dinglebear.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: UNRAID_API_URL, UNRAID_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (2.10.3) reached the registry 18 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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 standalone
runraidandincus-unraidrepos were merged in here. Some
deployed plugin install/update URLs still depend on the old-name redirect;
migrating those runtime URLs requires a deliberate release. The **PyPI package, the container image, the Claude plugin, and the
Unraid
.plg** are all still namedunraid-mcp— only the repo changed.
| 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 the compatibility npm launcher @dinglebear/unraid. | 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 |
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. | — | — |
/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).
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 endpoint, TLS, authentication, and tool-selector settings; 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
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`](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.
cargo install --path unraid-rs --locked # from the repository root
runraid setup check # inspect setup without repairing files runraid array # read array state runraid serve mcp # MCP HTTP (default :40010; configure auth)
| 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/AGENTS.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.
Start with AGENTS.md, the canonical contributor guide. CLAUDE.md and GEMINI.md are symlinks to it, including within components. The documentation index links to development and verification, architecture, and release procedures.
Rust MCP supports UNRAID_RMCP_PROJECTION=legacy (default), atomic, or both. All projections share enabled-action policy, scopes, and execution; atomic mode is not a second backend. See the Rust README for selectors and migration.
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.
MIT — see LICENSE.