post_v1_integrations_github_repos_repo_pages
Creates the repo's Pages site and answers 201 Created with it.
Creates the repo's Pages site and answers 201 Created with it. With buildType "workflow" the site builds via GitHub Actions; otherwise it builds from a branch source, defaulting to the repo's own default branch when none is given. Only "/" and "/docs" are legal source paths (GitHub's rule).
| Tool | post_v1_integrations_github_repos_repo_pages |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 4 |
| Operation | POST /v1/integrations/github/repos/{repo}/pages |
| Product | integrations |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
branch | string | — | — | — | Branch is the legacy source branch; empty defaults to the repo's own default branch. Ignored when buildType is "workflow". |
buildType | string | — | — | — | BuildType selects the builder: "workflow" builds via GitHub Actions, anything else builds from the branch source above. |
path | string | — | — | — | Path is the source directory within the branch: "/" (the default) or "/docs". GitHub allows no others. |
repo | string | — | — | — | Repo is the repository, from the :repo path segment. |
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_integrations_github_repos_repo_pages",
"arguments": {
"branch": "<branch>",
"buildType": "<buildType>",
"path": "<path>",
"repo": "<repo>"
}
}
}'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_integrations_github_repos_repo_pages | POST /v1/integrations/github/repos/{repo}/pages | integrations | Creates the repo's Pages site and answers 201 Created with it. |
The same capability over plain HTTP is in the integrations 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?