mcp-server-preferred-over-cli-acp-for-native-oracle-integration
Three invocation patterns were evaluated for wiring AutoResearchClaw into ORACLE Hermes: MCP Server (structured tools), CLI (docker exec shell-out), and ACP (agent client protocol). MCP Server was chosen because it provides typed JSON responses (not stdout), enables granular stage control (start/status/resume/gate-approve as separate tools), and matches the entire Oracle stack’s ‘everything is MCP’ architecture. ACP was designed for LLM delegation (ResearchClaw controlling the LLM), not for orchestration control (ORACLE controlling ResearchClaw).