Google Search Console MCP serverGoogle Search Console MCP Server for any AI client.
NotFair connects your Google Search Console properties to Claude, Codex, Cursor, and any MCP client — 9 tools to inspect organic search performance, surface issues, and apply approved sitemap changes.
No credit card required · Read live data, approve every write
MCP endpoint
https://notfair.co/api/mcp/google_search_consoleLive tools
9New to MCP? Read the spec at modelcontextprotocol.io.
Tools exposed
9Search Console tools your AI client can query and act on
Read tools scoped to the properties you connect, plus approval-gated sitemap management. Every write is proposed in chat and confirmed before it reaches Google.
| Tool | Type | What it does |
|---|---|---|
listProperties | Read | List the verified Google Search Console properties the connected Google account can access, with each property's permission level. Handles both domain (sc-domain:example.com) and URL-prefix (https://example.com/) properties. |
getSearchAnalytics | Read | Clicks, impressions, CTR, and average position over any date range, optionally grouped by query, page, country, device, or date. Up to 25,000 rows per call. |
inspectUrl | Read | Single-URL index status via the URL Inspection API — coverage state, last crawl time, Google-selected canonical, mobile usability, and rich-result status. Quota is tight, so inspect specific URLs, never a whole crawl. |
listSitemaps | Read | The sitemaps submitted for a property, with last-submitted / last-downloaded times and per-sitemap warning and error counts. |
submitSitemap | Write | Submit or resubmit a sitemap so Google re-fetches it. Idempotent, approval-gated, and reversible with deleteSitemap. |
deleteSitemap | Write | Remove a previously submitted sitemap from a property. Approval-gated and reversible by resubmitting the same URL. |
| and more search-analytics and sitemap tools | ||
Ready to wire up your client?
Authorize NotFair to read your Google Search Console, pick the verified properties your agent can see, then add the hosted MCP endpoint to your client.
FAQ — NotFair MCP server
Common questions about authenticating, configuring, and using the NotFair Google Search Console MCP server.
It's a remote MCP (Model Context Protocol) server at https://notfair.co/api/mcp/google_search_console that exposes your Google Search Console properties as a typed tool surface for AI agents. Claude Desktop, Claude.ai Web, Claude Cowork, Claude Code, and Codex can all connect to it and answer questions over live organic-search data — top queries, page CTR, index coverage, and sitemaps.
Claude.ai's Add custom connector flow and Codex both use OAuth 2.0 with PKCE — there's no Client ID or Secret to copy. You authorize NotFair to read your Google Search Console once, pick which verified properties to expose, and the connection is scoped to those properties and revocable at any time.
Verified properties and their permission levels, Search Analytics (clicks, impressions, CTR, average position) grouped by query, page, country, device, or date, single-URL index inspection (coverage, canonical, crawl, mobile usability, rich results), and submitted sitemaps with their warning and error counts. Tokens are encrypted at rest and refreshed server-side.
Reads are unrestricted. The only writes are sitemap management — submitSitemap and deleteSitemap — and both are approval-gated: the change is proposed in chat, you confirm, and each is reversible. There are no destructive tools beyond sitemap removal, which submitSitemap reverses.
By default getSearchAnalytics returns finalized data, which lags roughly 2-3 days behind real time. You can request the 'all' data state to include the most recent, still-changing rows. Note that query-dimension rows omit anonymized low-volume queries, so they will not sum exactly to property totals — that's a Google Search Console API behavior, not a NotFair one.
Yes. listProperties returns both forms — domain properties look like sc-domain:example.com and URL-prefix properties look like https://example.com/. Every property-scoped tool accepts whichever identifier the property uses.
From /connect/google_search_console you can revoke access at any time. That removes the stored credential and invalidates the Claude and Codex OAuth tokens issued for the connection.
Per-client setup guides
Walkthroughs for each supported client.
Claude × Search Console
Set up the NotFair Search Console MCP in Claude.
Read setup guideClaude Code × Search Console
Set up the NotFair Search Console MCP in Claude Code.
Read setup guideCodex × Search Console
Set up the NotFair Search Console MCP in Codex.
Read setup guideCursor × Search Console
Set up the NotFair Search Console MCP in Cursor.
Read setup guideOpenClaw × Search Console
Set up the NotFair Search Console MCP in OpenClaw.
Read setup guideHermes × Search Console
Set up the NotFair Search Console MCP in Hermes.
Read setup guide