ScrapeUnblocker/scrapeunblocker-mcp

A Model Context Protocol server that lets
Claude (and any other MCP client) fetch **any web page's HTML** - or run one of
100+ ready-made **site plugins** that return structured JSON - through the
ScrapeUnblocker scraping API, bypassing anti-bot
protection (Cloudflare, DataDome, PerimeterX, Akamai, Shape).
You bring your **own** API key. Nothing is shared or proxied through us.
Tools
| Tool | What it does |
|------|--------------|
| fetch_html | Fetch the fully rendered HTML of a URL (optionally after running interactive browser steps). |
| list_elements | List a page's notable elements with a ready-to-use selector for each (selector discovery). |
| fetch_parsed | Fetch a page and return AI-parsed structured JSON. |
| google_search | Run a Google search and return organic results as JSON. |
| list_plugins | List the ready-made site plugins (100+: Amazon, Walmart, Zillow, Booking.com, Indeed, Google Trends, YouTube, App Store, Ahrefs, ...) with their parameters. Free - it calls nothing. |
| run_plugin | Run one site plugin and return its structured JSON. |
| amazon_search, amazon_product, amazon_reviews, walmart_search, ebay_search, google_shopping, google_local, maps_place_details, google_images, youtube_search, youtube_transcript, zillow_search, indeed_jobs, trustpilot_reviews, booking_hotels | The most-used site plugins as tools of their own, each with its parameters in the tool schema - one call, no list_plugins lookup. Same JSON as run_plugin. |
Site plugins (structured JSON for known sites)
For many popular sites there is a plugin that returns the data already
parsed - a Target search, a Zillow listing search, an app's App Store reviews,
Google Trends for a few keywords. The model calls list_plugins (optionally
with search: "zillow" or a category) to find the plugin and its
parameters, then run_plugin with name and params (the most-used plugins, listed in
the table above, can also be called directly as their own tools):
Every plugin and parameter is documented on the
plugin pages.
Each run is billed like an API request.
Browser steps (interact, then capture)
Some pages only reveal what you need after you interact with them - accept a
cookie banner, click a tab, type into a search box and submit, or scroll to
trigger lazy loading. Pass an optional steps array to fetch_html and those
actions run in a **real browser**, in order, after the page loads; the resulting
HTML is then returned.
Available actions:
| Action | Fields |
|--------|--------|
| wait_for | selector, selector_type? (css/xPath/className/tagName), timeout_ms? |
| wait_for_text | value, timeout_ms? |
| wait | value (ms) |
| click | selector, selector_type?, timeout_ms? |
| type | selector, selector_type?, value, clear?, timeout_ms? (typed human-like) |
| select | selector, selector_type?, value, timeout_ms? |
| press_key | value (Enter, Tab, Escape, Backspace, Delete, Space, Arrow*, Home, End, PageUp, PageDown) |
| scroll | value ("bottom" or a pixel offset) |
Steps are **not idempotent** - they run once per call. If a step fails,