unraid-code-mode-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TRANSPORT | No | Transport mode: 'stdio' (default) or 'http'. | |
| UNRAID_API_KEY | Yes | API key for authenticating with the Unraid server. | |
| UNRAID_BASE_URL | Yes | The base URL of the Unraid server (e.g., https://tower.local or https://192.168.1.10). | |
| UNRAID_INSECURE | No | Set to 'true' to skip TLS verification (lab use only). | |
| UNRAID_CA_CERT_PATH | No | Path to a CA certificate file for TLS verification. | |
| UNRAID_EXECUTE_TIMEOUT_MS | No | Sandbox execution timeout in milliseconds (1 s – 10 min, default 30000). |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search the Unraid GraphQL schema by writing JavaScript. The sandbox is read-only — no network. Use this tool to discover what to call before invoking Globals
Examples |
| executeA | Run Unraid GraphQL operations by writing JavaScript that uses the Although the sandbox is JavaScript, the calls below appear synchronous — Surfaces:
Operations are async — use ExamplesLimits
|
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 2 tools
The two tools have clearly distinct purposes: 'execute' runs GraphQL operations, while 'search' explores the schema. There is no overlap, and their descriptions unambiguously differentiate them.
Both tool names are single, lowercase verbs that directly describe their function. Although they lack a verb_noun pattern, they follow a consistent, simple style that is easy to understand.
With only 2 tools, each covers a fundamental aspect of interacting with a GraphQL API: discovery and execution. The count is perfectly scoped for the server's purpose, avoiding unnecessary complexity.
The server provides all necessary functionality: you can explore the schema with 'search' and then execute any discovered operation with 'execute'. There are no obvious gaps in coverage.