MCP Server <--> n8n
This page explains how to use the ScraperAPI MCP (Model Context Protocol) Server inside your n8n workflows.
Note: this integration uses the same community node as the basic ScraperAPI API resource and therefore requires a self‑hosted n8n instance. If you haven't installed the node yet or configured your API key, follow the installation instructions on the n8n Integration page.
How it works
MCP Workflow
Add an MCP Client node to your workflow. This node uses n8n's MCP Client Tool to send requests to the ScraperAPI MCP server.
Configure the client node:
Endpoint: https://mcp.scraperapi.com/mcp
Server Transport: HTTP Streamable
Authentication: Bearer Auth
Credential for Bearer Auth: Enter your ScraperAPI API key as the Bearer Token.
Tools to include: Select a tool from the list (scrape, google_search, google_shopping, etc.)
Configure any optional parameters (see available Parameters).

Google Shopping Scraping Workflow
This example uses the ScraperAPI MCP Server inside n8n to scrape Google Shopping results, transform the output, and email the final results automatically.
Add an MCP Client node - configure it to connect to the ScraperAPI MCP Server.
During configuration, choose the google_shopping tool from the dropdown list.
Add an Edit Fields node to clean up the JSON response.
Add a Convert to File node to export the results to a JSON file.
Add a Send an Email node to send the final JSON file as an email attachment.
The example below shows a complete workflow that scrapes Google Shopping results, formats them and sends them over an email.

Last updated

