researchclaw-mcp-server-over-acp-for-oracle-orchestration

AutoResearchClaw supports both ACP (Agent Client Protocol) and MCP server integration. ACP is designed for LLM call delegation, not orchestration — it gives less control over individual pipeline stages and doesn’t return typed tool responses. MCP server is the correct integration pattern for ORACLE Hermes because it provides structured JSON responses, granular stage control (23 stages, 3 gate stages), and fits the existing oracle stack’s all-MCP architecture.

Related

• oracle
• acp-protocol-wrong-pattern-for-oracle-orchestration
• hermes
• docker
• oracle-researchclaw-mcp-server-over-cli-or-acp
• 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-invocation-over-cli-or-acp
• mcp-over-cli-over-acp-for-tool-integration
• researchclaw-mcp-server-chosen-over-cli-and-acp
• autoresearchclaw-native-acp-supports-claude-as-backend
• researchclaw-mcp-server-over-cli-or-acp
• acp-for-llm-delegation-not-orchestration-mcp-for-control
• researchclaw-mcp-server-preferred-over-cli-or-acp-invocation