get_workflow
Reports an integration's build lifecycle status and next steps. Set retrofit=true to derive state from an existing assembly when no aidlc-docs exists.
Instructions
Reports where an integration stands in its build lifecycle, and what to do next.
CALL THIS FIRST when picking up an integration you did not just scaffold — it answers "what is done, what is still a stub, and what should I do now?" without reading the XML.
THE LIFECYCLE (this MCP covers the first two phases):
INCEPTION — plan_integration gathers the design and scaffolds the assembly + diagram, decomposed into sub-flows (the units of work).
CONSTRUCTION — build ONE unit at a time: update_sub_flow to fill it in, then validate_assembly before moving to the next.
OPERATIONS — deploy, tenant config, launch. NOT automated here: this server is local-only and never touches a tenant. The handoff checklist lives in aidlc-docs/plan.md.
State is read from /aidlc-docs/state.json, written by plan_integration and kept current by update_sub_flow and validate_assembly.
If a project has no aidlc-docs/ (it predates the convention, or was built by hand), call again with retrofit=true to derive one from the existing assembly. Retrofit records only what the assembly proves — sub-flows and which are still TODO stubs. It marks the design brief as unrecorded rather than inventing one.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"project_name": "<project_name>"
},
"name": "get_workflow"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| retrofit | No | Generate aidlc-docs/ for a project that has none, by reading its existing assembly.xml | |
| project_name | Yes | Project name, e.g. "INT999_Employee_Sync" |