MCP server for Scrapling web scraping workflows, including HTTP scraping, browser-backed dynamic fetching, stealth fetching, screenshots, persistent browser sessions, selectors, proxies, and prompt-injection sanitization.
Scrapling MCP can issue HTTP requests, launch browser-backed fetches, run stealth fetches, reuse persistent browser sessions, capture screenshots, and scrape multiple URLs concurrently., Stealth and anti-bot features can interact with Cloudflare Turnstile, interstitial pages, and other protection systems; use them only where scraping is permitted., Bulk tools, persistent sessions, proxies, browser impersonation, and ad/tracker blocking can create high-volume automated traffic if an agent loops or broadens scope., Persistent browser sessions stay open until closed; use `list_sessions` and `close_session` to avoid leaked browser processes., Selector-targeted extraction reduces irrelevant content, but model decisions based on scraped data still need review before filing reports, publishing datasets, or making operational changes.
Privacy notes
Tool calls and outputs can expose target URLs, selectors, page content, screenshots, cookies or session-derived state, proxy choices, geo-targeting intent, and scrape strategy to the MCP client and model provider., Screenshots are returned as image content blocks that the model can inspect, so they may reveal account pages, customer data, internal dashboards, or authenticated browsing state., Scraped public pages can contain secrets, personal data, copyrighted content, or hidden prompt-injection text; keep `main_content_only` enabled unless there is a clear reason to inspect hidden content., Proxy providers, target websites, and any browser services used by the deployment may receive request metadata, IP address information, headers, or fingerprint data., Do not scrape private, login-gated, regulated, copyrighted, or personal-data-heavy pages without legal, privacy, and security review.
Author
Karim Shoair
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
5 safety and 5 privacy notes across 4 risk areas. Review closely: credentials & tokens, network access.
4 areas
SafetyCredentials & tokensScrapling MCP can issue HTTP requests, launch browser-backed fetches, run stealth fetches, reuse persistent browser sessions, capture screenshots, and scrape multiple URLs concurrently.
SafetyGeneralStealth and anti-bot features can interact with Cloudflare Turnstile, interstitial pages, and other protection systems; use them only where scraping is permitted.
SafetyCredentials & tokensBulk tools, persistent sessions, proxies, browser impersonation, and ad/tracker blocking can create high-volume automated traffic if an agent loops or broadens scope.
SafetyCredentials & tokensPersistent browser sessions stay open until closed; use `list_sessions` and `close_session` to avoid leaked browser processes.
SafetyGeneralSelector-targeted extraction reduces irrelevant content, but model decisions based on scraped data still need review before filing reports, publishing datasets, or making operational changes.
PrivacyCredentials & tokensTool calls and outputs can expose target URLs, selectors, page content, screenshots, cookies or session-derived state, proxy choices, geo-targeting intent, and scrape strategy to the MCP client and model provider.
PrivacyGeneralScreenshots are returned as image content blocks that the model can inspect, so they may reveal account pages, customer data, internal dashboards, or authenticated browsing state.
PrivacyCredentials & tokensScraped public pages can contain secrets, personal data, copyrighted content, or hidden prompt-injection text; keep `main_content_only` enabled unless there is a clear reason to inspect hidden content.
PrivacyNetwork accessProxy providers, target websites, and any browser services used by the deployment may receive request metadata, IP address information, headers, or fingerprint data.
PrivacyData retentionDo not scrape private, login-gated, regulated, copyrighted, or personal-data-heavy pages without legal, privacy, and security review.
Safety notes
Scrapling MCP can issue HTTP requests, launch browser-backed fetches, run stealth fetches, reuse persistent browser sessions, capture screenshots, and scrape multiple URLs concurrently.
Stealth and anti-bot features can interact with Cloudflare Turnstile, interstitial pages, and other protection systems; use them only where scraping is permitted.
Bulk tools, persistent sessions, proxies, browser impersonation, and ad/tracker blocking can create high-volume automated traffic if an agent loops or broadens scope.
Persistent browser sessions stay open until closed; use `list_sessions` and `close_session` to avoid leaked browser processes.
Selector-targeted extraction reduces irrelevant content, but model decisions based on scraped data still need review before filing reports, publishing datasets, or making operational changes.
Privacy notes
Tool calls and outputs can expose target URLs, selectors, page content, screenshots, cookies or session-derived state, proxy choices, geo-targeting intent, and scrape strategy to the MCP client and model provider.
Screenshots are returned as image content blocks that the model can inspect, so they may reveal account pages, customer data, internal dashboards, or authenticated browsing state.
Scraped public pages can contain secrets, personal data, copyrighted content, or hidden prompt-injection text; keep `main_content_only` enabled unless there is a clear reason to inspect hidden content.
Proxy providers, target websites, and any browser services used by the deployment may receive request metadata, IP address information, headers, or fingerprint data.
Do not scrape private, login-gated, regulated, copyrighted, or personal-data-heavy pages without legal, privacy, and security review.
Prerequisites
Python 3.10 or newer and the `scrapling[ai]` package installed from PyPI or run through `uvx`.
Browser dependencies installed with `scrapling install` before using browser-backed, stealth, screenshot, or session tools.
Permission to scrape the target sites under their terms, robots guidance, copyright, privacy, and rate-limit requirements.
Optional proxy configuration only when proxy use is allowed by policy and the target site's terms.
Review process for model-visible web content because scraped pages may contain prompt-injection text or sensitive data.
Scrapling MCP Server brings Scrapling's scraping and browser-fetching
capabilities into MCP clients. Claude can ask it to make fast HTTP requests,
fetch dynamic content through Chromium or Chrome, use stealth fetching for
protected pages, target specific elements with CSS selectors, capture screenshots
from open sessions, and manage persistent browser sessions across requests.
The project publishes MCP metadata in server.json, documents a PyPI package
runtime with scrapling mcp, and provides source and hosted documentation for
the MCP server. Scrapling is especially relevant when an agent needs targeted
extraction before handing page content to the model, which can reduce token use
and avoid passing full pages when a selector is enough.
These sources were reviewed on 2026-06-06. Prefer the live repository,
README, MCP metadata, source docs, API reference, package metadata, hosted docs,
PyPI page, and license for current install commands, package versions, tool
names, transport options, and scraping guidance.
Features
Stdio MCP server through scrapling mcp.
PyPI package metadata and MCP server.json package metadata for uvx usage.
Optional Streamable HTTP mode through the Scrapling CLI.
Basic HTTP scraping with get and bulk_get.
Browser-backed dynamic fetching with fetch and bulk_fetch.
Stealth browser fetching with stealthy_fetch and bulk_stealthy_fetch.
Screenshot capture from an existing dynamic or stealth browser session.
Persistent session management with open_session, close_session, and list_sessions.
CSS selector targeting before content is handed to the model.
Proxy support, browser impersonation, parallel processing, and session reuse.
Automatic hidden-content sanitization when main_content_only is enabled.
Installation
Install Scrapling with MCP dependencies, then install browser dependencies before
using browser-backed tools:
pip install "scrapling[ai]"
scrapling install
For Claude Code, add the stdio server after confirming the scrapling
executable is on the PATH:
Extract a specific product field, table, article body, or listing element with a CSS selector.
Use basic HTTP scraping for simple pages where browser automation is unnecessary.
Fetch JavaScript-rendered pages through a browser-backed dynamic fetch.
Use stealth fetching only for allowed workflows where normal fetching fails on protection pages.
Capture screenshots from an existing session so Claude can inspect visual page state.
Reuse a persistent session while scraping multiple pages from the same allowed site.
Use bulk tools to scrape a small reviewed list of URLs more efficiently than repeated single requests.
Keep hidden-content sanitization enabled to reduce prompt-injection exposure from scraped pages.
Safety and Privacy
Scrapling MCP is an automation-capable scraping server. Confirm permission,
scope, rate limits, and legal basis before letting an agent scrape or screenshot
a site. Its own documentation advises checking robots guidance, respecting rate
limits, complying with site terms, and respecting copyright.
Use the least invasive tool that works. Prefer selector-targeted get requests
for simple public pages, and reserve browser, stealth, proxy, screenshot, and
bulk workflows for cases where they are allowed and necessary. Close persistent
sessions when finished, and review scraped content for prompt injection,
personal data, secrets, and copyrighted material before forwarding it into
reports, datasets, or other tools.
Duplicate Check
Existing entries cover Browserbase, BrowserMCP, Bright Data, Chrome MCP,
Playwright MCP, and related browser automation or scraping tools. No
D4Vinci/Scrapling, Scrapling MCP, scrapling mcp, Scrapling selector
scraping, or Scrapling stealth scraping entry was found in content/mcp,
content/tools, content/guides, content/agents, or content/skills.
Show that Scrapling MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/scrapling-mcp-server)
How it compares
Scrapling MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
1 trust signal differ across this comparison (Submitter).
MCP server for Scrapling web scraping workflows, including HTTP scraping, browser-backed dynamic fetching, stealth fetching, screenshots, persistent browser sessions, selectors, proxies, and prompt-injection sanitization.
Hyperbrowser's MCP server for AI agents that need hosted browser scraping, crawling, structured extraction, Bing search, persistent browser profiles, and browser-use, OpenAI CUA, or Claude computer-use browser agents.
✓Scrapling MCP can issue HTTP requests, launch browser-backed fetches, run stealth fetches, reuse persistent browser sessions, capture screenshots, and scrape multiple URLs concurrently.
Stealth and anti-bot features can interact with Cloudflare Turnstile, interstitial pages, and other protection systems; use them only where scraping is permitted.
Bulk tools, persistent sessions, proxies, browser impersonation, and ad/tracker blocking can create high-volume automated traffic if an agent loops or broadens scope.
Persistent browser sessions stay open until closed; use `list_sessions` and `close_session` to avoid leaked browser processes.
Selector-targeted extraction reduces irrelevant content, but model decisions based on scraped data still need review before filing reports, publishing datasets, or making operational changes.
✓AgentQL MCP exposes one tool, `extract-web-data`, that sends a target URL and natural-language extraction prompt to the AgentQL API.
The tool is intended for public webpages; do not use it to bypass access controls, scrape private pages, evade paywalls, or extract data where automated collection is prohibited.
Web extraction can still trigger target-site rate limits, legal restrictions, robots guidance, or terms-of-service concerns.
The source implementation uses AgentQL's query-data endpoint with fast mode, no screenshot capture, no scroll-to-bottom behavior, and no local browser cookies.
Treat extracted output as untrusted web data that may include errors, stale content, ads, tracking text, or prompt-injection attempts.
✓This server sends web searches, URLs, scraping targets, browser actions, package names, and dataset requests to Bright Data APIs.
Review website terms, robots policies, rate limits, jurisdictional requirements, and internal scraping policies before automating collection.
`PRO_MODE`, browser automation groups, data-product groups, and batch tools can increase cost, request volume, and operational impact.
The server can create or use Bright Data zones through API calls; review account permissions and zone settings before running it with broad API tokens.
Use `RATE_LIMIT`, group selection, and explicit tool allowlists to keep agent-driven browsing and scraping bounded.
✓Hyperbrowser MCP can scrape pages, crawl linked pages, extract structured data, search with Bing, create persistent profiles, delete profiles, list profiles, and run browser automation agents.
Browser-use, OpenAI CUA, and Claude computer-use tools can click, type, navigate, and interact with web apps. Keep human approval around authenticated, paid, destructive, or account-changing actions.
Persistent browser profiles can retain session state. Delete profiles that should not be reused and avoid sharing profile identifiers in public logs or prompts.
Scraping and crawling should respect site terms, robots expectations, rate limits, authentication boundaries, and internal data handling rules.
Do not give the MCP server broad access to private web apps, admin consoles, payments, or production dashboards without a scoped task and review plan.
Privacy notes
✓Tool calls and outputs can expose target URLs, selectors, page content, screenshots, cookies or session-derived state, proxy choices, geo-targeting intent, and scrape strategy to the MCP client and model provider.
Screenshots are returned as image content blocks that the model can inspect, so they may reveal account pages, customer data, internal dashboards, or authenticated browsing state.
Scraped public pages can contain secrets, personal data, copyrighted content, or hidden prompt-injection text; keep `main_content_only` enabled unless there is a clear reason to inspect hidden content.
Proxy providers, target websites, and any browser services used by the deployment may receive request metadata, IP address information, headers, or fingerprint data.
Do not scrape private, login-gated, regulated, copyrighted, or personal-data-heavy pages without legal, privacy, and security review.
✓Target URLs, extraction prompts, API key-authenticated requests, and extracted structured data are sent to AgentQL's API.
Extracted data can include personal data, copyrighted content, customer information, job postings, prices, social content, or other third-party material.
AGENTQL_API_KEY should stay out of prompts, issues, logs, screenshots, and committed configuration files.
Claude transcripts and downstream reports may retain extracted data, so avoid collecting information that is not approved for the model session.
✓Bright Data API tokens must stay in environment variables or secret managers and should never be committed to MCP configuration files.
Queries, URLs, package names, web pages, scraping outputs, dataset filters, and browser activity may be visible to Bright Data, the MCP client, and the model provider.
Public web data can still contain personal data, copyrighted content, customer information, or contractual restrictions.
Tool outputs can include scraped page text, search results, social or ecommerce dataset fields, package metadata, and browser screenshots depending on enabled tools.
✓Webpage URLs, page content, screenshots or extracted data, search queries, browser actions, profile identifiers, and tool outputs may be processed by Hyperbrowser and the connected model provider.
Authenticated browser sessions can expose cookies, account data, private documents, customer data, admin UI state, and generated artifacts to the MCP client and model provider.
Keep `HYPERBROWSER_API_KEY`, cookies, one-time codes, session URLs, API responses, and extracted private data out of prompts, commits, issue comments, screenshots, and shared logs.
For regulated or customer-sensitive data, review Hyperbrowser, MCP client, and model-provider retention policies before using browser automation.
Prerequisites
Python 3.10 or newer and the `scrapling[ai]` package installed from PyPI or run through `uvx`.
Browser dependencies installed with `scrapling install` before using browser-backed, stealth, screenshot, or session tools.
Permission to scrape the target sites under their terms, robots guidance, copyright, privacy, and rate-limit requirements.
Optional proxy configuration only when proxy use is allowed by policy and the target site's terms.
Node.js and npx available to the MCP client runtime.
AgentQL API key from the AgentQL developer portal.
Approved list of public webpages or domains Claude may query.
Review of target site terms, robots guidance, rate limits, and data-use rules before extraction.
Node.js and npx available to the MCP client runtime.
Bright Data account and API token stored as `API_TOKEN`.
Review of Bright Data plan limits, free-tier scope, paid modes, and data-product terms.
A decision about whether to use default rapid tools, `PRO_MODE`, `GROUPS`, or explicit `TOOLS`.
Node.js 18 or newer for the `hyperbrowser-mcp` npm package.
A Hyperbrowser account and `HYPERBROWSER_API_KEY` for hosted browser sessions.
An MCP client such as Claude Desktop, Claude Code, Cursor, Windsurf, or another client that can run stdio MCP servers.
Explicit approval for the URLs, websites, accounts, browser profiles, and data classes the agent may access.
Install
claude mcp add ScraplingServer scrapling mcp
npx -y agentql-mcp
npx @brightdata/mcp
claude mcp add hyperbrowser -e HYPERBROWSER_API_KEY=your-api-key -- npx -y hyperbrowser-mcp