n8n
Connect n8n workflows to the CoreClaw MCP Server so your automation pipelines can discover CoreClaw workers, run them, monitor runs, and retrieve results as part of a workflow.
Prerequisites
Section titled “Prerequisites”- An n8n instance
- A CoreClaw account with an API key from Console -> Settings -> API & Integrations
Configuration
Section titled “Configuration”n8n supports MCP via Streamable HTTP transport through an MCP Client Tool node.
Step 1: Add an MCP Client Tool Node
Section titled “Step 1: Add an MCP Client Tool Node”- In your n8n workflow, add an MCP Client Tool node.
- Set the transport to Streamable HTTP.
Step 2: Configure the MCP Server
Section titled “Step 2: Configure the MCP Server”Fill in the node settings:
- URL:
https://mcp.coreclaw.com/mcp - Headers:
api-key:YOUR_CORECLAW_API_KEY
Replace YOUR_CORECLAW_API_KEY with your actual CoreClaw API key.
Step 3: Connect to Your Workflow
Section titled “Step 3: Connect to Your Workflow”- Connect the MCP Client Tool node to an AI Agent node.
- Connect the AI Agent node to downstream processing nodes.
Verify the Connection
Section titled “Verify the Connection”- Execute the workflow.
- The AI Agent should be able to call CoreClaw tools such as
list_store_workers.
Example Workflow
Section titled “Example Workflow”[Trigger] -> [AI Agent] -> [MCP Client Tool: CoreClaw] -> [Process Results] -> [Save to Database]Example prompt for the AI Agent:
Find an Amazon product worker on CoreClaw, inspect its input schema, run it with this product URL, and return the product title, price, and rating.
The AI Agent should:
- Call
list_store_workersto find an Amazon worker. - Call
get_worker_input_schemato inspect required inputs. - Call
run_workerwithinput_json. - Poll
get_worker_rununtil the run completes. - Call
list_worker_run_resultsorexport_worker_run_resultsto retrieve data.
Troubleshooting
Section titled “Troubleshooting”Tools not appearing
Section titled “Tools not appearing”- Verify the MCP Client Tool URL is exactly
https://mcp.coreclaw.com/mcp. - Ensure the
api-keyheader is set. - Check n8n execution logs for connection errors.
Authentication errors
Section titled “Authentication errors”- Ensure the
api-keyheader value matches your CoreClaw API key exactly. - Verify your key is active in the Console.
Next Steps
Section titled “Next Steps”- Back to MCP overview
- CoreClaw API documentation
- n8n community node — a dedicated CoreClaw node for n8n (no AI agent required)
- coreclaw-n8n-workflows — production-ready n8n workflow templates