Project

Also for this capability: API · CLI · MCP · SDKs

project: 52 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.

Arguments

op — what each one does:

• delete_project_by_slug — Deletes a project and takes its site off the internet.
• delete_project_by_slug_domains_by_host — Gives a custom hostname back, so the name is free to reuse.
• delete_project_by_slug_star — Removes the caller's own bookmark from a project, and answers whether it is starred afterwards.
• get_project — Returns every project your org owns.
• get_project_by_slug — Returns one project of yours by slug — its settings, its live URL and the deployment currently serving it.
• get_project_by_slug_deployments — Returns a project's deploy history, newest version first.
• get_project_by_slug_deployments_by_id — Returns one deployment of a project by id.
• get_project_by_slug_domains — Returns every custom hostname this site holds: the live ones, plus any pending claim with the DNS records it still owes.
• get_project_by_slug_releases — Returns a site's releases newest-first, marking the active one — the rollback menu.
• get_project_edge — health reports whether a publish reaches readers, rather than whether it was accepted.
• get_project_sites — Returns the org's deployed sites at the pretty URLs they serve at.
• get_project_sites_by_slug — Returns one site — the same row ListSites carries, for one slug.
• patch_project_by_slug — Changes a project's settings, and only the settings you send.
• post_project — Creates a project — the handle a site is deployed and served under — and answers 201 with it in draft.
• post_project_by_slug_deployments — Opens a deployment and hands back a short-lived, prefix-scoped grant to write its bytes straight to object storage.
• post_project_by_slug_deployments_by_id_complete — The CI completion hook that flips a queued git deployment to live (or error) once CI has synced the built site to S3.
• post_project_by_slug_domains — Attaches one or more CUSTOM public hostnames to this org's site.
• post_project_by_slug_domains_by_host_verify — Checks the DNS challenge for a pending custom hostname and, when it passes, promotes the host so it begins routing at the edge.
• post_project_by_slug_publish — Promotes a build output into a new release AND goes live with it — create+activate in one call, which is the 99% path.
• post_project_by_slug_purge — Flushes the site's edge cache without redeploying anything.
• post_project_by_slug_releases — Promotes a build output into a new immutable release WITHOUT serving it — the staged half of publishing, for when you want to check a release before it goes live.
• post_project_by_slug_releases_by_release_activate — Points the site at an existing release — the go-live, and equally the ROLLBACK.
• post_project_fork — Creates a project seeded from a PUBLISHED EXAMPLE — either a starter-kit template from the ONE embedded gallery catalog, or any live project on the platform (an example a seeded creator published, or another org's app serving at <slug>.hanzo.app).
• post_project_sites — Generates a self-contained, mobile-responsive static site from a natural-language brief and deploys it live in one call.
• post_project_sites_deploy — Deploys a caller-supplied file manifest — the deploy_site capability an agent calls — and answers with where it went live.
• put_project_by_slug_star — Bookmarks a project for the person calling, and answers whether it is starred afterwards.

tools/list declares a type, a description, which fields are required and an enumerated value set for each field and nothing further, and every column above is MCP's own. This tool takes an operation name and that operation's arguments, so what the document constrains is what goes inside input, field by field, on the operation you name — ask describe for that. A — means MCP does not constrain 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": "project",
         "arguments": {
           "op": "get_project"
         }
       }
     }'

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 MCP 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

project dispatches to 52 operations.

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

All 120 tools · MCP · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 120 tools captured 2026-09-30.