post_v1_git_repos
Provisions an empty bare repository in the caller's scope and returns it with its clone URLs. Answers 201.
Provisions an empty bare repository in the caller's scope and returns it with its clone URLs. Answers 201. The name must be unique within the scope — a repeat is a 409, never a silent overwrite of an existing repo. The org comes from the validated principal, so a repo is always born owned by the caller's own tenant.
| Tool | post_v1_git_repos |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 4 |
| Operation | POST /v1/git/repos |
| Product | git |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
description | string | — | — | Description is a free-form blurb, max 4KiB. |
name | string | — | — | Name is the repo's handle, unique within the scope, and the last segment of both clone URLs. Must match ^[A-Za-z0-9][A-Za-z0-9._-]{0,63}$; a trailing ".git" is stripped first. Required. |
project | string | — | — | Project narrows the repo to a sub-scope of the org. Omit it to use the caller's own X-Project-Id scope; it can never widen past the caller's org. |
public | boolean | — | — | Public grants ANONYMOUS read (fetch) only; push and the whole control plane stay org-authed. Defaults to false. |
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_git_repos",
"arguments": {
"description": "<description>",
"name": "<name>",
"project": "<project>",
"public": false
}
}
}'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_git_repos | POST /v1/git/repos | git | Provisions an empty bare repository in the caller's scope and returns it with its clone UR |
The same capability over plain HTTP is in the git 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?