post_v1_integrations_github_repos_import
GithubImport imports the selected (or all) granted repos into git.hanzo.ai.
GithubImport imports the selected (or all) granted repos into git.hanzo.ai. The selection is intersected with the installation's GRANTED set, so a client can never import a repo the App was not granted (org isolation + a grant check). The import runs in a bounded background worker (don't block the request), so the answer is 202 Accepted; poll GET /v1/integrations/github/repos for the per-repo status to flip to imported.
| Tool | post_v1_integrations_github_repos_import |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2 |
| Operation | POST /v1/integrations/github/repos/import |
| Product | integrations |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
all | boolean | — | — | All imports every repository the installation grants, instead of naming them. Archived and disabled repositories are skipped either way — they cannot be fetched. |
repos | string[] | — | — | Repos names the repositories to import, either owner-qualified ("hanzo-apps/ai") or as a bare name ("ai"); a trailing ".git" is stripped. A bare name that matches more than one granted repository is an error rather than a guess, because one Hanzo org may hold several GitHub installations and a name is only unique within an owner. Ignored when all is true. |
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.
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_integrations_github_repos_import",
"arguments": {
"all": false,
"repos": [
"<repos>"
]
}
}
}'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
| Operation | Route | Product | Summary |
|---|---|---|---|
cloud_post_v1_integrations_github_repos_import | POST /v1/integrations/github/repos/import | integrations | GithubImport imports the selected (or all) granted repos into git.hanzo.ai. |
The same capability over plain HTTP is in the integrations 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?