Skip to content
MCP server

Google Search Console

Google Search Console data and SEO opportunity analysis for AI assistants

Runs locallyStatus and history
Install
Pricing
Open source
Platforms
CLI, API
Runs
Locally
Version
0.1.0
Listing updated
today

Similar MCP servers

About Google Search Console

Google Search Console is an open-source MCP server for marketing and seo. It runs locally on your machine and is started by your AI client.

Where most Search Console connectors hand back raw rows, this one adds analysis on top: keywords sitting just below page one, pages that rank but earn few clicks, queries split between several of your pages, and pages that lost traffic along with the reason. Expected click-through is estimated from your own site's data, and every result states caveats such as row caps, sampled data, hidden queries and incomplete days.

It runs on your machine and talks only to Google's API. Access is through a Google service account (added as a user on each property) or your own account via an OAuth browser sign-in. It is read-only unless GSC_ALLOW_WRITE=true is set, which enables the sitemap submit and delete tools. Inputs are forgiving: say example.com or paste a URL, and omit dates to get the last 28 complete days.

A doctor command checks credentials, the API and visible properties. Node.js 22 or newer is required.

Install

Run in a terminal

claude mcp add search-console-mcp --env GSC_SERVICE_ACCOUNT_JSON='<GSC_SERVICE_ACCOUNT_JSON>' -- npx -y @pixfrix/search-console-mcp

Add to claude_desktop_config.json

{
  "mcpServers": {
    "search-console-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pixfrix/search-console-mcp"
      ],
      "env": {
        "GSC_SERVICE_ACCOUNT_JSON": "<GSC_SERVICE_ACCOUNT_JSON>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "search-console-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pixfrix/search-console-mcp"
      ],
      "env": {
        "GSC_SERVICE_ACCOUNT_JSON": "<GSC_SERVICE_ACCOUNT_JSON>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "search-console-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@pixfrix/search-console-mcp"
      ],
      "env": {
        "GSC_SERVICE_ACCOUNT_JSON": "<GSC_SERVICE_ACCOUNT_JSON>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "search-console-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pixfrix/search-console-mcp"
      ],
      "env": {
        "GSC_SERVICE_ACCOUNT_JSON": "<GSC_SERVICE_ACCOUNT_JSON>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "search-console-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pixfrix/search-console-mcp"
      ],
      "env": {
        "GSC_SERVICE_ACCOUNT_JSON": "<GSC_SERVICE_ACCOUNT_JSON>"
      }
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Configuration

  • GSC_SERVICE_ACCOUNT_KEYPath to a Google service account JSON key. Not needed after signing in with 'auth login'.
  • GSC_SERVICE_ACCOUNT_JSONThe service account JSON key itself, as a string, for hosts without a file system.
  • GSC_SITE_URLDefault Search Console property, for example sc-domain:example.com.
  • GSC_BRAND_TERMSComma-separated brand names, used to separate branded from non-branded search.
  • GSC_ALLOW_WRITESet to true to enable the tools that submit and remove sitemaps.

Tools this server provides (18)

Taken from the project documentation; the running server may differ.

list_sites
Lists readable properties.
get_performance_overview
Totals, trend and top queries, pages, countries and devices.
search_analytics
Custom queries over any dimension with filters and paging.
compare_periods
Gainers, decliners, new and lost rows against a prior period.
detect_traffic_anomalies
Flags traffic drops and spikes.
get_brand_split
Splits branded and non-branded traffic.
find_quick_wins
Keywords ranking just below the top results.
find_ctr_opportunities
Well-ranked results with low click-through.
find_keyword_cannibalization
Queries split across several pages.
find_declining_pages
Pages or queries that lost the most clicks.
find_content_gaps
Searches the site appears for without a serving page.
analyze_page
Queries, devices, countries, trend and index status for one URL.
inspect_url
Indexing status of a URL.
inspect_urls
Indexing status of up to 50 URLs.
audit_sitemap_indexing
Share of a sitemap that is indexed.
list_sitemaps
Submitted sitemaps and their errors.
submit_sitemap
Submits a sitemap; needs write enabled.
delete_sitemap
Removes a sitemap; needs write enabled.

What it does

Opportunity finders
Ranked lists of quick wins, CTR gaps and keyword cannibalization.
Traffic change analysis
Compares periods and flags anomalies and declining pages.
Indexing checks
Inspects up to 50 URLs and audits sitemap indexing.
Brand split
Separates branded from non-branded search using your brand terms.
Read-only by default
Sitemap changes need `GSC_ALLOW_WRITE=true`.
Setup doctor
Checks credentials, API access and properties.

Good for

  • Find keywords one push from page one
  • Diagnose a sudden drop in organic traffic
  • Check whether a page is indexed and why not
  • Pick blog posts worth refreshing

Pricing

Open source

Google Search Console FAQ

How do I authenticate?

Use a Google service account added to each property, or sign in with your own Google account via `auth login`. The README says both are free.

Can it change my Search Console?

Only submit and delete sitemaps, and only when `GSC_ALLOW_WRITE=true`. Otherwise it is read-only.

What does it need to run?

Node.js 22 or newer and a Google account with access to the properties.

What happens if I omit dates?

It uses the last 28 complete days.

Is Google Search Console free?

Yes. Google Search Console is open source, so you can use and self-host it for free.

How do I add Google Search Console to Claude Code?

Run this command in your terminal: claude mcp add search-console-mcp --env GSC_SERVICE_ACCOUNT_JSON='<GSC_SERVICE_ACCOUNT_JSON>' -- npx -y @pixfrix/search-console-mcp

What are the best alternatives to Google Search Console?

The closest alternatives to Google Search Console are Scrapling MCP Server, Firecrawl MCP Server, Agent-Native Analytics, Douyin_TikTok_Download_API and Google Ads + Meta Ads + SEO/GEO MCP.

Where this comes from

  • Description: written from the project's README.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers