Browser Use MCP Server vs Auth Fetch MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
Browser Use MCP Server vs Auth Fetch MCP
In-depth architectural comparison of the Browser Use MCP Server 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
Browser Use MCP Server
Browser Automation · Local stdio
Quality: 59/100 (Good) | Auth: API Key required
Auth Fetch MCP
Browser Automation · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Browser Use MCP Server 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 Browser Use MCP Server 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: OPENAI_API_KEY, CHROME_PATH, PATIENT.
Primary tools included: Browser control through browser-use, SSE and stdio transport modes, Asynchronous browser operations.
browser-use packaged as an MCP server with SSE transport. includes a dockerfile to run chromium in docker + a vnc server.
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
Browser Use MCP Server Tools (5)
Browser control through browser-use
SSE and stdio transport modes
Asynchronous browser operations
VNC browser streaming
Dockerized Chromium environment
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).
Browser Use MCP Server 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 Browser Use MCP Server 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.