mirror of
https://github.com/trustgraph-ai/trustgraph.git
synced 2026-07-01 09:29:38 +02:00
6ac5446a76
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> |
||
|---|---|---|
| .. | ||
| data | ||
| deploy | ||
| entrypoints | ||
| packages | ||
| scripts | ||
| .dockerignore | ||
| .gitignore | ||
| bun.lock | ||
| Containerfile | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| tsconfig.base.json | ||
| tsconfig.json | ||
| turbo.json | ||