Cloud MCPtemplates
templates
5 MCP tools on the Hanzo cloud door that call the templates API.
The 5 tools tools/list names for templates. Each dispatches to an operation in the templates API reference.
| Tool | Route | Arguments | Required | Description |
|---|---|---|---|---|
delete_v1_templates_slug | DELETE /v1/templates/{slug} | 1 | slug | Deletes the caller org's OWN starter kit. A slug they do not own is a 404, never a delete: the… |
get_v1_templates | GET /v1/templates | 0 | — | Lists the public starter-kit catalog plus, for a validated caller, that org's own private kits. |
get_v1_templates_slug | GET /v1/templates/{slug} | 1 | slug | Returns one starter kit: the caller org's own by that slug, else the public catalog's. |
post_v1_templates | POST /v1/templates | 11 | — | Creates a starter kit PRIVATE to the caller's org and answers 201 with the stored kit. |
put_v1_templates_slug | PUT /v1/templates/{slug} | 11 | — | Overwrites the caller org's OWN starter kit at the path slug, answering the stored kit. |
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?