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
- 2,060 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Accesses Search Console data through a Google account
- Can submit sitemaps and, with GSC_ALLOW_DESTRUCTIVE, remove sites and sitemaps
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/google-search-console-mcp-server-for-seosDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Accesses Search Console data through a Google account
- Can submit sitemaps and, with GSC_ALLOW_DESTRUCTIVE, remove sites and sitemaps
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 mostMCP
- Transport
- stdio
- Authentication
- OAuth
Environment variables
GSC_OAUTH_CLIENT_SECRETS_FILEsecret- Absolute path to the OAuth client secrets JSON, needed for OAuth
GSC_CREDENTIALS_PATHsecret- 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
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.
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.
Discussion
No questions or reviews yet.
Related
MCP serversSearch Console MCP: Google, Bing and GA4 data for agents
Search Console MCP
An MCP server that gives an agent Google Search Console, Bing Webmaster, GA4 and AdSense data with ready SEO checks
SEO CLI and MCP
seo-cli
The seo command and an MCP server for SEO work: page audits, Search Console, analytics and keywords. Sign-in through Google
A 36-tool MCP server: Google Search Console, Bing Webmaster, IndexNow submission to Yandex, LLM citation checks, page audits and llms.txt, all local
MCP server for Google Ads: analyze campaigns, metrics and keywords with GAQL queries right in the chat with an agent
Eight read-only SEO MCP servers
seo-tools-mcp
SERP, Wordstat, GSC, GA4, Yandex Webmaster, Metrika and A-Parser: eight read-only MCP servers with strict JSON and multi-account support for Claude Code
The experimental official Google Analytics 4 MCP server: reports, funnels and realtime data on request
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.