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

docs: mark wf-mcp as legacy entrypoint

Browse Source
This commit is contained in:
lda
2026-06-06 15:14:34 +07:00 Verified
parent fa37f57c00
commit d4939ccce4
2 changed files with 13 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/current_roadmap.md
+5
View File
@@ -254,6 +254,11 @@ implementation state.
as workflow capabilities. The current `wf_mcp` package still contains both
roles plus compatibility entrypoints; new server/transport work should avoid
depending on that combined facade.
The `wf-mcp` script is now a legacy/special-purpose MCP entrypoint, not the
preferred durable workflow server. New product paths should target
`wf-rpc-server` plus neutral `wf_config`/`wf_server` composition, then keep
shrinking `wf_mcp` toward upstream MCP source utilities, MCP transport
adapters, proxy/debug compatibility, and old entrypoint shims.
MCP UI/App metadata is source metadata only for now. Do not advertise widget
or MCP Apps support through workflow transports until a dedicated MCP
frontend transport owns iframe hosting, `ui://` resources, app-only tool
docs/project_map.md
+8 -4
View File
@@ -8,7 +8,7 @@ This repository has three main packages plus examples and tests.
| --- | --- | --- |
| `wf_core` | Deterministic workflow kernel: models, validation, runtime, run state, traces, interrupts, foreach, and path/state operations. | Runtime users, `wf_authoring`, workflow adapters. |
| `wf_authoring` | Ergonomic workflow construction: `@node`, `NodeSpec`, builder DSL, conditions, path helpers, reusable ops, subgraph nodes. | Humans, tests, future LLM workflow builders. |
| `wf_mcp` | MCP integration: SDK adapters, broker/proxy runtime, storage, config control, and workflow wrappers for discovered tools. | MCP-facing CLI/server code and future UI/control surfaces. |
| `wf_mcp` | MCP-specific integration: SDK adapters, upstream MCP runtime, proxy/debug compatibility, legacy broker entrypoints, and wrappers for discovered MCP tools. | MCP source/provider code, MCP transport work, and compatibility callers. Durable workflow server paths should prefer `wf_server` plus transport packages. |
## Important Entry Points
@@ -22,8 +22,9 @@ This repository has three main packages plus examples and tests.
- `wf_authoring.node`: typed Python function to `NodeSpec`.
- [`docs/wf_authoring_control_flow.md`](wf_authoring_control_flow.md): when to
use `branch`, `handle`, `match`, `when`, and `choose`.
- `wf_mcp`: public MCP facade.
- `wf-mcp`: CLI script from `pyproject.toml`.
- `wf_mcp`: MCP-specific facade and compatibility package.
- `wf-mcp`: legacy/special-purpose MCP script from `pyproject.toml`.
- `wf-rpc-server`: preferred durable workflow server script for CLI/API clients.
- `wf_mcp.broker.WfMcpService.get_catalog()`: backend MCP catalog snapshots.
- `wf_mcp.broker.WfMcpService.get_planner_catalog()`: backend snapshots plus
broker-local workflow sources such as `wf.std` and `wf.mcp`.
@@ -69,7 +70,10 @@ need local environment configuration.
- Add new graph/model syntax in `wf_core.models`, then validate it in
`wf_core.validation`.
- Add author convenience helpers in `wf_authoring`, not `wf_core`.
- Add MCP transport/proxy/config behavior in `wf_mcp` concern packages.
- Add upstream MCP source/provider behavior in `wf_mcp` concern packages until a
dedicated `wf_sources_mcp` split exists.
- Add durable workflow server behavior in `wf_server` or transport packages, not
the legacy `wf-mcp` entrypoint.
- Add broker-local workflow utilities as `WfMcpService` spec sources, not as
fake MCP connections.
- Add runnable examples in `examples`.