Cloud MCPsync
sync
6 MCP tools on the Hanzo cloud door that call the sync API.
The 6 tools tools/list names for sync. Each dispatches to an operation in the sync API reference.
| Tool | Route | Arguments | Description |
|---|---|---|---|
delete_v1_sync_id | DELETE /v1/sync/{id} | 1 | Delete removes one sync and tears down the outbound mirror it derived, answering 204. |
get_v1_sync | GET /v1/sync | 0 | List returns every sync link the caller's org has, each with its two endpoints, its direction and tr |
get_v1_sync_id | GET /v1/sync/{id} | 1 | Get returns one sync by id. It is org-scoped: an id belonging to another tenant is the same 404 an u |
patch_v1_sync_id | PATCH /v1/sync/{id} | 4 | Patch updates one sync's mutable policy — direction, trigger and actor — in place. |
post_v1_sync | POST /v1/sync | 7 | Create declares a sync between two endpoints and returns it. |
post_v1_sync_id_run | POST /v1/sync/{id}/run | 1 | Run reconciles one sync now — the manual re-sync, and the initial import for a link created without |
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?