feat(mcp-tool): wire McpToolService into deploy stack

Three pieces, all required for an end-to-end MCP tool call:

* McpToolService used generic spec names "request"/"response" instead of
  "mcp-tool-request"/"mcp-tool-response", so RequestResponseSpec's
  flow-config topic lookup never matched and consumers bound to literal
  subjects nobody else publishes to.

* Add entrypoints/mcp-tool.mjs (mirrors agent/librarian entrypoints) so
  the service can be launched in the prebuilt trustgraph-ts image.

* Add a `mcp-tool` service block to deploy/docker-compose.yml.

With these three fixes plus a `mcp-tool-request`/`mcp-tool-response`
entry in each flow's topics map, the agent ReAct loop can now invoke
remote MCP tools (verified end-to-end against Brave Search and FireCrawl).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
elpresidank 2026-05-01 22:16:37 -05:00
parent 4c356cd24c
commit 6ac5446a76
3 changed files with 21 additions and 3 deletions

View file

@ -0,0 +1,6 @@
import("../packages/flow/dist/agent/mcp-tool/service.js")
.then((m) => m.McpToolService.launch("mcp-tool"))
.catch((err) => {
console.error(err);
process.exit(1);
});