Hanzo
Cloud MCPcloud

adminInfra

Serves the whole DigitalOcean infrastructure board: droplets, volumes, DOKS clusters and load balancers, each cross-referenced against every cluster's live Kubernetes state so the board can say what i

Serves the whole DigitalOcean infrastructure board: droplets, volumes, DOKS clusters and load balancers, each cross-referenced against every cluster's live Kubernetes state so the board can say what is safe to destroy and what is not.

It is cached for up to a minute because one read is a fan-out over the DO API plus a full pod/PV listing per cluster. Staleness is never load-bearing: every MUTATION re-scans from scratch and ignores this cache.

Only an unusable DO account is a hard failure. A partial read still produces a board, with the failing source named in sources[] — except for clusters and volumes, which the safety verdict depends on; without those the analysis degrades rather than classifying anything it cannot prove.

TooladminInfra
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments1
OperationGET /v1/admin/infra
Productcloud

Arguments

FieldTypeRequiredDefaultDescription
refreshstringRefresh, when present, forces a full re-scan instead of serving the cached snapshot. Every MUTATION re-scans regardless — this is only for the reader.

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": "adminInfra",
         "arguments": {
           "refresh": "<refresh>"
         }
       }
     }'

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_adminInfraGET /v1/admin/infracloudServes the whole DigitalOcean infrastructure board: droplets, volumes, DOKS clusters and l

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