> For the complete documentation index, see [llms.txt](https://docs.scraperapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scraperapi.com/integrations/automation-and-workflow-integrations/n8n-integration/mcp-server-less-than-greater-than-n8n.md).

# MCP Server <--> n8n

This page explains how to use the ScraperAPI MCP (Model Context Protocol) Server inside your **n8n workflows**.

#### How it works <a href="#how-it-works" id="how-it-works"></a>

**MCP Workflow**

1. **Add an MCP Client node** to your workflow. This node uses n8n's MCP Client Tool to send requests to the ScraperAPI MCP server.
2. **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.)

3. Configure any optional parameters (see available [Parameters](https://github.com/scraperapi/n8n-nodes-scraperapi-official/blob/master/README.md#parameters)).

<figure><img src="https://921583510-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXJv4kz1e8RdAq9HrFwyo%2Fuploads%2Ffh7NZVhqEJoHX0X14A8T%2FMCP-n8n.gif?alt=media&amp;token=940a8360-cf77-4a78-825f-f974f9c031c6" alt=""><figcaption></figcaption></figure>

#### 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](#how-it-works) 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.

<figure><img src="https://921583510-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXJv4kz1e8RdAq9HrFwyo%2Fuploads%2FtSZmbUdZO3ZZhPz1eDSd%2FMCP-workflow.gif?alt=media&amp;token=f21c2ae4-0f9d-4a1c-9890-3927116cb7ae" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scraperapi.com/integrations/automation-and-workflow-integrations/n8n-integration/mcp-server-less-than-greater-than-n8n.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.