lda.chat/lda-wf
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: add mcp backed workflow server

Browse Source
This commit is contained in:
lda
2026-06-04 23:17:02 +07:00 Unverified
parent 0d34174a84
commit 3b8a1fe6dc
10 changed files with 862 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/superpowers/specs/2026-06-03-long-lived-workflow-api-boundary.md
+10 -6
View File
@@ -2,12 +2,13 @@
Date: 2026-06-03
Status: Slices 1-3 implemented. `wf_server` provides
`build_local_static_workflow_server`, `wf_transport_rpc_http` provides JSON-RPC
methods and client support, `wf_cli` has target-aware context, and `wf_config`
owns neutral config models. WebSocket transport, source providers, auth,
streaming/progress, database backend, and live MCP source management remain
future work.
Status: Slices 1-4 implemented. `wf_server` provides
`build_local_static_workflow_server`; `wf_mcp.broker.server` can adapt MCP
broker config/services into the neutral `WorkflowServer`; `wf_transport_rpc_http`
provides JSON-RPC methods and client support; `wf_cli` has target-aware context;
and `wf_config` owns neutral config models. WebSocket transport, auth,
streaming/progress, database backend, and live source hot reload remain future
work.
Related:
@@ -105,6 +106,9 @@ Implementation status:
- Slice 3 complete: `wf_cli` supports target-aware context with `--local`,
`--url`, and `--timeout` overrides, and works with remote RPC targets for
capability and run commands.
- Slice 4 complete: `wf_mcp.broker.server.build_workflow_server_from_config()`
returns a neutral `WorkflowServer` backed by MCP broker runtime services,
including source registry admin and platform admin surfaces.
First slice should not include: