Cloud MCPauto
auto
11 MCP tools on the Hanzo cloud door that call the auto API.
The 11 tools tools/list names for auto. Each dispatches to an operation in the auto API reference.
| Tool | Route | Arguments | Description |
|---|---|---|---|
delete_v1_auto_flows_flow | DELETE /v1/auto/flows/{flow} | 1 | FlowDelete deletes one of the caller's flows. |
get_v1_auto_flows | GET /v1/auto/flows | 0 | Flows lists the caller's flows, newest first. |
get_v1_auto_flows_flow | GET /v1/auto/flows/{flow} | 1 | Flow reads one of the caller's flows — the full record, graph included. |
get_v1_auto_pieces | GET /v1/auto/pieces | 0 | Pieces lists the product's built-in piece catalog: the trigger and action types a flow's nodes can u |
get_v1_auto_runs | GET /v1/auto/runs | 1 | Runs lists the caller's run records, newest first — optionally one flow's. |
get_v1_auto_runs_run | GET /v1/auto/runs/{run} | 1 | Run reads one run record: status, input, output (each executed node's result keyed by node id once c |
get_v1_auto_status | GET /v1/auto/status | 0 | Status reports whether the auto service is reachable — its own health endpoint as an honest lens for |
patch_v1_auto_flows_flow | PATCH /v1/auto/flows/{flow} | 3 | FlowUpdate patches one of the caller's flows: the name, the graph, or both — only the stated fields |
post_v1_auto_flows | POST /v1/auto/flows | 2 | FlowCreate creates a flow in the caller's org. |
post_v1_auto_flows_flow_publish | POST /v1/auto/flows/{flow}/publish | 1 | Publish snapshots the flow's current graph as its next immutable version and arms the flow's trigger |
post_v1_auto_runs | POST /v1/auto/runs | 2 | Start begins one asynchronous run of a flow: the product dispatches the graph to its durable executi |
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?