> 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/resources/release-notes/november-2025/scraperapi-n8n-integration-with-mcp-connectivity.md).

# ScraperAPI n8n integration with MCP connectivity

### Getting started

* **Easy setup:**

  * Install the ScraperAPI node from the n8n Community Nodes library ([Docs](https://docs.scraperapi.com/integrations/automation-and-workflow-integrations/n8n-integration.md)).
  * Connect it to your ScraperAPI account using your API key.

  *Note*

  * *Until n8n approves the node, enable Community Nodes in n8n settings to install.*
* **Simple requests:** Use the **API** resource to make GET requests to any URL.
* **Core parameters:**
  * **Required:** `URL`, `API Key`
  * **Optional:** `Country Code`, `Device Type`, `Render`, `Premium`, `Ultra Premium`
* **Flexible scraping:** Choose whether to render JavaScript, target a specific country, or use premium proxies, all from the node settings.
* **Improved usability:** Clearer parameter descriptions, cleaner layout, and smarter defaults make setup effortless.
* A hosted **MCP endpoint** ([mcp.scraperapi.com](http://mcp.scraperapi.com/)) will allow you to connect to ScraperAPI through an MCP server for broader AI and automation integrations beyond n8n.

Visit the docs to learn how to set it up:

<a href="https://docs.scraperapi.com/integrations/automation-and-workflow-integrations/n8n-integration.md" class="button primary" data-icon="code-branch">ScraperAPI n8n node documentation</a>


---

# 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/resources/release-notes/november-2025/scraperapi-n8n-integration-with-mcp-connectivity.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.
