n8n
Connect n8n workflows to the CoreClaw MCP Server so your automation pipelines can search for scrapers, run them, and retrieve data as part of your workflow.
Prerequisites
Section titled “Prerequisites”- n8n instance (self-hosted or cloud)
- A CoreClaw account with an API key — get it from Console → Settings → API & Integrations
Configuration
Section titled “Configuration”n8n supports MCP via Streamable HTTP transport. You can configure it via the 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:scraper_api_YOUR_KEY_HERE
Replace scraper_api_YOUR_KEY_HERE 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 subsequent processing nodes
Verify the connection
Section titled “Verify the connection”- Execute the workflow
- The AI Agent should be able to call CoreClaw tools like
search_scrapers
Example workflow
Section titled “Example workflow”A typical n8n workflow with CoreClaw MCP:
[Trigger] → [AI Agent] → [MCP Client Tool: CoreClaw] → [Process Results] → [Save to Database]Example prompt for the AI Agent:
Search for an Amazon product scraper on CoreClaw, run it with this URL: https://www.amazon.com/dp/B0CHHSFMRL, and return the product title, price, and rating.
The AI Agent will automatically:
- Call
search_scrapersto find an Amazon scraper - Call
get_scraper_detailsto get the parameter schema - Call
run_scraperwith the URL - Poll
get_run_statusuntil completion - Call
get_run_resultsto retrieve the data
Troubleshooting
Section titled “Troubleshooting”Tools not appearing
Section titled “Tools not appearing”- Verify the MCP Client Tool node URL is correct
- Ensure the
api-keyheader is set - Check n8n 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