Hanzo
Cloud MCPcloudflare

post_v1_cloudflare_pages_projects

PagesCreate creates a Cloudflare Pages project on the org's account.

PagesCreate creates a Cloudflare Pages project on the org's account. Requires org admin. Only the modeled fields reach Cloudflare, so an unmodeled key in the request is dropped rather than forwarded.

Toolpost_v1_cloudflare_pages_projects
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments4
OperationPOST /v1/cloudflare/pages/projects
Productcloudflare

Arguments

FieldTypeRequiredDefaultDescription
build_configPagesBuildConfig
deployment_configsPagesDeploymentConfigs
namestring
production_branchstring

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

PagesBuildConfig, PagesD1Binding, PagesDeploymentConfig, PagesDeploymentConfigs, PagesEnvVar, PagesKVBinding, PagesR2Binding are objects this tool's fields refer to. Each is declared inside the tool's own schema.

PagesBuildConfig

FieldTypeRequiredDefaultDescription
build_commandstring
destination_dirstring
root_dirstring

PagesD1Binding

FieldTypeRequiredDefaultDescription
idstring

PagesDeploymentConfig

FieldTypeRequiredDefaultDescription
compatibility_datestring
compatibility_flagsstring[]
d1_databasesobject
env_varsobject
kv_namespacesobject
r2_bucketsobject

PagesDeploymentConfigs

FieldTypeRequiredDefaultDescription
previewPagesDeploymentConfig
productionPagesDeploymentConfig

PagesEnvVar

FieldTypeRequiredDefaultDescription
typestring
valuestring

PagesKVBinding

FieldTypeRequiredDefaultDescription
namespace_idstring

PagesR2Binding

FieldTypeRequiredDefaultDescription
namestring

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_cloudflare_pages_projects",
         "arguments": {
           "build_config": {},
           "deployment_configs": {},
           "name": "<name>",
           "production_branch": "<production_branch>"
         }
       }
     }'

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

OperationRouteProductSummary
cloud_post_v1_cloudflare_pages_projectsPOST /v1/cloudflare/pages/projectscloudflarePagesCreate creates a Cloudflare Pages project on the org's account.

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

On this page