What is the key difference between Auth Fetch MCP and WebReaper?

Auth Fetch MCP belongs to the Browser Automation category with local stdio execution, while WebReaper belongs to the Browser Automation category with cloud HTTP/SSE execution.

How do I install Auth Fetch MCP or WebReaper in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Auth Fetch MCP and WebReaper free or paid?

Auth Fetch MCP operates under a Free / Open Source model (No auth required). WebReaper operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Auth Fetch MCP lists 4 tools with 1 views and 36 GitHub stars. WebReaper lists 6 tools with 3 views and 147 GitHub stars.

Can I use both Auth Fetch MCP and WebReaper together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Auth Fetch MCP vs WebReaper

In-depth architectural comparison of the Auth Fetch MCP and WebReaper 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

Auth Fetch MCP

Browser Automation · Local stdio

Quality: 52/100 (Good) | Auth: No auth required

WebReaper

Browser Automation · Remote HTTP/SSE

Quality: 53/100 (Good) | Auth: API Key required

Verdict Summary: Choose Auth Fetch MCP if you need specialized Browser Automation tools running via a local process. Choose WebReaper if your workspace requires Browser Automation integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Auth Fetch MCP 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: auth_fetch, download_media, list_pages.

Explore Auth Fetch MCP Details

Choose WebReaper when:

You need dedicated capabilities in the Browser Automation domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: WEBREAPER_MCP_TOKEN.
Primary tools included: MCP tools for scraping, mapping, extraction, and crawling, Stdio and Streamable HTTP server variants, Markdown output by default.

Feature & Specification Comparison

Specification	Auth Fetch MCP ymw0407 Browser Automation	WebReaper alex-on-ai Browser Automation
Summary	Fetch content from login-protected web pages (Notion, Google Docs, Jira, Confluence, etc.) by opening a real browser for authentication with persistent session caching.	⃣ 🏠 🍎 🪟 🐧 - AI-native web scraper MCP server. Single binary, returns clean markdown, MIT-licensed Firecrawl alternative.
Category & Scope	Browser Automation

Tools & Capabilities Breakdown

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.

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.

WebReaper Tools (6)

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).

Auth Fetch MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "ymw0407-auth-fetch-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "auth-fetch-mcp@latest"
      ]
    }
  }
}

WebReaper Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "alex-on-ai-webreaper": {
      "url": "https://api.openai.com/v1"
    }
  }
}

Frequently Asked Questions

Auth Fetch MCP is categorized under Browser Automation and uses a local stdio subprocess. In contrast, WebReaper belongs to Browser Automation using remote streaming HTTP/SSE transport. Select Auth Fetch MCP when you need capabilities focused on browser automation and WebReaper when you require tools for browser automation.

More alternatives to Auth Fetch MCP More alternatives to WebReaper Browser Automation category hub Canonical compare URL