Hanzo
Cloud MCPprojects

get_v1_projects_slug_domains

ListDomains returns every custom hostname this site holds: the live ones, plus any pending claim with the DNS records it still owes.

ListDomains returns every custom hostname this site holds: the live ones, plus any pending claim with the DNS records it still owes.

domains is the routing answer — the hosts that are verified right now — while claims is the full panel, one row per host, each saying whether it is live or pending and, if pending, exactly what to publish.

Scope: a validated principal is required (403 without one) and the site is resolved within that principal's org, so another tenant's slug is a 404.

Toolget_v1_projects_slug_domains
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments1, 1 required
OperationGET /v1/projects/{slug}/domains
Productprojects

Arguments

FieldTypeRequiredDefaultValuesDescription
slugstringyesSlug is the project to act on, from the path. It is unique within the caller's org and nowhere else, so another tenant's slug is a 404.

tools/list declares a type and a description for each field and nothing further. The Required column is taken from GET /v1/projects/{slug}/domains, the operation this tool dispatches to — the same declaration the REST API validates against. 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. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.

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": "get_v1_projects_slug_domains",
         "arguments": {
           "slug": "<slug>"
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source 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

OperationRouteProductSummary
cloud_get_v1_projects_slug_domainsGET /v1/projects/{slug}/domainsprojectsListDomains returns every custom hostname this site holds: the live ones, plus any…

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


All 833 tools · The door · API reference

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

How is this guide?

On this page