Cloud MCPflow
flow
8 MCP tools on the Hanzo cloud door that call the flow API.
The 8 tools tools/list names for flow. Each dispatches to an operation in the flow API reference.
| Tool | Route | Arguments | Description |
|---|---|---|---|
delete_v1_flow_workflows_workflow | DELETE /v1/flow/workflows/{workflow} | 1 | WorkflowDelete deletes one of the caller's workflows and its runs. |
get_v1_flow_runs | GET /v1/flow/runs | 1 | Runs reads one workflow's recorded runs: every component build with its result, keyed by component. |
get_v1_flow_status | GET /v1/flow/status | 0 | Status reports whether the flow service is reachable and which version it runs. |
get_v1_flow_workflows | GET /v1/flow/workflows | 2 | Workflows lists the caller's workflows, paged. |
get_v1_flow_workflows_workflow | GET /v1/flow/workflows/{workflow} | 1 | Workflow reads one of the caller's workflows — the full record, graph included. |
patch_v1_flow_workflows_workflow | PATCH /v1/flow/workflows/{workflow} | 5 | WorkflowUpdate patches one of the caller's workflows: name, description, graph, or the locked flag — |
post_v1_flow_runs | POST /v1/flow/runs | 4 | Run executes one of the caller's workflows synchronously: the graph runs in the flow service and the |
post_v1_flow_workflows | POST /v1/flow/workflows | 3 | WorkflowCreate creates a workflow in the caller's org. |
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?