Interact with WebScraping.AI for web data extraction and scraping.
WebScraping.AI becomes available to MCP clients through the webscraping.ai mcp server. Interact with WebScraping.AI for web data extraction and scraping.
A Model Context Protocol (MCP) server implementation that integrates with WebScraping.AI for web data extraction capabilities — Chromium JavaScript rendering, rotating datacenter/residential/stealth proxies, and AI-powered question answering and structured field extraction on any page.
Once connected, the assistant can call these 12 tools directly:
timeout — Maximum web page retrieval time in ms (15000 by default, maximum is 30000)js_timeout — Maximum JavaScript rendering time in ms (2000 by default)wait_for — CSS selector to wait for before returning the page contentproxy — Type of proxy: datacenter, residential, or stealth (residential by default). Use stealth for the most heavily protected sites with advanced anti-bot detectioncountry — Country of the proxy to use (US by default). Supported countries: us, gb, de, it, fr, ca, es, ru, jp, kr, incustom_proxy — Your own proxy URL in "http://user:password@host:port" formatdevice — Type of device emulation. Supported values: desktop, mobile, tableterror_on_404 — Return error on 404 HTTP status on the target page (false by default)error_on_redirect — Return error on redirect on the target page (false by default)js_script — Custom JavaScript code to execute on the target pageRequired — The Required tool exposed by this serverContributing — 1. Fork the repository 2. Create your feature branch 3. Run tests: npm test 4. Submit a pull requestThe server is distributed via npm as webscraping-ai-mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
Before the server will start you need to supply 8 environment variables: WEBSCRAPING_AI_API_KEY, WEBSCRAPING_AI_CONCURRENCY_LIMIT, WEBSCRAPING_AI_ENABLE_CONTENT_SANDBOXING, WEBSCRAPING_AI_DEFAULT_PROXY_TYPE, WEBSCRAPING_AI_DEFAULT_JS_RENDERING, WEBSCRAPING_AI_DEFAULT_TIMEOUT, WEBSCRAPING_AI_DEFAULT_JS_TIMEOUT, ANTHROPIC_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.
Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. WebScraping.AI sits in that group, and the shape of its toolset — timeout, js_timeout, wait_for among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| timeout | Maximum web page retrieval time in ms (15000 by default, maximum is 30000) |
| js_timeout | Maximum JavaScript rendering time in ms (2000 by default) |
| wait_for | CSS selector to wait for before returning the page content |
| proxy | Type of proxy: datacenter, residential, or stealth (residential by default). Use stealth for the most heavily protected sites with advanced anti-bot detection — costs more than residential, see the pricing page. |
| country | Country of the proxy to use (US by default). Supported countries: us, gb, de, it, fr, ca, es, ru, jp, kr, in |
| custom_proxy | Your own proxy URL in "http://user:password@host:port" format |
| device | Type of device emulation. Supported values: desktop, mobile, tablet |
| error_on_404 | Return error on 404 HTTP status on the target page (false by default) |
| error_on_redirect | Return error on redirect on the target page (false by default) |
| js_script | Custom JavaScript code to execute on the target page |
| Required | The Required tool exposed by this server. |
| Contributing | 1. Fork the repository 2. Create your feature branch 3. Run tests: npm test 4. Submit a pull request |
{
"mcpServers": {
"mcp-server-webscraping-ai": {
"command": "npx",
"args": ["-y", "webscraping-ai-mcp"],
"env": {
"WEBSCRAPING_AI_API_KEY": "YOUR_API_KEY_HERE",
"WEBSCRAPING_AI_CONCURRENCY_LIMIT": "5",
"WEBSCRAPING_AI_ENABLE_CONTENT_SANDBOXING": "true"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| WEBSCRAPING_AI_API_KEY | Credential the server authenticates with. | Yes |
| WEBSCRAPING_AI_CONCURRENCY_LIMIT | Configuration value read at startup. | Optional |
| WEBSCRAPING_AI_ENABLE_CONTENT_SANDBOXING | Configuration value read at startup. | Optional |
| WEBSCRAPING_AI_DEFAULT_PROXY_TYPE | Configuration value read at startup. | Optional |
| WEBSCRAPING_AI_DEFAULT_JS_RENDERING | Configuration value read at startup. | Optional |
| WEBSCRAPING_AI_DEFAULT_TIMEOUT | Configuration value read at startup. | Optional |
| WEBSCRAPING_AI_DEFAULT_JS_TIMEOUT | Configuration value read at startup. | Optional |
| ANTHROPIC_API_KEY | Credential the server authenticates with. | Yes |
The simplest web tool that matters — fetch any URL and get model-ready markdown back.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Put 6,000+ pre-built scrapers at your assistant's fingertips through one MCP endpoint.