Scrapeunblocker MCP Server

Fetch any web page's HTML or AI-parsed JSON through the ScrapeUnblocker anti-bot API.

Local serverstdio

What is the Scrapeunblocker MCP server?

Scrapeunblocker MCP server exists for a simple reason — assistants are far more useful when they can act on Scrapeunblocker directly instead of describing what you should do. Fetch any web page's HTML or AI-parsed JSON through the ScrapeUnblocker anti-bot API.

What you get

You bring your own API key. Nothing is shared or proxied through us.

What the assistant can call

Once Scrapeunblocker is connected, these are the calls the assistant has available:

  • fetch_html — Fetch the fully rendered HTML of a URL
  • fetch_parsed — Fetch a page and return AI-parsed structured JSON
  • google_search — Run a Google search and return organic results as JSON

Configuration and credentials

You will need one environment variable: SCRAPEUNBLOCKER_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Installation goes through your MCP client rather than a global install: point it at scrapeunblocker-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Scrapeunblocker's toolset — fetch_html, fetch_parsed, google_search — is a fair guide to whether it matches your workflow. It is maintained by com.scrapeunblocker; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the scrapeunblocker mcp server does with a few real requests.

Available tools

ToolWhat it does
fetch_htmlFetch the fully rendered HTML of a URL.
fetch_parsedFetch a page and return AI-parsed structured JSON.
google_searchRun a Google search and return organic results as JSON.

How to install the Scrapeunblocker MCP server

{
  "mcpServers": {
    "scrapeunblocker": {
      "command": "npx",
      "args": ["-y", "scrapeunblocker-mcp"],
      "env": {
        "SCRAPEUNBLOCKER_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
SCRAPEUNBLOCKER_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Scrapeunblocker to fetch html.
  • Use Scrapeunblocker to fetch parsed.
  • Use Scrapeunblocker to google search.

Frequently asked questions

It connects Scrapeunblocker to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (fetch_html, fetch_parsed, google_search) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Scrapeunblocker directly.