autoresearchclaw-mcp-server-pattern-over-cli-or-acp
AutoResearchClaw integration was designed as a dedicated MCP server (~11 tools) rather than CLI invocation or ACP protocol. CLI is rejected because it returns unstructured stdout with no typed responses. ACP is rejected because it delegates LLM calls rather than providing orchestration control — unsuitable when you need granular stage-level control over a 23-stage pipeline. MCP server exposes tools like researchclaw_run, researchclaw_status, researchclaw_approve_gate, and standalone researchclaw_verify_citations and researchclaw_search_literature for use outside paper pipelines.