clusters
6 MCP tools on the Hanzo cloud door that call the clusters API.
The 6 tools tools/list names for clusters. Each dispatches to an operation in the clusters API reference.
| Tool | Route | Arguments | Required | Description |
|---|---|---|---|---|
attachCluster | POST /v1/clusters | 4 | — | Attaches a BYO cluster to the caller's org — the kubeconfig is validated, KMS-sealed and added to… |
createNodePool | POST /v1/clusters/{clusterId}/pools | 8 | — | Adds a node pool to one of the caller org's clusters and answers 201 with the created pool. |
deleteNodePool | DELETE /v1/clusters/{clusterId}/pools/{poolId} | 3 | clusterId, poolId | Removes a node pool from one of the caller org's clusters. |
detachCluster | DELETE /v1/clusters/{id} | 1 | id | Removes a BYO cluster from the caller org's fleet. |
listClusters | GET /v1/clusters | 0 | — | Returns the caller org's clusters from both sources: the managed clusters projected from Visor's… |
scaleNodePool | POST /v1/clusters/{clusterId}/pools/{poolId}/scale | 4 | — | Resizes a node pool to an absolute node count and returns the pool as Visor reports it after the… |
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?
put_v1_channels_allowlist
Edits the caller org's access policy for one channel and answers the policy as GET would, so both verbs return ONE shape. It requires ORG ADMIN.
attachCluster
Attaches a BYO cluster to the caller's org — the kubeconfig is validated, KMS-sealed and added to the fleet — and answers 201 with the cluster as it now appears on GET /v1/clusters.