Suganthan's GSC MCP
Google Search Console MCP Server
29 Google Search Console tools for an agent: quick wins, cannibalization, content decay, image audits and URL indexing
- 188 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- Reads your site's Search Console data: queries, pages, clicks and impressions
- In full mode it submits URLs and sitemaps for indexing on your behalf and needs owner rights on the property
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/suganthan-mohanadasan-suganthans-gsc-mcpDetects 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.
- Reads your site's Search Console data: queries, pages, clicks and impressions
- In full mode it submits URLs and sitemaps for indexing on your behalf and needs owner rights on the property
This is third-party code. Review the repository files before installing.
What it does
The server connects Claude Code and Claude Desktop to Google Search Console data and returns finished conclusions instead of raw API rows. A question such as "which queries sit at positions 4 to 15 with lots of impressions" becomes a `quick_wins` call with an opportunity score. Other analysis tools find pages competing for the same query, content whose traffic fell three periods in a row, and queries whose CTR is below the benchmark for their position. A separate group covers images: `image_page_audit` visits pages on your own site and checks alt text, filenames, dimensions, lazy loading of the main image, formats, ImageObject schema and metadata inside the files. `genai_conversation_queries` sorts queries that look like follow-ups to Google's AI, such as "yes, go on", into seven groups. Data goes from your computer straight to Google and does not pass through anyone else's servers. Sign-in works through OAuth or a service account. `submit_url`, `submit_batch` and `submit_sitemap` send addresses and sitemaps for indexing and need full access.
Who it is for. SEO specialists and Search Console site owners who analyze traffic by asking Claude and want finished findings instead of exports.
Good fit when
- Monthly traffic dropped and you need to see what fell: rankings, CTR or demand
- You need a list of queries at positions 4 to 15 where a small page edit can lift clicks
- Two pages of the site pull in the same query and cannibalization is suspected
- A blog section is losing impressions and you want to see which articles have been decaying for three periods
- Images get impressions in image search but no clicks, and the pages need a breakdown
Not a fit when
- You need data from Bing, GA4 or AdSense: the server works only with Google Search Console
- You cannot create an OAuth client in Google Cloud once: built-in sign-in without that step is not available yet
- The site is not verified in Search Console: without a property there is nothing to show
- You want a web interface with charts instead of questions to an agent
Example request
Show the quick wins for the site over 28 days and find pages that cannibalize each other for the same queriesMCP
- Transport
- stdio
- Authentication
- OAuth
Environment variables
GSC_AUTH_MODE- Sign-in method; the README example uses oauth.
GSC_OAUTH_SECRETS_FILE- Path to the OAuth client JSON downloaded from Google Cloud.
GSC_KEY_FILEsecret- Path to a service account JSON key when sign-in runs without a browser.
GSC_SITE_URL- Default Search Console property, for example sc-domain:yoursite.com.
GSC_SCOPES- Access level: readonly or full. Without a value, full access applies.
GSC_SITE_URLS- A comma-separated list of properties for working with several sites.
Limitations
- You need your own OAuth client from Google Cloud or a service account. The setup wizard handles the rest, but this step is mandatory for now.
- Access is read-only by default. The indexing tools need full access, and Google's rules limit the Indexing API to JobPosting and BroadcastEvent, although in practice it accepts other pages too.
- The Generative AI report in Search Console has no API, so `genai_conversation_queries` looks for its traces by indirect signs in regular queries.
- Submitting URLs needs owner-level rights on the property for the service account.
How to disable. Remove the `gsc` entry from `claude_desktop_config.json`, or run `claude mcp remove gsc` in Claude Code, and restart the client. The saved token lives locally in `~/.gsc-mcp/` and can be deleted by hand. The app's access is revoked on the Google account security page.
FAQ
How do I connect Google Search Console to Claude Code?
Run `npx -y suganthan-gsc-mcp setup`. The wizard opens Google sign-in, verifies the connection with a live call, lets you pick a property and writes the settings for Claude Desktop and Claude Code. You need an OAuth client JSON from Google Cloud once.
Does my Search Console data go to third-party servers?
According to the author, no: data goes from your computer straight to Google. The token is stored locally in `~/.gsc-mcp/`.
What is the difference between readonly and full?
In readonly mode Google asks for a single view permission and the analysis works. Full mode also opens URL and sitemap submission for indexing. The choice is made in the wizard with the `--scopes` flag.
Can I connect several sites?
Yes, list the properties separated by commas in the `GSC_SITE_URLS` variable. The advanced analytics tool, `genai_conversation_queries` and all image audit tools take an optional `site_url` parameter, so you can ask about another site right in the request.
What can I ask?
For example: "what are my quick wins", "which pages lost traffic and why", "what content is decaying", "how does my CTR compare to benchmarks", "is this page indexed". The agent picks the right one of the 29 tools itself.
Discussion
No questions or reviews yet.
Related
MCP serversGoogle 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
Search 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
GA4 MCP server: an agent reads Google Analytics 4 reports, schema and real-time data and analyses traffic by playbooks.
MCP server for Google Ads: analyze campaigns, metrics and keywords with GAQL queries right in the chat with an agent
An MCP server joins Google Search Console history with a live site crawl and ranks findings by the clicks a fix could recover.
The experimental official Google Analytics 4 MCP server: reports, funnels and realtime data on request
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Suganthan's GSC MCP (this card) | no | OAuth | 188 | |
| Search Console MCP: Google, Bing and GA4 data for agents | no | OAuth | 322 | adds Bing, GA4 and AdSense data to Google Search Console, while this server sticks to Google only |
| Google Search Console MCP | no | OAuth | 2,186 | also a Google Search Console only server, centered on queries, pages, indexing and sitemaps |
README in short
The README opens with example questions and result screenshots, then covers quick setup with the wizard, manual OAuth or service account configuration and an `.mcpb` bundle for Claude Desktop. After that come tables of all 29 tools by group, an indexing section and notes on versions 2.4 and 2.5 from August 2026.