Unbrowser vs Auth Fetch MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Unbrowser vs Auth Fetch MCP
In-depth architectural comparison of the Unbrowser 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
Unbrowser
Browser Automation · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Auth Fetch MCP
Browser Automation · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Unbrowser 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 Unbrowser when:
You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Stateful cookies and DOM sessions, Structured BlockMap page output, Stable element references.
Lightweight browser MCP server for LLM agents. Runs JavaScript, follows links, fills forms, manages cookies, and returns low-token BlockMaps from a single native binary without Chrome.
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
Unbrowser Tools (6)
Stateful cookies and DOM sessions
Structured BlockMap page output
Stable element references
HTML link and form handling
Bounded QuickJS script execution
Challenge and SPA escalation signals
Auth Fetch MCP Tools (4)
auth_fetch
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).
Unbrowser 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 Unbrowser 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.