oracle-researchclaw-mcp-server-over-cli-or-acp

AutoResearchClaw integration chose MCP Server wrapping over CLI invocation or ACP protocol. CLI returns unstructured stdout, making 23-stage granular control impossible. ACP is designed for LLM call delegation (ResearchClaw delegates its own LLM calls outward), not for an orchestrator to invoke ResearchClaw — a subtle but critical distinction. MCP Server gives ORACLE Hermes structured JSON tool responses and per-stage control matching the rest of the oracle-network topology.

Related

• mcp-server-preferred-over-cli-acp-for-researchclaw-invocatio
• autoresearchclaw-integrated-as-mcp-server-not-cli-or-acp
• autoresearchclaw-integration-architecture-decisions
• oracle
• docker
• researchclaw-gate-stages-need-dedicated-mcp-tools
• acp-protocol-wrong-pattern-for-oracle-orchestration
• researchclaw-mcp-server-over-acp-for-oracle-orchestration
• mcp-server-preferred-over-cli-acp-for-oracle-integration
• acp-protocol-designed-for-llm-delegation-not-orchestration
• autoresearchclaw-mcp-server-beats-cli-and-acp-for-oracle-int
• researchclaw-mcp-server-chosen-over-cli-and-acp
• hostinger-mcp-dns-deletion-tool-schema-bug-filters-missing