v0.1.33

UnraidClaw 0.1.33 adds an optional MCP endpoint so Claude Code, Codex and other MCP clients can use the same 55 tools as the OpenClaw plugin, and ships a new unraidclaw command-line client for the server and for remote machines. Docker, VM, array, parity, share and notification actions now validate their input more strictly and check the real state before reporting success. TLS certificates gain alternative names so clients can verify the host, and a few login and logging bugs are fixed.

Highlights

MCP support

• New Streamable HTTP endpoint at /mcp on the service port, off by default and switched on with Enable MCP in Settings. It exposes the same 55 tools with the same API key, permissions, input validation and activity logging as the REST API. REST and the OpenClaw plugin keep working as before.
• Activity log entries for MCP tool calls name the tool and show the outcome of the API route it ran. Successful MCP handshakes and GET/DELETE responses with status 405 are left out of the log; other failed connection requests are still logged.
• Setup for Claude Code, Codex and other clients is described in the MCP section of the README.

Command-line client

• The plugin now installs the unraidclaw command at /usr/local/bin/unraidclaw, with the same tools and permissions as OpenClaw and MCP. On the server it finds the local gateway and trusts its certificate on its own; set the API key once with unraidclaw config set-key.
• For other machines, the same client is published as unraidclaw-cli on npm and as unraidclaw-cli-0.1.33.tar.gz on this release. It needs Node.js 22 or newer.
• Connection errors name the cause (untrusted certificate, address not in the certificate, nothing listening, protocol mismatch or DNS), and invalid arguments name the failing flag and rule. Tables and help are shorter, logs and nested values are formatted for reading, certificate details are shown once when trusting in table mode, and supported dry runs proceed without confirmation.
• See the CLI guide for install, credentials, certificate trust, all commands and exit codes.

TLS certificate

• Generated certificates now list the server's host name, its .local name, loopback and stable global addresses in subjectAltName, so clients that trust the certificate can verify the host name.
• Settings shows the certificate's subject, alternative names, expiry and SHA-256 fingerprint, so remote CLI users can compare the fingerprint before trusting it.
• A Regenerate certificate button replaces the certificate when the server's address or host name changed. It keeps the old pair as .bak files (older backups get numbered suffixes) and restarts the service.

Security and reliability fixes

• A parity check started with correct sent as the text "false" no longer runs as a correcting check. The field must now be true or false.
• Share comments containing quotes, backslashes, $, backticks or control characters are rejected, since they could write extra keys into the share's config file. Share settings are now written atomically and read back.
• Docker, VM, array, parity and notification actions reject malformed input and unknown fields, refuse IDs that start with -, time out instead of hanging, and check the real state afterwards. Responses include a verified field; a VM shutdown or reboot still in progress returns verified: false.
• A container created through the API keeps its Unraid template even when it exits right after starting, and a failed create reports Docker's error without echoing environment values.
• Requests to paths that do not exist return 404 instead of 401 when sent without a key, and no longer count toward the failed-login limit. MCP clients that probe for OAuth metadata locked themselves out before connecting.
• /api/health stays public and unlogged when called with a query string.
• /api/health no longer reports the previous version after an upgrade until the service restarted again. The package now records its own version instead of the service reading it from the .plg, which Unraid saves only after the install script restarts the service.

Other changes

• Settings Apply reports when the service did not end up running or stopped, and no longer restarts the service when the settings file could not be written.
• The Disk Info permission description no longer mentions SMART data, which the disk endpoints do not return.
• The unused vms:create permission is removed from the VM Manager preset.

Upgrade notes

• MCP is off after the upgrade. Turn it on with Enable MCP in Settings if you want the /mcp endpoint.
• A certificate created by an earlier version has no subjectAltName and is replaced once on the first service start after the upgrade. The previous pair is kept as cert.pem.bak and key.pem.bak in /boot/config/plugins/unraidclaw/tls. Clients that pinned or trusted the old certificate must trust the new one; the OpenClaw plugin with tlsSkipVerify: true is not affected.
• Regenerating the certificate from Settings has the same effect: clients that trusted the old certificate must trust the new one.
• Docker, VM, array, parity, share and notification routes now reject unknown fields and wrongly typed values that earlier versions accepted. Check API scripts that send extra or loosely typed fields, and note that responses from these routes now carry a verified field.
• Unknown paths answer 404 without a key where they previously answered 401.

Install and downloads

• Unraid plugin: update from the Unraid WebGUI (Plugins > Check for Updates) or install through Community Applications. unraidclaw-0.1.33-x86_64-1.txz is the package the WebGUI downloads; you do not need to fetch it by hand.
• CLI: npm install -g unraidclaw-cli, or download unraidclaw-cli-0.1.33.tar.gz for machines without npm. Verify it with the .sha256 file, extract it, and make sure Node.js 22 or newer is on PATH. On Linux, macOS and Windows; see the CLI guide.
• OpenClaw plugin: unraidclaw 0.1.15 is published to npm alongside this version. See OpenClaw plugin in the README for install and update commands.
• Checksums: the .md5 file covers the .txz package and the .sha256 file covers the CLI archive.