mcp-server-preferred-over-cli-acp-for-researchclaw-invocation
ORACLE Hermes should invoke AutoResearchClaw via an MCP server wrapper (not CLI or ACP protocol) because: MCP gives structured typed tool responses instead of stdout parsing, allows granular per-stage control, fits the existing ‘everything is MCP’ architecture, and aligns with the Bible v18.1 MCP server development framework. ACP was designed for LLM delegation not orchestration and provides less stage-level control. CLI is crude and requires parsing unstructured output. Register as session-based (not permanent) to keep tool budget lean.
Related
- autoresearchclaw-integrated-as-mcp-server-not-cli-or-acp
- 2026-04-04-oracle-001-self-architecture-analysis
- docker
- clawteam-openclaw-multi-agent-swarm-evaluation
- oracle-has-zero-citation-integrity-gap
- autoresearchclaw-acp-protocol-uses-claude-as-llm-backend
- oracle-researchclaw-mcp-server-over-cli-or-acp
- researchclaw-mcp-invocation-over-cli-or-acp
- mcp-server-preferred-over-cli-and-acp-for-oracle-tool-integr