Comprehensive fixes across Python code, shell scripts, and documentation addressing all remaining MEDIUM and LOW priority review comments. Python Code Fixes (27 fixes): - tools/info.py: Simplified dispatch with lookup tables, defensive guards, CPU fallback formatting, !s conversion flags, module-level sync assertion - tools/docker.py: Case-insensitive container ID regex, keyword-only confirm, module-level ALL_ACTIONS constant - tools/virtualization.py: Normalized single-VM dict responses, unified list/details queries - core/client.py: Fixed HTTP client singleton race condition, compound key substring matching for sensitive data redaction - subscriptions/: Extracted SSL context creation to shared helper in utils.py, replaced deprecated ssl._create_unverified_context API - tools/array.py: Renamed parity_history to parity_status, hoisted ALL_ACTIONS - tools/storage.py: Fixed dict(None) risks, temperature 0 falsiness bug - tools/notifications.py, keys.py, rclone.py: Fixed dict(None) TypeError risks - tests/: Fixed generator type annotations, added coverage for compound keys Shell Script Fixes (13 fixes): - dashboard.sh: Dynamic server discovery, conditional debug output, null-safe jq, notification count guard order, removed unused variables - unraid-query.sh: Proper JSON escaping via jq, --ignore-errors and --insecure CLI flags, TLS verification now on by default - validate-marketplace.sh: Removed unused YELLOW variable, defensive jq, simplified repository URL output Documentation Fixes (24+ fixes): - Version consistency: Updated all references to v0.2.0 across pyproject.toml, plugin.json, marketplace.json, MARKETPLACE.md, __init__.py, README files - Tool count updates: Changed all "26 tools" references to "10 tools, 90 actions" - Markdown lint: Fixed MD022, MD031, MD047 issues across multiple files - Research docs: Fixed auth headers, removed web artifacts, corrected stale info - Skills docs: Fixed query examples, endpoint counts, env var references All 227 tests pass, ruff and ty checks clean.
5.3 KiB
name, description
| name | description |
|---|---|
| unraid | Query and monitor Unraid servers via the GraphQL API. Use when the user asks to 'check Unraid', 'monitor Unraid', 'Unraid API', 'get Unraid status', 'check disk temperatures', 'read Unraid logs', 'list Unraid shares', 'Unraid array status', 'Unraid containers', 'Unraid VMs', or mentions Unraid system monitoring, disk health, parity checks, or server status. |
Unraid API Skill
⚠️ MANDATORY SKILL INVOCATION ⚠️
YOU MUST invoke this skill (NOT optional) when the user mentions ANY of these triggers:
- "Unraid status", "disk health", "array status"
- "Unraid containers", "VMs on Unraid", "Unraid logs"
- "check Unraid", "Unraid monitoring", "server health"
- Any mention of Unraid servers or system monitoring
Failure to invoke this skill when triggers occur violates your operational requirements.
Query and monitor Unraid servers using the GraphQL API. Access all 27 read-only endpoints for system monitoring, disk health, logs, containers, VMs, and more.
Quick Start
Set your Unraid server credentials:
export UNRAID_URL="https://your-unraid-server/graphql"
export UNRAID_API_KEY="your-api-key"
Get API Key: Settings → Management Access → API Keys → Create (select "Viewer" role)
Use the helper script for any query:
./scripts/unraid-query.sh -q "{ online }"
Or run example scripts:
./scripts/dashboard.sh # Complete multi-server dashboard
./examples/disk-health.sh # Disk temperatures & health
./examples/read-logs.sh syslog 20 # Read system logs
Core Concepts
GraphQL API Structure
Unraid 7.2+ uses GraphQL (not REST). Key differences:
- Single endpoint:
/graphqlfor all queries - Request exactly what you need: Specify fields in query
- Strongly typed: Use introspection to discover fields
- No container logs: Docker container output logs not accessible
Two Resources for Stats
info- Static hardware specs (CPU model, cores, OS version)metrics- Real-time usage (CPU %, memory %, current load)
Always use metrics for monitoring, info for specifications.
Common Tasks
System Monitoring
Check if server is online:
./scripts/unraid-query.sh -q "{ online }"
Get CPU and memory usage:
./scripts/unraid-query.sh -q "{ metrics { cpu { percentTotal } memory { used total percentTotal } } }"
Complete dashboard:
./scripts/dashboard.sh
Disk Management
Check disk health and temperatures:
./examples/disk-health.sh
Get array status:
./scripts/unraid-query.sh -q "{ array { state parityCheckStatus { status progress errors } } }"
List all physical disks (including cache/USB):
./scripts/unraid-query.sh -q "{ disks { name } }"
Storage Shares
List network shares:
./scripts/unraid-query.sh -q "{ shares { name comment } }"
Logs
List available logs:
./scripts/unraid-query.sh -q "{ logFiles { name size modifiedAt } }"
Read log content:
./examples/read-logs.sh syslog 20
Containers & VMs
List Docker containers:
./scripts/unraid-query.sh -q "{ docker { containers { names image state status } } }"
List VMs:
./scripts/unraid-query.sh -q "{ vms { domain { name state } } }"
Note: Container output logs are NOT accessible via API. Use docker logs via SSH.
Notifications
Get notification counts:
./scripts/unraid-query.sh -q "{ notifications { overview { unread { info warning alert total } } } }"
Helper Script Usage
The scripts/unraid-query.sh helper supports:
# Basic usage
./scripts/unraid-query.sh -u URL -k API_KEY -q "QUERY"
# Use environment variables
export UNRAID_URL="https://unraid.local/graphql"
export UNRAID_API_KEY="your-key"
./scripts/unraid-query.sh -q "{ online }"
# Format options
-f json # Raw JSON (default)
-f pretty # Pretty-printed JSON
-f raw # Just the data (no wrapper)
Additional Resources
Reference Files
For detailed documentation, consult:
references/endpoints.md- Complete list of all 27 API endpointsreferences/troubleshooting.md- Common errors and solutionsreferences/api-reference.md- Detailed field documentation
Helper Scripts
scripts/unraid-query.sh- Main GraphQL query toolscripts/dashboard.sh- Automated multi-server inventory reporter
Quick Command Reference
# System status
./scripts/unraid-query.sh -q "{ online metrics { cpu { percentTotal } } }"
# Disk health
./examples/disk-health.sh
# Array status
./scripts/unraid-query.sh -q "{ array { state } }"
# Read logs
./examples/read-logs.sh syslog 20
# Complete dashboard
./scripts/dashboard.sh
# List shares
./scripts/unraid-query.sh -q "{ shares { name } }"
# List containers
./scripts/unraid-query.sh -q "{ docker { containers { names state } } }"
🔧 Agent Tool Usage Requirements
CRITICAL: When invoking scripts from this skill via the zsh-tool, ALWAYS use pty: true.
Without PTY mode, command output will not be visible even though commands execute successfully.
Correct invocation pattern:
<invoke name="mcp__plugin_zsh-tool_zsh-tool__zsh">
<parameter name="command">./skills/SKILL_NAME/scripts/SCRIPT.sh [args]</parameter>
<parameter name="pty">true</parameter>
</invoke>