Instead of local flows, you drive recurring processes through keywords that the MCP server resolves into multi-step workflows.
How it works
resolve-keyword({ keyword: "KIDOKU" })returns aworkflow_id.get_workflow_step({ workflow_id })returns step 1.- Implement each step and submit it via
submit_step_result(...). - The next step arrives automatically — until
workflow_complete.
Available keywords
KIDOKU FULL— documentation sequence (9 steps)CONTENT CREATION— session insight as a briefing row (5 steps)SUMMARY— status + recommendation in one blockDEPLOYMENT— check branch deploy-ready + push
Single source of truth
Steps and output_schema always come from the MCP server (gold DB) — never from a local file.