unraid-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNRAID_HOST | No | Hostname/IP of the Unraid server. Required unless UNRAID_API_URL is set. | |
| UNRAID_API_KEY | No | API key from `unraid-api apikey --create`. | |
| UNRAID_API_URL | No | Full GraphQL endpoint override. | http://{host}/graphql |
| UNRAID_TIMEOUT | No | Read timeout in seconds. | 30 |
| UNRAID_LOG_LEVEL | No | Logging level. | INFO |
| UNRAID_TRANSPORT | No | Transport mode: stdio or http. | stdio |
| UNRAID_VERIFY_SSL | No | Set to 0 or provide a path to a CA bundle. | 1 |
| UNRAID_ALLOW_WRITES | No | Master write switch. | 0 |
| UNRAID_MAX_RESPONSE_BYTES | No | Response size cap. | 40000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| unraidC | Single entry point for all Unraid operations. Use health.capabilities to discover available actions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The tool is a single entry point, so all operations funnel through it, but that is an intra-tool concern rather than inter-tool ambiguity.
The lone tool is named 'unraid', which is trivially consistent since there is no other name to conflict with. However, it does not follow a descriptive verb_noun convention, making it slightly less predictable than ideal.
One tool for an entire Unraid management server is far too few. The domain typically involves discrete operations for array, disk, Docker, VM, and share management, and a single catch-all tool is a poor fit for that scope.
The tool claims to be a single entry point for all Unraid operations with capability discovery, suggesting broad coverage. The opaque surface and lack of explicit operations is a minor gap, but the design intends complete access.