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.
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. Billed the nominal management fee: the customer brings the compute, Hanzo meters the management plane.
| Tool | attachCluster |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 4 |
| Operation | POST /v1/clusters |
| Product | clusters |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
default | boolean | — | — | — | Default marks this the org's default cluster for scheduling. |
kubeconfig | string | — | — | — | Kubeconfig is the cluster's kubeconfig, verbatim. Required — a body without one is not an attach. |
name | string | — | — | — | Name is the fleet-local name for the cluster; lower-cased, and the key the detach route addresses it by. Required. |
provider | string | — | — | — | Provider is a free-form label for where the cluster runs ("gke", "on-prem"); it is display only, not a routing key. |
tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.
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": "attachCluster",
"arguments": {
"default": false,
"kubeconfig": "<kubeconfig>",
"name": "<name>",
"provider": "<provider>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. default holds a stand-in that cannot be spelled that way — JSON gives a number, a boolean and a timestamp no placeholder form — so that value is this page's, not the API's. Neither the door nor the operation declares one. 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
| Operation | Route | Product | Summary |
|---|---|---|---|
attachCluster | POST /v1/clusters | clusters | Attaches a BYO cluster to the caller's org — the kubeconfig is validated, KMS-sealed and… |
The same capability over plain HTTP is in the clusters API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
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?