autoresearchclaw-acp-protocol-for-claude-code-integration

AutoResearchClaw natively supports ACP (Agent Client Protocol) with llm.acp.agent: claude configuration, designed specifically for delegation of LLM calls through Claude Code. However, ACP is optimized for LLM delegation, not orchestration — it gives less granular control over individual pipeline stages compared to MCP Server integration. ACP is appropriate when ResearchClaw drives the workflow; MCP Server is appropriate when ORACLE Hermes needs to orchestrate ResearchClaw as a sub-system.

Related

• acp-protocol-wrong-pattern-for-oracle-orchestration
• autoresearchclaw-native-acp-supports-claude-as-backend
• autoresearchclaw-acp-protocol-uses-claude-as-llm-backend
• autoresearchclaw-acp-protocol-claude-code-native-integration
• mcp-over-cli-over-acp-for-tool-integration
• autoresearchclaw-acp-native-support-for-claude-code
• autoresearchclaw-acp-protocol-supports-claude-code