In-depth architectural comparison of the Scrapeunblocker MCP and Auth Fetch 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
Auth Fetch MCP
Browser Automation · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Scrapeunblocker MCP if you need specialized Browser Automation tools running via a local process. Choose Auth Fetch 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.
Fetch content from login-protected web pages (Notion, Google Docs, Jira, Confluence, etc.) by opening a real browser for authentication with persistent session caching.
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.
Auth Fetch MCP Tools (4)
auth_fetch
The primary tool. Fetches page content using a real browser, opening a window for login if needed. Returns cleaned HTML with noise elements (nav, footer, scripts, etc.) stripped and media tags (`<img>`, `<video>`, `<iframe>`) preserved.
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, Auth Fetch MCP belongs to Browser Automation using local stdio subprocess. Select Scrapeunblocker MCP when you need capabilities focused on browser automation and Auth Fetch MCP when you require tools for browser automation.
Downloads files from URLs using saved browser sessions. Use this to lazily download images, videos, or other files found in `auth_fetch` results. The browser's saved cookies handle authentication automatically — no need to log in again.
list_pages
Lists all open tabs in the browser with their URLs and titles.
close_browser
Closes the browser window. Login sessions are saved and will be reused next time.