Cloud MCPconnectors
connectors
8 MCP tools on the Hanzo cloud door that call the connectors API.
The 8 tools tools/list names for connectors. Each dispatches to an operation in the connectors API reference.
| Tool | Route | Arguments | Description |
|---|---|---|---|
delete_v1_connectors_id | DELETE /v1/connectors/{id} | 1 | Forgets a connector: every custodied secret, then the row. |
get_v1_connectors | GET /v1/connectors | 0 | Lists the caller's OWN connectors across every provider — the set hanzo connector ls prints. |
get_v1_connectors_id_token | GET /v1/connectors/{id}/token | 1 | Hands the custodied access token to its owner — the ONE place custody exits. |
get_v1_connectors_providers | GET /v1/connectors/providers | 0 | Lists the user-scoped provider cards — the catalog of what a user can connect, and how. |
post_v1_connectors_id_refresh | POST /v1/connectors/{id}/refresh | 1 | Forces a token rotation for a connected connector, ahead of the automatic rotation a token read woul |
post_v1_connectors_provider_credential | POST /v1/connectors/{provider}/credential | 5 | Is the direct intake path: a customer-held token/setup-token (Verify) or an externally obtained OAut |
post_v1_connectors_provider_device | POST /v1/connectors/{provider}/device | 2 | Begins a device sign-in and returns the code to show the user plus how to poll for completion. |
post_v1_connectors_provider_device_flow_poll | POST /v1/connectors/{provider}/device/{flow}/poll | 2 | Advances a device sign-in. Terminal outcomes are DATA, not errors (verifyConn {active:false} discipl |
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?