MCP client capability for archie agents #857

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

Sam wants archie to be able to connect to MCP servers as a client (consume external tools/data sources from within agent workflows), analogous to how Claude Code itself uses MCP. Design and implement as a Layer 2 core plugin or agent-loop tool integration, depending on findings from wiring the plugin loader (archie-core-abg.2). Per docs/prds/multi-agent-collaboration.md phase E.

Acceptance Criteria

An agent workflow stage can call a tool exposed by a configured external MCP server, with the connection configured via daemon config or a core plugin.

Close reason

Closed on GitHub; syncing bead state


Imported from beads archie-core-1786637498363-325-5853a9dd · GitHub #346 · type task · priority P2 · created 2026-08-08 · closed 2026-09-26

Sam wants archie to be able to connect to MCP servers as a client (consume external tools/data sources from within agent workflows), analogous to how Claude Code itself uses MCP. Design and implement as a Layer 2 core plugin or agent-loop tool integration, depending on findings from wiring the plugin loader (archie-core-abg.2). Per docs/prds/multi-agent-collaboration.md phase E. ### Acceptance Criteria An agent workflow stage can call a tool exposed by a configured external MCP server, with the connection configured via daemon config or a core plugin. ### Close reason Closed on GitHub; syncing bead state --- _Imported from beads `archie-core-1786637498363-325-5853a9dd` · GitHub #346 · type task · priority P2 · created 2026-08-08 · closed 2026-09-26_
sam added the mediumtask labels 2026-10-27 13:38:02 +00:00
sam self-assigned this 2026-10-27 13:38:02 +00:00
sam closed this issue 2026-10-27 13:38:02 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#857