acp-protocol-wrong-pattern-for-oracle-orchestration

AutoResearchClaw’s ACP (Agent Client Protocol) is designed for LLM call delegation (ResearchClaw delegates its LLM calls through Claude Code), not for orchestration control. Using ACP would give ORACLE Hermes less granular control over individual pipeline stages compared to MCP. MCP server is the correct integration pattern when the orchestrator needs to start, pause, approve gates, resume, and retrieve typed artifacts from ResearchClaw. ACP remains useful if the goal is purely to route LLM inference through Claude, not to orchestrate the pipeline.

Related

• autoresearchclaw-acp-protocol-uses-claude-as-llm-backend
• docker
• oracle
• oracle-researchclaw-mcp-server-over-cli-or-acp
• 2026-04-04-oracle-001-self-architecture-analysis
• researchclaw-mcp-server-over-acp-for-oracle-orchestration
• acp-protocol-designed-for-llm-delegation-not-orchestration
• autoresearchclaw-acp-protocol-delegates-llm-calls-through-cl
• autoresearchclaw-acp-protocol-claude-code-native-integration
• autoresearchclaw-native-acp-supports-claude-as-backend
• autoresearchclaw-acp-protocol-for-claude-code-integration
• autoresearchclaw-acp-native-support-for-claude-code
• autoresearchclaw-acp-protocol-supports-claude-code
• acp-for-llm-delegation-not-orchestration-mcp-for-control