Fetcher MCP vs Wet MCP

In-depth architectural comparison of the Fetcher MCP and Wet 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.

Which MCP Server Should You Choose?

Choose Fetcher MCP when:

• You need dedicated capabilities in the Search & Data Extraction domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: Playwright-based JavaScript rendering, Readability content extraction, Markdown or HTML output.

Explore Fetcher MCP Details

Choose Wet MCP when:

• You need dedicated capabilities in the Search & Data Extraction domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• You have access to required keys: WET_MCP_CONFIG.
• Primary tools included: search, extract, media.

Explore Wet MCP Details

Feature & Specification Comparison

Specification	Fetcher MCP jae-jae Search & Data Extraction	Wet MCP n24q02m Search & Data Extraction
Summary	MCP server for fetching web page content using Playwright headless browser, supporting Javascript rendering and intelligent content extraction, and outputting Markdown or HTML format.	Web search (embedded SearXNG), content extraction, and library docs indexing with hybrid search (FTS5 + semantic). Built-in Qwen3 embedding, no API keys required.
Category & Scope	Search & Data Extraction

Tools & Capabilities Breakdown

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

{
  "mcpServers": {
    "jae-jae-fetcher-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "fetcher-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "n24q02m-wet-mcp": {
      "command": "uvx",
      "args": [
        "invocation"
      ],
      "env": {
        "WET_MCP_CONFIG": "YOUR_WET_MCP_CONFIG_HERE"
      }
    }
  }
}

Related MCP Server Comparisons