wire MCP per-server parallel-tool-calls flag into config and daemon startup #702

Closed
opened 2026-10-27 13:37:24 +00:00 by sam · 0 comments
Owner

Follow-up to archie-core-abg.17.20, which added mcp.Client.parallelToolCalls + WithParallelToolCalls(bool) at the client-API level (adversarially reviewed, race-clean). Nothing currently sets it: config.MCPServer (internal/config/config.go) has no field for it, and both NewClient call sites (cmd/archied/main.go:510's mcp.NewClient, and internal/tools/provider/mcp/provider.go:85's protocol.NewClient) construct clients without the option -- so the flag has zero effect in production as things stand today.

Acceptance Criteria

config.MCPServer gains a ParallelToolCalls bool field (default false, matching the client's safe-by-default); both NewClient call sites read it and pass mcp.WithParallelToolCalls(cfg value) accordingly; a config-driven test proves a server configured with parallel_tool_calls=true actually gets a parallel-opted Client.

Notes

Design: docs/prds/mcp-tool-completion.md#per-server-parallel-tool-calls-flag-177. Suggested council lens: lens-boundary.

Close reason

Landed: MCPServer.ParallelToolCalls is decoded, threaded to the MCP client (per-server mutex), passed by both construction paths, and carried through the control-plane tool-settings projection with a reflection-based parity guard.


Imported from beads archie-core-1786637494422-177-3ec91c84 · GitHub #198 · type task · priority P2 · created 2026-08-08 · closed 2026-09-21

Follow-up to archie-core-abg.17.20, which added mcp.Client.parallelToolCalls + WithParallelToolCalls(bool) at the client-API level (adversarially reviewed, race-clean). Nothing currently sets it: config.MCPServer (internal/config/config.go) has no field for it, and both NewClient call sites (cmd/archied/main.go:510's mcp.NewClient, and internal/tools/provider/mcp/provider.go:85's protocol.NewClient) construct clients without the option -- so the flag has zero effect in production as things stand today. ### Acceptance Criteria config.MCPServer gains a ParallelToolCalls bool field (default false, matching the client's safe-by-default); both NewClient call sites read it and pass mcp.WithParallelToolCalls(cfg value) accordingly; a config-driven test proves a server configured with parallel_tool_calls=true actually gets a parallel-opted Client. ### Notes Design: docs/prds/mcp-tool-completion.md#per-server-parallel-tool-calls-flag-177. Suggested council lens: lens-boundary. ### Close reason Landed: MCPServer.ParallelToolCalls is decoded, threaded to the MCP client (per-server mutex), passed by both construction paths, and carried through the control-plane tool-settings projection with a reflection-based parity guard. --- _Imported from beads `archie-core-1786637494422-177-3ec91c84` · GitHub #198 · type task · priority P2 · created 2026-08-08 · closed 2026-09-21_
sam added the mediumtask labels 2026-10-27 13:37:24 +00:00
sam self-assigned this 2026-10-27 13:37:24 +00:00
sam closed this issue 2026-10-27 13:37:24 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#702