In-depth architectural comparison of the Agent Scraper 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
Agent Scraper MCP
Browser Automation · Local stdio
Quality: 56/100 (Good) | Auth: other
Auth Fetch MCP
Browser Automation · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Agent Scraper 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 Agent Scraper MCP when:
You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Freemium).
You have access to required keys: PUBLIC_HOST, X402_WALLET_ADDRESS.
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.
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
Agent Scraper MCP Tools (6)
title
Page title
description
Meta description
canonical
Canonical URL
favicon
Favicon URL
og
Open Graph tags
twitter
Twitter Card tags
Auth Fetch MCP Tools (4)
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).
Agent Scraper 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 Agent Scraper MCP when you need capabilities focused on browser automation and Auth Fetch MCP when you require tools for browser automation.
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.
download_media
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.