SkillAgentSearch skills...

better-unraid-mcp

Unraid MCP server for Claude, Codex, Gemini CLI, and any MCP client. Monitor and manage your array, Docker, VMs, ZFS, shares, logs, and UPS in plain English. 67 tools, confirmation-gated writes, read-only mode, one npx command.

Install / Use

claude mcp add mswdev -- npx -y github:mswdev/better-unraid-mcp

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

83/100

Supported Platforms

Claude Code
Claude Desktop
Gemini CLI
OpenAI Codex

Our assessment of better-unraid-mcp

better-unraid-mcp scores 83/100 on our quality scale, 657th of 948 AI & Machine Learning skills we index.

Its MCP Server is 35 KB long, well organised into 41 sections with 13 code examples: a thorough specification that gives an agent plenty to work with.

It has 3 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
3/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated yesterday, so better-unraid-mcp is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 92/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

better-unraid-mcp compared with similar skills

All 4 of these similar skills score higher than better-unraid-mcp; compare them before choosing.

SkillScoreStarsUpdatedFormat
better-unraid-mcp (this skill)by mswdev8331d agoMCP Server
claude-memby thedotmack100117.9ktodayCLAUDE.md
Agent-Reachby Panniantong100112.7k10d agoCLAUDE.md
Understand-Anythingby Egonex-AI10093.0k2d agoCLAUDE.md
rufloby ruvnet10082.0ktodayCLAUDE.md

Frequently asked questions

How do I install better-unraid-mcp?
Run claude mcp add mswdev -- npx -y github:mswdev/better-unraid-mcp. The install tabs above show the steps for each supported agent.
Which AI agents does better-unraid-mcp work with?
It is written for Claude Code, Claude Desktop, Gemini CLI and OpenAI Codex, as a MCP Server file. Other agents that read the same format can often use it too.
Is better-unraid-mcp safe to use?
It is MIT-licensed and scores 92/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is better-unraid-mcp still maintained?
The repository was last updated yesterday, so better-unraid-mcp is actively maintained.
<div align="center">

Better Unraid MCP

Monitor and manage your Unraid server in plain English, from any MCP client.

npm version CI Coverage License: MIT Node.js 20+

MCP protocol 2026-07-28 MCP Registry Docker Claude Desktop bundle

Features · Quick start · Tools · MCP features · Configuration · HTTP transport · Security · FAQ · Development

<img src="assets/demo.svg" alt="Better Unraid MCP in a Claude Code session: asking why the array is degraded, getting a health rollup, and a gated container restart" width="760"> </div>

Better Unraid MCP is an open-source Unraid MCP server. It connects Claude Desktop, Claude Code, Codex, Gemini CLI, or any other Model Context Protocol client to the Unraid GraphQL API, so you can ask things like "why is my array degraded?", "tail the syslog", or "restart the Plex container".

Features

Ask a plain question and get a real answer from your server. "Why is my array degraded?" turns into calls to array_status and disk_list, and you find out which disk is unhappy and what SMART thinks of it without opening an SSH session or clicking through WebGUI tabs.

