post_v1_git_repos_name_subscriptions
Binds a Slack channel to a repo, so the lifecycle notifier posts that repo's push and deploy events there. Answers 201.
Binds a Slack channel to a repo, so the lifecycle notifier posts that repo's push and deploy events there. Answers 201. The same channel twice on one repo is a 409; a repo outside the caller's scope is a 404, exactly as reading it is.
| Tool | post_v1_git_repos_name_subscriptions |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 3 |
| Operation | POST /v1/git/repos/{name}/subscriptions |
| Product | git |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
channel | string | — | — | Channel is the Slack channel the notifier posts to — an id (C…/G…), a #name, or a bare name. Required. |
events | string[] | — | — | Events narrows delivery to these lifecycle kinds (push.landed, deploy.live, deploy.failed). Omit it to receive every deliverable kind; a kind that is never posted to Slack is refused rather than silently dropped. |
name | string | — | — | Name is the repo to subscribe, from the :name path segment. |
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_subscriptions",
"arguments": {
"channel": "<channel>",
"events": [
"<events>"
],
"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_subscriptions | POST /v1/git/repos/{name}/subscriptions | git | Binds a Slack channel to a repo, so the lifecycle notifier posts that repo's push and depl |
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?