NF-9: MCP nodes (v2) #330

New issue

Closed

opened 2026-04-24 11:29:51 +00:00 by code-lead · 0 comments

code-lead commented

2026-04-24 11:29:51 +00:00

Collaborator

As an operator, I want to call any registered MCP tool (mcp__forge__*, mcp__penpot__*, custom servers) from a flow so that I can compose micro-automations without dispatching a full Claude agent.

Acceptance criteria

Registry

Each registered MCP server's tools schema is introspected at service startup.
For every tool, a mcp.<server>.<tool> node is synthesised with inputs matching the tool's declared JSON schema.
Custom MCP servers added after startup are picked up on the next reload.

Execution

Node invocation proxies through the same MCP client the agent-runner uses.
Errors returned by the server surface on the node's err output port (not thrown).
Tool calls count against the per-flow rate-limit budget.

Out of scope

Letting agents invoke a flow via MCP (reverse direction).

References

Spec: specs/node-flows.md § Stories § NF-9.
Depends on NF-7 (#328).

As an operator, I want to call any registered MCP tool (`mcp__forge__*`, `mcp__penpot__*`, custom servers) from a flow so that I can compose micro-automations without dispatching a full Claude agent. ## Acceptance criteria ### Registry - [ ] Each registered MCP server's `tools` schema is introspected at service startup. - [ ] For every tool, a `mcp.<server>.<tool>` node is synthesised with inputs matching the tool's declared JSON schema. - [ ] Custom MCP servers added after startup are picked up on the next reload. ### Execution - [ ] Node invocation proxies through the same MCP client the agent-runner uses. - [ ] Errors returned by the server surface on the node's `err` output port (not thrown). - [ ] Tool calls count against the per-flow rate-limit budget. ## Out of scope - Letting agents invoke a flow via MCP (reverse direction). ## References - Spec: [`specs/node-flows.md`](../src/branch/main/specs/node-flows.md) § Stories § NF-9. - Depends on NF-7 (#328).

code-lead added this to the M21 — Node Flows milestone

2026-04-24 11:29:51 +00:00

code-lead added the

area:agents

type:user-story

labels

2026-04-24 11:29:51 +00:00

code-lead referenced this issue

2026-04-24 11:29:57 +00:00

M21 Tracking — Node Flows #340

code-lead was assigned by claude-desktop

2026-04-26 18:56:57 +00:00