Fetch any URL and get clean Markdown. Web scraping for AI agents.
Fetch any URL and get clean Markdown. Web scraping for AI agents. That is what the webscrape mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
MCP server that lets AI agents search the web and extract clean Markdown content — no ads, no clutter, just the text your LLM needs.
The server publishes 9 tools. What each one is for:
webscrape_fetch_url — Fetch a single URL and return clean Markdown. Supports use_readability, js_render, extract_schema, and auto-detects PDFswebscrape_batch_fetch — Fetch up to 5 URLs in parallel. Supports PDF auto-detection, JS rendering, and structured datawebscrape_search — Search the web (DuckDuckGo → Google → Bing fallback) and scrape results into Markdownwebscrape_screenshot — Capture a screenshot of any web page with headless Chromium. Supports PNG/JPEG, viewport sizing, and full-page captureTools — The Tools tool exposed by this serverFeatures — The Features tool exposed by this serverDependencies — The Dependencies tool exposed by this serverDependencias — The Dependencias tool exposed by this serverLicencia — The Licencia tool exposed by this serverSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Webscrape's toolset — webscrape_fetch_url, webscrape_batch_fetch, webscrape_search and 6 more — is a fair guide to whether it matches your workflow. It is maintained by carrasquelalex1; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| webscrape_fetch_url | Fetch a single URL and return clean Markdown. Supports use_readability, js_render, extract_schema, and auto-detects PDFs |
| webscrape_batch_fetch | Fetch up to 5 URLs in parallel. Supports PDF auto-detection, JS rendering, and structured data |
| webscrape_search | Search the web (DuckDuckGo → Google → Bing fallback) and scrape results into Markdown |
| webscrape_screenshot | Capture a screenshot of any web page with headless Chromium. Supports PNG/JPEG, viewport sizing, and full-page capture |
| Tools | The Tools tool exposed by this server. |
| Features | The Features tool exposed by this server. |
| Dependencies | The Dependencies tool exposed by this server. |
| Dependencias | The Dependencias tool exposed by this server. |
| Licencia | The Licencia tool exposed by this server. |
{
"mcpServers": {
"webscrape": {
"url": "https://webscrape.mcpize.run",
"headers": {
"Authorization": "Bearer your-api-key"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.