Hanzo
Cloud MCPcloud

adminReloadPlugin

Swaps a plugin for another build without dropping a request.

Swaps a plugin for another build without dropping a request. The replacement is started and proven to be LISTENING before any traffic moves to it, so a bad build leaves the old one serving and returns an error rather than a hole; the old process then drains before it is killed.

With a version or url+sum it pins; naming a digest this host has run before is the rollback, and costs no network because the digest IS the cache key. With neither it restarts what is already loaded.

Fleet scope applies it to one host at a time and STOPS at the first failure, so a build that cannot come up reaches exactly one host.

TooladminReloadPlugin
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments5
OperationPOST /v1/admin/plugins/{name}/reload
Productcloud

Arguments

FieldTypeRequiredDefaultDescription
namestringName is the app, from the path. It must be one the manifest declares.
scopestringScope "host" applies here only. Default "fleet" rolls it out one host at a time, halting on the first host that fails to come up.
sumstring
urlstringURL is the artifact directly, for an origin with no index. Sum is its hex SHA-256 and is REQUIRED with it: zip refuses an unverified download, and so does this.
versionstringVersion is a release tag, resolved to a URL and digest through the origin's binaries.json index — the same index CI publishes, so there is no second table mapping versions to digests.

This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "adminReloadPlugin",
         "arguments": {
           "name": "<name>",
           "scope": "<scope>",
           "sum": "<sum>",
           "url": "<url>",
           "version": "<version>"
         }
       }
     }'

Values are placeholders derived from each field's declared type. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →

The operation behind it

OperationRouteProductSummary
cloud_adminReloadPluginPOST /v1/admin/plugins/{name}/reloadcloudSwaps a plugin for another build without dropping a request.

The same capability over plain HTTP is in the cloud API reference, on https://api.hanzo.ai.


All 834 tools · The door · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).

How is this guide?

On this page