Cloud MCPtracker
tracker
8 MCP tools on the Hanzo cloud door that call the tracker API.
The 8 tools tools/list names for tracker. Each dispatches to an operation in the tracker API reference.
| Tool | Route | Arguments | Description |
|---|---|---|---|
delete_v1_tracker_projects_key | DELETE /v1/tracker/projects/{key} | 1 | DeleteProject removes one tracker project of the caller's org AND every issue filed under it, and an |
delete_v1_tracker_projects_key_issues_num | DELETE /v1/tracker/projects/{key}/issues/{num} | 2 | DeleteIssue removes one issue from a tracker project and answers 204 with no body. |
get_v1_tracker_projects | GET /v1/tracker/projects | 0 | ListProjects returns every tracker project in the caller's org, newest first. |
get_v1_tracker_projects_key | GET /v1/tracker/projects/{key} | 1 | GetProject returns one tracker project of the caller's org by its key — its name, description and ti |
get_v1_tracker_projects_key_issues | GET /v1/tracker/projects/{key}/issues | 5 | ListIssues returns the issues of one tracker project, optionally filtered by status, kind, repo and |
get_v1_tracker_projects_key_issues_num | GET /v1/tracker/projects/{key}/issues/{num} | 2 | GetIssue returns one issue of one tracker project by its per-project number — title, description, st |
patch_v1_tracker_projects_key | PATCH /v1/tracker/projects/{key} | 3 | UpdateProject renames a tracker project or rewrites its description, and returns the updated project |
patch_v1_tracker_projects_key_issues_num | PATCH /v1/tracker/projects/{key}/issues/{num} | 8 | UpdateIssue edits one issue in place and returns it — retitle it, rewrite its body, move it between |
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?