post_v1_git_repos_name_mirror
Imports an external git repository into the caller's repo, provisioning it on first use.
Imports an external git repository into the caller's repo, provisioning it on first use. Fetch is FORCED and covers every ref, so a first call clones the source and a repeat call re-syncs it — the endpoint is idempotent by mirror semantics. Mirrored bytes are metered exactly like a push, and a push.landed event is emitted for the default branch so the code index picks the repo up.
| Tool | post_v1_git_repos_name_mirror |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 3 |
| Operation | POST /v1/git/repos/{name}/mirror |
| Product | git |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
name | string | — | — | Name is the local repo to mirror into, from the :name path segment. It is CREATED on first use. |
project | string | — | — | Project is the sub-scope to land the repo in; empty uses the caller's own, exactly as a create would. |
source | string | — | — | Source is the http(s) git URL to fetch from. The host is SSRF-guarded and the shared mirror credential is only sent to allowlisted hosts. |
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_name_mirror",
"arguments": {
"name": "<name>",
"project": "<project>",
"source": "<source>"
}
}
}'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_name_mirror | POST /v1/git/repos/{name}/mirror | git | Imports an external git repository into the caller's repo, provisioning it on first use. |
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?