post_v1_templates
Creates a starter kit PRIVATE to the caller's org and answers 201 with the stored kit.
Creates a starter kit PRIVATE to the caller's org and answers 201 with the stored kit. The owner is stamped by the server, so a body "org" is never trusted; publishing over a public-catalog slug is 409, so a slug still names exactly one kit.
| Tool | post_v1_templates |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 11 |
| Operation | POST /v1/templates |
| Product | cloud |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
category | string | — | — | Category groups the kit in the gallery browser. |
demo | string | — | — | Demo is the deployed site itself, when there is one. |
description | string | — | — | Description is the browse-card blurb, max 4096 characters. |
features | string[] | — | — | Features are the highlights the card lists, at most 32. |
framework | string | — | — | Framework is the stack the kit is built on ("Next.js 14"). |
preview | string | — | — | Preview is the still image the browse card renders, max 4096 characters. |
slug | string | — | — | Slug is the kit's identity — lowercase alphanumeric with dashes, max 40. |
source | string | — | — | Source is the repository the kit is forked from, max 4096 characters. |
title | string | — | — | Title is the display name. Required, max 200 characters. |
useCase | string | — | — | UseCase is what the kit is for, in a phrase. |
variants | Variant[] | — | — | Variants are the shapes this kit ships in, at most 32; the fork picks one. |
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.
Object types
Variant are objects this tool's fields refer to. Each is declared inside the tool's own schema.
Variant
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
framework | string | — | — | only when it differs from the template's |
id | string | — | — | selector, unique within the template ("react", "grid-3-fluid") |
kind | string | — | — | the axis it varies: format | page | theme |
label | string | — | — | human label for the picker |
source | string | — | — | the repository this shape is forked from; the synthesized default shape carries the template's own |
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": "post_v1_templates",
"arguments": {
"category": "<category>",
"demo": "<demo>",
"description": "<description>",
"features": [
"<features>"
],
"framework": "<framework>",
"preview": "<preview>",
"slug": "<slug>",
"source": "<source>",
"title": "<title>",
"useCase": "<useCase>",
"variants": [
{}
]
}
}
}'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
| Operation | Route | Product | Summary |
|---|---|---|---|
cloud_post_v1_templates | POST /v1/templates | cloud | Creates a starter kit PRIVATE to the caller's org and answers 201 with the stored kit. |
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?