post_v1_cloudflare_workers_zones_zone_routes
WorkersRouteCreate binds a URL pattern in a zone to a Worker script.
WorkersRouteCreate binds a URL pattern in a zone to a Worker script. Requires org admin — a route is what puts a script in front of live traffic.
| Tool | post_v1_cloudflare_workers_zones_zone_routes |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 3 |
| Operation | POST /v1/cloudflare/workers/zones/{zone}/routes |
| Product | cloudflare |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
pattern | string | — | — | — | Pattern is the URL pattern to bind, e.g. "acme.com/api/*". |
script | string | — | — | — | Script is the Worker script to dispatch to. Omit it to leave the pattern bound to no script, which is how Cloudflare expresses "bypass the Worker here". |
zone | string | — | — | — | Zone is the 32-hex Cloudflare zone id, from the path. |
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.
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": "post_v1_cloudflare_workers_zones_zone_routes",
"arguments": {
"pattern": "<pattern>",
"script": "<script>",
"zone": "<zone>"
}
}
}'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
| Operation | Route | Product | Summary |
|---|---|---|---|
post_v1_cloudflare_workers_zones_zone_routes | POST /v1/cloudflare/workers/zones/{zone}/routes | cloudflare | Binds a URL pattern in a zone to a Worker script. |
The same capability over plain HTTP is in the cloudflare 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?
post_v1_cloudflare_workers_scripts_script_subdomain
WorkersScriptSubdomainSet publishes or withdraws one Worker script on the account's workers.dev subdomain.
post_v1_cloudflare_zones_zone_purge
ZonePurge drops a zone's Cloudflare edge cache — either the whole zone (purge_everything) or exactly the listed file URLs. Requires org admin. Purging is the one zone-scoped WRITE this plane owns.