The 67 tools cover most of what you would normally do over SSH or in the WebGUI:

  • Diagnose problems in one conversation: unread alerts, CPU and memory pressure, network errors, disk temperatures, SMART health
  • Read any log on the server: list them all, tail the syslog, or page through the middle of a huge file
  • Manage Docker: container status and logs, per-container resource usage, start and stop, image updates, port conflict detection, boot autostart order
  • Control VMs through libvirt, from a graceful shutdown to a hard reset
  • Run the array: start or stop it, manage parity checks, review parity history, check the mover
  • Triage notifications: read, archive, and clear the alerts you have been putting off
  • Watch the UPS during an outage: battery charge, runtime estimate, load
  • Go past the API when you need to (optional, via SSH): read any file on the host, such as /boot/logs/syslog-previous, or run a confirmed one-off command
  • Work with ZFS: pool health, datasets, snapshots (create, destroy, rollback), and ARC usage
  • Reach the host when the API can't: processes, GPU metrics, disk spin, SMART deep reports, User Scripts, VM snapshots
  • Manage the platform itself: API keys, native .plg plugin installs, mover control, reboot and shutdown
  • Watch things live: WebSocket-fed resources for parity progress, Docker stats, system metrics (CPU, memory, network, temperature), UPS, array state, notifications, and log following (unraid://live/*, unraid://logs/{path})
  • Reach the rest of the API with raw graphql_query and a confirm-gated graphql_mutation while dedicated tools catch up

The tools are deliberately paranoid. A destructive tool refuses to run unless the request includes confirm: true, so a stray sentence in a chat can't stop your array. The operations that can really hurt (stopping the array, hard-killing a VM, rebooting the host) also need acknowledge_risk: true. If your client supports MCP elicitation, you get an interactive confirmation prompt instead. Every read works with a viewer-level API key, and MCP_READ_ONLY=true takes every state-changing tool out of the listing.

You don't install anything on the Unraid server. The MCP server runs on your machine, talks to Unraid's built-in GraphQL API with one API key, and starts with a single npx command.

Quick start

1. Create an Unraid API key

On your Unraid server (7.2 or newer), go to Settings > Management Access > API Keys and create a key. Or from the Unraid terminal:

unraid-api apikey --create

[!IMPORTANT] The key controls your server, so treat it like a password and give it the least privilege you need. A viewer-level key is enough for every read-only tool.

2. Add the server to your MCP client

<details open> <summary><strong>Claude Code</strong></summary>
claude mcp add better-unraid \
  -e UNRAID_API_URL=https://tower.local/graphql \
  -e UNRAID_API_KEY=your-api-key \
  -- npx -y better-unraid-mcp@latest
</details> <details> <summary><strong>Claude Desktop</strong></summary>

Add an entry to the mcpServers object in your claude_desktop_config.json:

{
  "mcpServers": {
    "better-unraid": {
      "command": "npx",
      "args": ["-y", "better-unraid-mcp@latest"],
      "env": {
        "UNRAID_API_URL": "https://tower.local/graphql",
        "UNRAID_API_KEY": "your-api-key"
      }
    }
  }
}
</details> <details> <summary><strong>Codex</strong></summary>
codex mcp add better-unraid \
  --env UNRAID_API_URL=https://tower.local/graphql \
  --env UNRAID_API_KEY=your-api-key \
  -- npx -y better-unraid-mcp@latest

Or add a server table to ~/.codex/config.toml:

[mcp_servers.better-unraid]
command = "npx"
args = ["-y", "better-unraid-mcp@latest"]
env = { UNRAID_API_URL = "https://tower.local/graphql", UNRAID_API_KEY = "your-api-key" }
</details> <details> <summary><strong>Gemini CLI</strong></summary>

Add an entry to the mcpServers object in ~/.gemini/settings.json:

{
  "mcpServers": {
    "better-unraid": {
      "command": "npx",
      "args": ["-y", "better-unraid-mcp@latest"],
      "env": {
        "UNRAID_API_URL": "https://tower.local/graphql",
        "UNRAID_API_KEY": "your-api-key"
      }
    }
  }
}
</details>

If your server uses a self-signed TLS certificate on the LAN, also set UNRAID_ALLOW_SELF_SIGNED=true. To turn on the SSH-backed tools (reading files like /boot/logs/syslog-previous, ZFS, running one-off commands, and the rest of the tools marked SSH below), also pass the UNRAID_SSH_* variables described under Configuration. @latest keeps you on the newest release; pin a version (for example better-unraid-mcp@0.1.3) if you want fully predictable behavior.

Other ways to install

All of them run the same server, and none of them install anything on the Unraid box.

| Option | Details | | --- | --- | | Claude Desktop, one click | Download better-unraid-mcp-<version>.mcpb from the latest release and open it. Claude Desktop asks for the URL and API key. | | Claude Code plugin marketplace | claude plugin marketplace add mswdev/better-unraid-mcp, then claude plugin install better-unraid@better-unraid-mcp. The plugin reads UNRAID_API_URL and UNRAID_API_KEY from your environment. | | Docker (remote HTTP transport) | ghcr.io/mswdev/better-unraid-mcp. See Docker. | | MCP Registry | Listed as io.github.mswdev/better-unraid-mcp for clients that browse the registry. |

Cautious quickstart (read-only)

Not ready to let a model touch anything? Add MCP_READ_ONLY=true to the environment above and the server registers only the read-only tools. The state-changing tools aren't refused at call time; they never appear at all. Pair that with a VIEWER-role API key and nothing in this server can change your machine.

3. Verify your setup

Before wiring up a client, run the built-in doctor with the same environment:

UNRAID_API_URL=https://tower.local/graphql UNRAID_API_KEY=... npx better-unraid-mcp doctor

It prints one line per check (GraphQL reachability and versions, schema skew against the server's API version, SSH when configured, rate limiting, and read-only mode) and exits non-zero when something is broken:

✓ Reachable in 12 ms — Unraid 7.3.2, API 4.37.4+ad268301, online=true.
✓ Vendored schema matches the server API (4.37.4 vs 4.37.4+ad268301).
⚠ SSH: not configured (optional). Host tools (...) are unavailable; set UNRAID_SSH_* to enable them.
✓ Client-side rate limiting active: 90 request burst, 9/s refill.
✓ read-only mode: disabled — mutating tools are registered (each behind its confirm gate).
doctor: OK

4. Try it

Ask your client:

"What's the status of my Unraid array?"

Tools

Read-only tools never change anything. Destructive tools always require confirm: true; without it they refuse and leave your server alone.

| Category | Tools | | --- | --- | | System and storage | 14 | | Array control | 3 | | Docker | 9 | | Virtual machines | 4 | | Notifications | 8 | | Observability | 4 | | Plugins | 4 | | ZFS (SSH) | 4 | | Host configuration (SSH) | 7 | | Backup (SSH) | 1 | | User Scripts (SSH) | 2 | | API keys | 2 | | UPS | 1 | | Host shell (optional, needs SSH) | 2 | | Raw GraphQL (advanced) | 2 |

Speed and safety

The SSH channel is one kept-alive connection: it connects lazily, sends keepalive probes, reconnects on its own, and closes after UNRAID_SSH_IDLE_SECONDS of idle time, so commands don't pay for a new handshake each time. GraphQL requests reuse a keep-alive HTTP agent and have a hard 30-second timeout, and idempotent queries get a small jittered retry on transient failures. The busiest reads (system_metrics, array_status, docker_container_list) come from a 5-second snapshot cache, and detailed output includes data_age_ms so you can see how fresh the data is. Long-running shell_exec and docker_container_update calls send MCP progress notifications when the client asks for them (stdio or session-mode HTTP).

All tool output goes through secret redaction: your configured API key, SSH password, and bearer token, plus credential-shaped key/value pairs and JWTs, come back as [redacted]. A client-side rate limiter keeps request bursts inside the Unraid API's throttle, and oversized JSON results are truncated into an envelope that still parses with JSON.parse.

System and storage

<details> <summary>14 tools</summary>

| Tool | Type | Description | | --- | --- | --- | | system_info | read-only | OS, kernel, uptime, hostname, and CPU summary. | | array_status | read-only | Array state, capacity, current parity-check status, and per-disk health. | | parity_history | read-only | Recent parity checks (date, status, errors, speed). | | disk_list | read-only | Physical disks with model, size, SMART status, temperature, and partitions. | | disk_smart_report | read-only | Full smartctl attribute report for one disk (SSH). | | disk_spin

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars3
CategoryAI
Updated1d ago
Forks0

Languages

TypeScript

Trust signals

92/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 low