NotFairNotFair
Start now
Search ConsoleGoogle Search Console MCP server

Google 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

Works with
Search Console MCP
Live

MCP endpoint

https://notfair.co/api/mcp/notfair
OAuth 2.0Streamable HTTP

Live tools

9

New 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.

ToolType
listPropertiesRead
getSearchAnalyticsRead
inspectUrlRead
listSitemapsRead
submitSitemapWrite
deleteSitemapWrite
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/notfair 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.

In Claude.ai, install the published Notfair directory connector and complete OAuth 2.0 with PKCE — no server URL, Client ID, or Secret to copy. Codex connects to the remote MCP endpoint and uses the same secure OAuth flow. You choose which verified properties to expose, and access is 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.