Unraid RMCP

Rust MCP server and CLI for Unraid GraphQL, NAS, Docker, VM, and storage workflows.

Unraid RMCP is a Rust-implemented MCP server and command-line interface designed to expose Unraid system management capabilities to AI agents. It communicates over stdio transport and connects to an Unraid instance via a configurable API URL and API key, both supplied through environment variables. The server targets the full range of Unraid operational domains: GraphQL API interactions, NAS file and storage management, Docker container workflows, virtual machine control, and disk or array storage operations.

Configuration is handled entirely through environment variables. UNRAID_API_URL and UNRAID_API_KEY point the server at a specific Unraid instance. UNRAID_RMCP_VERSION, UNRAID_RMCP_REPO, and UNRAID_RMCP_RELEASE_BASE_URL control versioning and release resolution. RUST_LOG governs log verbosity. The package is distributed via npm under version 0.2.3 and is published by ai.dinglebear.

No tool list is published in the registry record, so the exact set of operations an agent can invoke at runtime is not enumerable from this entry. Developers should inspect the repository at github.com/jmagar/unraid-rmcp to understand current tool coverage before integrating. Because transport is stdio only, this server is not suitable for deployments that require HTTP or SSE-based MCP transport.

Use cases

  • Automate Docker container management on an Unraid host through an AI agent
  • Query Unraid system state via its GraphQL API from an agent workflow
  • Monitor and manage NAS storage arrays without manual UI interaction
  • Orchestrate virtual machine start, stop, or status checks on Unraid from an agent
  • Integrate Unraid disk and storage health data into an automated pipeline

When to use it

  • The target system runs Unraid and exposes its API at a reachable URL
  • An AI agent needs to automate Docker, VM, or NAS operations on Unraid
  • The deployment environment supports stdio-based MCP transport
  • GraphQL-level access to Unraid system data is required by an agent

When not to use it

  • The deployment requires HTTP or SSE MCP transport rather than stdio
  • The managed server does not run Unraid
  • A full enumeration of available tools is needed before integration, since no tool list is published in the registry record
  • A production environment requires a stable, audited license — no license is specified for this package