Scrapeunblocker MCP vs Agent Scraper MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
Scrapeunblocker MCP vs Agent Scraper MCP
In-depth architectural comparison of the Scrapeunblocker MCP and Agent Scraper MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Scrapeunblocker MCP
Browser Automation · Local stdio
Quality: 61/100 (Good) | Auth: API Key required
Agent Scraper MCP
Browser Automation · Local stdio
Quality: 56/100 (Good) | Auth: other
Verdict Summary: Choose Scrapeunblocker MCP if you need specialized Browser Automation tools running via a local process. Choose Agent Scraper MCP if your workspace requires Browser Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Scrapeunblocker MCP when:
You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: SCRAPEUNBLOCKER_KEY.
Fetch any web page's HTML (or AI-parsed JSON, or Google results) through the ScrapeUnblocker anti-bot API (Cloudflare, DataDome, PerimeterX, Akamai, Shape), using your own API key. Three tools: fetchhtml, fetchparsed, googlesearch. Install: npx -y scrapeunblocker-mcp.
Web scraping MCP server for AI agents. 6 tools: clean content extraction, structured scraping with CSS selectors, full-page screenshots via Playwright, link extraction, metadata extraction (OG/Twitter cards), and Google search. Free tier with x402 micropayments.
Category & Scope
Tools & Capabilities Breakdown
Scrapeunblocker MCP Tools (4)
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.
Agent Scraper MCP Tools (6)
title
Page title
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Scrapeunblocker MCP is categorized under Browser Automation and uses a local stdio subprocess. In contrast, Agent Scraper MCP belongs to Browser Automation using local stdio subprocess. Select Scrapeunblocker MCP when you need capabilities focused on browser automation and Agent Scraper MCP when you require tools for browser automation.