post_v1_git_repos_name_push

Lands a set of files as one commit without a git client — the hanzo.app builder's push.

Lands a set of files as one commit without a git client — the hanzo.app builder's push. The repo is CREATED on first push, the files are merged onto the branch tip (unlisted files survive), and the same push-to-deploy hook a real receive-pack fires is fired, so downstream this is indistinguishable from a git push.


Tool	`post_v1_git_repos_name_push`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	4
Operation	`POST /v1/git/repos/{name}/push`
Product	git

Arguments

Field	Type	Required	Default	Description
`branch`	`string`	—	—	Branch to advance; empty means "main". A fresh branch that is the repo's first also becomes HEAD.
`files`	`pushFile[]`	—	—	Files are added to or overwritten on the branch tip — files already there and not listed SURVIVE. At least one, at most 5000, 32 MiB each.
`message`	`string`	—	—	Message is the commit message; empty gets a generated one.
`name`	`string`	—	—	Name is the repo to push into, from the :name path segment. It is CREATED on first push if it does not exist.

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.

Object types

pushFile are objects this tool's fields refer to. Each is declared inside the tool's own schema.

pushFile

Field	Type	Required	Default	Description
`content`	`string`	—	—	Content is the file's bytes, carried per Encoding.
`encoding`	`string`	—	—	Encoding is "base64", or "utf-8" (the default, also "utf8" / "text").
`path`	`string`	—	—	Path is repo-relative. Absolute or traversing paths are refused.

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_push",
         "arguments": {
           "branch": "<branch>",
           "files": [
             {}
           ],
           "message": "<message>",
           "name": "<name>"
         }
       }
     }'

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_push`	`POST /v1/git/repos/{name}/push`	git	Lands a set of files as one commit without a git client — the hanzo.app builder's push.

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).