Google Search Console MCP

A Google Search Console MCP is an MCP server that exposes Search Console data as tools an AI assistant can call. Instead of you opening Search Console, applying filters, and exporting a report, the assistant asks the MCP server for the rows it needs and answers your question directly.

MCP, the Model Context Protocol, is an open standard for connecting AI assistants to outside data and tools. A client such as Claude, ChatGPT, or Cursor connects to an MCP server, reads the list of tools it offers, and calls them when a prompt needs outside data. The server does the actual work and returns structured results.

A GSC MCP server sits between the assistant and Google’s Search Console API. It handles authentication with Google, translates a tool call like “top queries for this property in the last 28 days” into an API request, and returns clicks, impressions, CTR, and position in a shape the assistant can reason about. The terms “GSC MCP”, “Search Console MCP”, and “MCP for Google Search Console” all describe the same thing.

CalmSEO’s version is a hosted SEO MCP server. The seven Search Console tools are free and sit next to paid keyword, SERP, audit, and backlink tools on the same endpoint.

Seven tools, all free, all read-only. Every tool except list_gsc_sites takes a site_url that matches a property exactly, for example sc-domain:example.com or https://www.example.com/. The analytics tools take start_date and end_date in YYYY-MM-DD format and an optional type for web, image, video, news, Discover, or Google News.

The same seven tools are also available as REST endpoints under /gsc/ on the CalmSEO API for scripts and automations that do not go through an assistant.

ChatGPT adds remote MCP servers through developer mode, not through the Custom GPT builder.

1. Open ChatGPT settings, go to Connectors, then Advanced settings, and enable Developer mode.
2. Click Create app. Name it CalmSEO and use https://mcp.calmseo.com/mcp as the server URL.
3. Choose OAuth for authentication and complete the CalmSEO sign-in.
4. In a new chat, pick Developer mode from the + menu, select CalmSEO, and ask about your Search Console data.

If the Developer mode toggle is missing, your plan or workspace may not have access yet. See the ChatGPT setup docs for screenshots and the ChatGPT Search Console setup guide for prompts and troubleshooting.

The assistant decides which tool to call and what to do with the rows. These are typical prompts and the shape of the answer you can expect.

• “Find pages with over 1,000 impressions and CTR below 1% in the last 28 days.” The assistant calls get_gsc_top_pages, filters the rows locally, and returns a short table of pages with their impressions, CTR, and position, usually followed by title and meta suggestions if you ask.
• “Which queries rank between position 8 and 20 with at least 200 impressions?” A striking-distance list built from get_gsc_top_queries or a search analytics query with a position filter. Good input for deciding which pages to update.
• “Compare the last 28 days with the previous 28 and list pages that lost the most clicks.” Two search analytics calls with different date ranges, then a diff. You get the page, clicks before, clicks after, and the change.
• “What queries does /blog/invoice-template rank for?” One get_gsc_page_queries call. The answer lists each query with clicks, impressions, CTR, and position for that URL only.
• “Show clicks by country for the last 90 days and tell me if anything looks off.” A search analytics query with the country dimension, then a short reading of the numbers. The assistant does the interpretation; the MCP only supplies the rows.
• “Are any of my sitemaps failing?” list_gsc_sitemaps for the property, then a plain summary of which sitemaps have errors or warnings and when Google last read them.
• “Check which of the URLs in my sitemap Google has actually indexed.” Repeated inspect_gsc_urls calls, 25 URLs at a time, then counts by coverage state and a list of URLs to look at. Google allows 2,000 inspections per day per property, so a large site can take more than one day.

Example output

Illustrative output for “What does /blog/invoice-template rank for?” The numbers are made up to show the shape; every row in a real answer comes from your own property.

From there a follow-up like “which of these could reach page one with a title rewrite?” needs no new tool call. Adding keyword volume for each query takes one paid call on the same endpoint. That two-step pattern is the basis of finding SEO opportunities in Search Console.

The Google connection is limited to the webmasters.readonly scope. CalmSEO can read analytics, property lists, sitemap status, and URL index status. It cannot submit or remove sitemaps, request indexing, change users, or edit anything in your Search Console account. Every GSC tool is also marked read-only in its MCP annotations, so clients that respect annotations know the call has no side effects.

What CalmSEO stores

To retrieve your data when you ask for it, CalmSEO stores the OAuth tokens, token expiry, granted scopes, connected property URLs, permission levels, and related timestamps. Retrieved Search Console results are held temporarily for up to five minutes and are not used for advertising or to train AI models. The full details are in the privacy policy.

Revoking access

Disconnect Google Search Console from the CalmSEO dashboard at any time. That removes the stored OAuth connection and property list. You can also revoke CalmSEO from your Google account’s third-party access settings, which invalidates the token on Google’s side.