Flow MCP Node

warning

This node is in beta and may not be fully tested or documented. Use with caution.

The Flow MCP surface is split into three routes with different scopes:

• botdojo://flow/mcp: global discovery and cloning surface
• botdojo://core/flow/{flow_id}/TOOLS.md: flow-scoped management surface for one exact flow
• botdojo://flow/{flow_id}/editor/{branch}/mcp: branch-scoped editor surface

Use the global botdojo://flow/mcp route to find flows, inspect public templates, clone a flow, or open an editor. Once you know the target flow id, switch to botdojo://core/flow/{flow_id}/TOOLS.md for branch creation, export, sync, running, and publish operations. This avoids accidentally mutating a different flow from the generic/global tool palette.

Recommended workflow

1. Discover or clone via botdojo://flow/mcp.
2. Switch immediately to botdojo://core/flow/{flow_id}/TOOLS.md.
3. Create a working branch with newBranch.
4. Export with export or exportToWorkspace and verify the returned resolvedSource metadata before editing.
5. For model-context flows, call listModelContextTools first, then testModelContext with the specific tool parameters.
6. Publish when the branch is ready.

Branch naming

Persisted feature branches use the canonical flow_mcp_* alias format. The core flow-management tools accept both the raw branch name such as sales-crm-tools-build and the canonical alias such as flow_mcp_sales-crm-tools-build, and they return both display and canonical forms in their responses.

Running model-context flows

Use listModelContextTools to inspect the available tools, descriptions, and parameter schemas for a branch or release before calling testModelContext. This is the safest way to exercise parameterized MCP tools without guessing the expected input shape.

Output

Label	Property	Type	Description	Default Value
Model Context	modelContext	botdojo/interface/model_context	Flow management model context	null