researchclaw-mcp-long-running-tool-pattern

For long-running MCP tools like researchclaw_run (23-stage pipeline that can take hours), the tool returns immediately with a run_id and ORACLE Hermes polls status via researchclaw_status. Gate stages (5, 9, 20) pause the pipeline waiting for ORACLE Hermes to call researchclaw_approve_gate or researchclaw_reject_gate. This async + gate pattern is the correct MCP design for pipelines exceeding typical tool timeout windows.

Related

• autoresearchclaw-mcp-server-integration-pattern
• oracle
• autoresearchclaw-mcp-server-11-tools-interface-design
• researchclaw-gate-stages-need-dedicated-mcp-tools
• async-mcp-tool-pattern-for-long-running-pipelines
• autoresearchclaw-async-pipeline-pattern-run-id
• researchclaw-async-run-id-polling-pattern-for-long-pipelines
• mcp-async-pipeline-must-return-run-id-not-block
• researchclaw-mcp-async-pattern-run-id-polling