Git

Also for this capability: API · CLI · MCP · SDKs

git: 38 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.

Arguments

op — what each one does:

• delete_git_repo — Removes a repo's metadata and purges its storage.
• delete_git_repo_subscription — Removes one Slack subscription from a repo; the notifier stops posting that repo's events to that channel.
• delete_git_repo_target — Removes one outbound mirror target; later pushes stop being forwarded to it.
• list_git_keys — Returns the SSH public keys registered to the caller's org — the keys that authenticate git clone git@<host>:<org>/<repo>.git.
• list_git_pools — Returns the capacity this org has declared and how many daemons have entered each pool.
• list_git_repos — Returns the repos in the caller's scope, most recently updated first.
• get_git_repo — Returns one repo with its live ref state: every branch name and the resolved HEAD commit.
• get_git_repo_blob — Returns one file's bytes at one revision.
• list_git_repo_commits — Walks a ref's history newest first, or one path's history when a path is given.
• list_git_repo_files — Returns every file a glob selects at one revision, WITH its bytes and the revision they came from.
• list_git_repo_pulls — Returns a repo's pull requests, newest number first — what is waiting to be reviewed, and what has already landed.
• get_git_repo_pull — Returns one pull request by its per-repo number.
• get_git_repo_readme — Returns the README at the tree root as plain text — unrendered, so the caller decides how to present it.
• list_git_repo_refs — Lists a repo's branches, tags and default branch — what a branch picker needs in one call.
• list_git_repo_subscriptions — Returns a repo's Slack subscriptions — which channels the lifecycle notifier posts this repo's push and deploy events to.
• list_git_repo_targets — Returns a repo's outbound mirror targets — the downstream remotes the mirror reactor pushes to whenever a push lands here.
• get_git_repo_tree — Lists the immediate children of one directory at one revision, directories before files.
• list_git_runners — Returns the daemons registered into this org's pools, newest first, with when each was last heard from.
• list_git_runs — Returns this org's runs, newest first.
• get_git_run — Returns one run.
• get_git_usage — Returns per-repo and total storage bytes for the caller's org — the queryable, per-tenant number commerce and o11y meter on.
• list_git_workflows — Reports the workflows a repository declares at a ref and which declared pool would execute each job — the answer to "would a push here run, and where".
• update_git_repo — Flips a repo's public bit, the one mutable repo setting today.
• create_git_pool — Records the capacity an org has, and answers with the secret a runner daemon presents to enter it.
• create_git_repo — Provisions an empty bare repository in the caller's scope and returns it with its clone URLs.
• gc_git_repo — Repacks a repo into one bitmapped pack and rewrites its commit-graph, so the next clone reuses the bitmap instead of walking the whole object graph.
• mirror_git_repo — Imports an external git repository into the caller's repo, provisioning it on first use.
• create_git_repo_pull — Proposes a branch for merging and returns it with its number.
• merge_git_repo_pull — Merges an open pull request by FAST-FORWARDING base to head, and answers the proposal in its merged state with the revision base now points at.
• push_git_repo — Lands a set of files as one commit without a git client — the hanzo.app builder's push.
• create_git_repo_subscription — Binds a Slack channel to a repo, so the lifecycle notifier posts that repo's push and deploy events there.
• create_git_repo_target — Registers a downstream remote the repo's advanced refs are pushed to whenever a push lands here.
• create_git_run — Runs a repository's workflows at a ref, on demand.

tools/list declares a type, a description, which fields are required and an enumerated value set for each field and nothing further, and every column above is MCP's own. This tool takes an operation name and that operation's arguments, so what the document constrains is what goes inside input, field by field, on the operation you name — ask describe for that. A — means MCP does not constrain the field.

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.

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": "git",
         "arguments": {
           "op": "list_git_keys"
         }
       }
     }'

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 MCP 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

git dispatches to 38 operations. 1 of them MCP names exactly as the document ids it, and that one is below; for the rest MCP has its own verb, which describe resolves.

The same capability over plain HTTP is in the git API reference, on https://api.hanzo.ai.

All 120 tools · MCP · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 120 tools captured 2026-09-30.