Hanzo
Cloud MCPtemplates

put_v1_templates_slug

Overwrites the caller org's OWN starter kit at the path slug, answering the stored kit.

Overwrites the caller org's OWN starter kit at the path slug, answering the stored kit. A slug they do not own is 404, never a create: the UPDATE binds org, so a PUT can never reach another org's kit.

Toolput_v1_templates_slug
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments11
OperationPUT /v1/templates/{slug}
Producttemplates

Arguments

FieldTypeRequiredDefaultValuesDescription
categorystringCategory groups the kit in the gallery browser.
demostringDemo is the deployed site itself, when there is one.
descriptionstringDescription is the browse-card blurb, max 4096 characters.
featuresstring[]Features are the highlights the card lists, at most 32.
frameworkstringFramework is the stack the kit is built on ("Next.js 14").
previewstringPreview is the still image the browse card renders, max 4096 characters.
slugstringSlug is the kit to replace, from the path.
sourcestringSource is the repository the kit is forked from, max 4096 characters.
titlestringTitle is the display name. Required, max 200 characters.
useCasestringUseCase is what the kit is for, in a phrase.
variantsVariant[]Variants are the shapes this kit ships in, at most 32; the fork picks one.

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.

Object types

Variant is an object this tool's fields are made of, declared inside the tool's own schema and enumerated in full below.

Variant

FieldTypeRequiredDefaultValuesDescription
frameworkstringonly when it differs from the template's
idstringselector, unique within the template ("react", "grid-3-fluid")
kindstringthe axis it varies: format | page | theme
labelstringhuman label for the picker
sourcestringthe 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. 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": "put_v1_templates_slug",
         "arguments": {
           "category": "<category>",
           "demo": "<demo>",
           "description": "<description>",
           "features": [
             "<features>"
           ],
           "framework": "<framework>",
           "preview": "<preview>",
           "slug": "<slug>",
           "source": "<source>",
           "title": "<title>",
           "useCase": "<useCase>",
           "variants": [
             {
               "framework": "<framework>",
               "id": "<id>",
               "kind": "<kind>",
               "label": "<label>",
               "source": "<source>"
             }
           ]
         }
       }
     }'

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
put_v1_templates_slugPUT /v1/templates/{slug}templatesOverwrites the caller org's OWN starter kit at the path slug, answering the stored kit.

The same capability over plain HTTP is in the templates 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?

On this page