What is the key difference between Google Search Console MCP and Fetcher MCP?

Google Search Console MCP belongs to the Search & Data Extraction category with local stdio execution, while Fetcher MCP belongs to the Search & Data Extraction category with local stdio execution.

How do I install Google Search Console MCP or Fetcher MCP 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 Google Search Console MCP and Fetcher MCP free or paid?

Google Search Console MCP operates under a Free / Open Source model (No auth required). Fetcher MCP operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Google Search Console MCP lists 12 tools with 1 views and 0 GitHub stars. Fetcher MCP lists 6 tools with 5 views and 1,087 GitHub stars.

Can I use both Google Search Console MCP and Fetcher MCP 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

Google Search Console MCP vs Fetcher MCP

In-depth architectural comparison of the Google Search Console MCP and Fetcher 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

Google Search Console MCP

Search & Data Extraction · Local stdio

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

Fetcher MCP

Search & Data Extraction · Local stdio

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

Verdict Summary: Choose Google Search Console MCP if you need specialized Search & Data Extraction tools running via a local process. Choose Fetcher MCP if your workspace requires Search & Data Extraction integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Google Search Console 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: list_sites, get_site, add_site.

Explore Google Search Console MCP Details

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

Feature & Specification Comparison

Specification	Google Search Console MCP Search & Data Extraction	Fetcher MCP jae-jae Search & Data Extraction
Summary	MCP server for the Google Search Console API: search analytics, sitemaps, URL inspection, sites.	MCP server for fetching web page content using Playwright headless browser, supporting Javascript rendering and intelligent content extraction, and outputting Markdown or HTML format.
Category & Scope	Search & Data Extraction

Tools & Capabilities Breakdown

Google Search Console MCP Tools (12)

list_sites

All Search Console properties the account can access, with permission levels.

get_site

One property's entry (siteUrl + permissionLevel).

add_site

Add a property (stays unverified until verified in Search Console).

delete_site

Unlink a property from the account (no data is deleted).

search_analytics

Performance query: clicks/impressions/CTR/position by date, query, page, country, device, search appearance or hour; filters, search type, pagination, fresh-data mode.

get_top_queries

Shortcut for the most common ask: top queries by clicks, optionally filtered by page substring, country or device.

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

Google Search Console MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "google-search-console-mcp-2": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-search-console@latest"
      ]
    }
  }
}

Fetcher MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Google Search Console MCP is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, Fetcher MCP belongs to Search & Data Extraction using local stdio subprocess. Select Google Search Console MCP when you need capabilities focused on search & data extraction and Fetcher MCP when you require tools for search & data extraction.

More alternatives to Google Search Console MCP More alternatives to Fetcher MCP Search & Data Extraction category hub