Potencia tu agente
El comando propio del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
npx -y @dinglebear/[email protected]Claude Code no tiene enlace de instalación para un comando local. Copia el comando de abajo y ejecútalo en una terminal.
UNRAID_API_URL=<value> UNRAID_API_KEY=<secret> UNRAID_RMCP_VERSION=<value> UNRAID_RMCP_REPO=<value> UNRAID_RMCP_RELEASE_BASE_URL=<value> RUST_LOG=<value> claude mcp add ai.dinglebear-unraid -- npx -y @dinglebear/unraid@0.6.3Ejecútalo en una terminal.
{ "mcpServers": { "ai.dinglebear-unraid": { "command": "npx", "args": [ "-y", "@dinglebear/[email protected]" ], "env": { "UNRAID_API_URL": "<value>", "UNRAID_API_KEY": "<secret>", "UNRAID_RMCP_VERSION": "<value>", "UNRAID_RMCP_REPO": "<value>", "UNRAID_RMCP_RELEASE_BASE_URL": "<value>", "RUST_LOG": "<value>" } } }}claude_desktop_config.json
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDel publicador
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 → on 2026-07-27, and the former standalone and repos 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 are all still named — only the repo changed.
Rust MCP server and CLI for Unraid GraphQL operations across NAS, Docker, VM, and storage workflows.
unraid-mcpunraidrunraidincus-unraid.plgunraid-mcp/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 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
# Configure UNRAID_API_URL and UNRAID_API_KEY privately before querying.
runraid setup check # inspect setup without repairing files
runraid array # read array state
runraid serve mcp # MCP HTTP (default :40010; configure auth)
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.
Rust MCP server and CLI for Unraid GraphQL operations across NAS, Docker, VM, and storage workflows.
{ "mcpServers": { "ai.dinglebear-unraid": { "command": "npx", "args": [ "-y", "@dinglebear/[email protected]" ], "env": { "UNRAID_API_URL": "<value>", "UNRAID_API_KEY": "<secret>", "UNRAID_RMCP_VERSION": "<value>", "UNRAID_RMCP_REPO": "<value>", "UNRAID_RMCP_RELEASE_BASE_URL": "<value>", "RUST_LOG": "<value>" } } }}Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
El publicador indica estas variables de entorno: UNRAID_API_URL, UNRAID_API_KEY, UNRAID_RMCP_VERSION, UNRAID_RMCP_REPO, UNRAID_RMCP_RELEASE_BASE_URL, RUST_LOG.
Unraid RMCP se ejecuta localmente por stdio.
Última comprobación: 2026-11-09. Rust MCP server and CLI for Unraid GraphQL operations across NAS, Docker, VM, and storage workflows.