Google Search Console MCP

Google Search Console MCP Server for SEOs

An MCP server for Google Search Console: queries and pages with clicks and positions, URL indexing checks, sitemaps and ready SEO skills

MCP serverMedium risk

aminforou/mcp-gsc

Install

{
  "mcpServers": {
    "gscServer": {
      "command": "/FULL/PATH/TO/uvx",
      "args": ["mcp-search-console"],
      "env": {
        "GSC_OAUTH_CLIENT_SECRETS_FILE": "/full/path/to/client_secrets.json"
      }
    }
  }
}

Install uv first: curl -LsSf https://astral.sh/uv/install.sh | sh. For a service account use GSC_CREDENTIALS_PATH and GSC_SKIP_OAUTH=true.

This is third-party code. Review the repository files before installing.

What it does

The server gives the agent Search Console data: properties, queries and pages with impressions, clicks, CTR and position, period comparisons and filters by country, device and page. It inspects indexing for single URLs and batches of up to ten, lists sitemaps with errors and submits new ones. Adding and removing sites and deleting sitemaps are enabled only with GSC_ALLOW_DESTRUCTIVE. Bundled skills cover a weekly SEO report, cannibalization checks, an indexing audit and finding queries ranked 11 to 20.

Who it is for. For SEO specialists and marketers analyzing a site's Google search traffic.

Good fit when

  • You need to see which queries drive traffic and where clicks dropped
  • You need to check why pages are not indexed
  • You need to find pages competing for the same query

Not a fit when

  • Most of the site's traffic comes from Yandex, which needs Yandex Webmaster
  • The site is not verified in Search Console

Example request

Compare example.com clicks and impressions for the last 28 days with the previous period and name the queries that dropped most

Limitations

Requires a Google Cloud project with the Search Console API enabled and an OAuth client or service account. With uvx the config needs the full path to uvx; manual install needs Python 3.11 or later. Batch inspection is limited to ten URLs. Google API availability from Russia without a VPN may vary.

How to disable. Remove the gscServer block from your MCP client config and revoke the OAuth app's access in your Google account if needed.

MCP

Transport
stdio
Authentication
OAuth
Environment variables
Environment variables
GSC_OAUTH_CLIENT_SECRETS_FILE
secret
Absolute path to the OAuth client secrets JSON, needed for OAuth
GSC_CREDENTIALS_PATH
secret
Absolute path to the service account key
GSC_SKIP_OAUTH
true forces service account auth
GSC_DATA_STATE
all as in the dashboard, or final for confirmed data only
GSC_ALLOW_DESTRUCTIVE
true enables adding and removing sites and deleting sitemaps

Security check

  • Accesses Search Console data through a Google account
  • Can submit sitemaps and, with GSC_ALLOW_DESTRUCTIVE, remove sites and sitemaps

README in short

The README lists the server's features and tools and walks through Google access via OAuth or a service account. The main launch method is uvx with configs for Claude Desktop, Cursor and Codex, with a clone-and-Python fallback. It documents environment variables, Cursor skills and common errors. The README also promotes the author's paid hosted version. MIT licensed.

FAQ

How to fix spawn uvx ENOENT?

GUI clients do not see ~/.local/bin. Find the path with which uvx and use it in the command field.

Can the agent remove a site from Search Console?

Only with GSC_ALLOW_DESTRUCTIVE=true; such tools are off by default.

A Claude Code plugin for SEO audits: technical SEO, E-E-A-T, schema, local and AI search via parallel subagents

PluginHigh risk16.9K

A Claude Code skill set for auditing sites for AI search: citability, AI crawler access, llms.txt, schema and reports

SkillMedium risk10.6K

The experimental official Google Analytics 4 MCP server: reports, funnels and realtime data on request

MCP serverMedium risk3.2K

SEO audits for sites, articles and GitHub repos: topic sub-skills, evidence-collecting scripts and a fix plan

SkillMedium risk907