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

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.

Object types

pushFile is an object this tool's fields are made of, declared inside the tool's own schema and enumerated in full below.

pushFile

Field	Type	Required	Default	Values	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. 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_git_repos_name_push",
         "arguments": {
           "branch": "<branch>",
           "files": [
             {
               "content": "<content>",
               "encoding": "<encoding>",
               "path": "<path>"
             }
           ],
           "message": "<message>",
           "name": "<name>"
         }
       }
     }'

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