Cloud MCPdestinations
destinations
4 MCP tools on the Hanzo cloud door that call the destinations API.
The 4 tools tools/list names for destinations. Each dispatches to an operation in the destinations API reference.
| Tool | Route | Arguments | Description |
|---|---|---|---|
delete_v1_destinations_platform | DELETE /v1/destinations/{platform} | 1 | Forgets a destination for the caller's org: every credential held in KMS, then the stored config. |
get_v1_destinations | GET /v1/destinations | 0 | Reports every destination this deployment can forward to, each with the caller org's connection stat |
get_v1_destinations_platform | GET /v1/destinations/{platform} | 1 | Reports one destination's card for the caller's org — its config fields, its connection state, and w |
post_v1_destinations_platform_test | POST /v1/destinations/{platform}/test | 1 | Sends ONE synthetic pageview through the connected destination end to end and reports what the platf |
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?