trustgraph/ts/entrypoints/mcp-tool.mjs

import("@effect/platform-bun/BunRuntime")
  .then(async (BunRuntime) => {
    const m = await import("../packages/flow/dist/agent/mcp-tool/service.js");
    BunRuntime.runMain(m.program);
  })
  .catch((err) => {
    console.error(err);
    process.exit(1);
  });
saving 2026-05-12 08:06:58 -05:00			`import("@effect/platform-bun/BunRuntime")`
			`.then(async (BunRuntime) => {`
			`const m = await import("../packages/flow/dist/agent/mcp-tool/service.js");`
			`BunRuntime.runMain(m.program);`
			`})`
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> 2026-05-01 22:16:37 -05:00			`.catch((err) => {`
			`console.error(err);`
			`process.exit(1);`
			`});`