NotFairNotFair
Start now

Codex · Google Search Console

Manage Google Search Console from Codex CLI with the same hosted MCP Claude uses

NotFair is a hosted Google Search Console MCP for OpenAI's Codex CLI. One terminal command registers the server. Codex then reads live Search Console data and stages writes for approval. 10 Search Console tools.

10 Search Console tools

Most tools are reads. submitSitemap and deleteSitemap wait for approval and are inverses. This is not a Google Ads impact/undo product.

Turn Codex Into Your Marketing Engine

Bring ads, search, analytics, CRM, and WordPress into your AI client. Explore each integration to see its supported actions.

Choose a platform

Choose your AI client

1

Install the MCP

Run this in your terminal:
codex mcp add NotFair-GoogleSearchConsole --url https://notfair.co/api/mcp/notfair
2

Sign in and start asking

After running the command, Codex auto-opens a sign-in link in your browser. Sign in with NotFair and you are all set. Try: Audit my Search Console account and rank fixes by impact.

How it works

From install to an approved Search Console change

01

Connect Search Console

NotFair hosts Google OAuth for Search Console. You authorize verified properties; you do not create a Cloud project for the MCP client.

02

Add Codex

From any shell where Codex CLI is installed: `codex mcp add NotFair-GoogleSearchConsole --url https://notfair.co/api/mcp/notfair`. Codex walks through OAuth and registers the MCP.

03

Ask, then approve writes

Codex can inspect Verified properties, Search Analytics, URL inspection, and sitemap inventory. Writes wait for your confirmation. Default Search Analytics uses finalized data (~2–3 day lag). inspectUrl covers one URL at a time.

What the client can do

Search Analytics plus reversible sitemap writes

There is no official Google Search Console MCP in the public sources used here. NotFair hosts OAuth and gates the only two mutations — sitemap submit and delete.

Search Analytics

Query clicks, impressions, and queries with freshness metadata. Default data is finalized (~2–3 day lag).

URL inspection

inspectUrl returns coverage, canonical, crawl, and rich-result evidence for one URL.

Sitemap inverses

submitSitemap and deleteSitemap wait for approval. Resubmit the same URL to reverse a delete.

No ads undo claims

Recovery is sitemap submit/delete, not campaign impact snapshots.

Search Console tools

10 Search Console tools the client can call

The advertised count is measured from registerSearchConsoleTools() and guarded by a drift test.

ToolType
listSitesread
querySearchAnalyticsread
inspectUrlread
runScriptread
submitSitemapwrite
deleteSitemapwrite

Full tool surface: /google-search-console-mcp.

Google Search Console + Codex FAQ

Direct answers for operators connecting Google Search Console to OpenAI Codex CLI through NotFair.

Connect Google Search Console at notfair.co, run `codex mcp add NotFair-GoogleSearchConsole --url https://notfair.co/api/mcp/notfair`, then ask Codex to inspect live data. Writes stay staged until you approve them.

Same hosted MCP endpoint, different client. Codex CLI calls NotFair using OpenAI's MCP support. Claude's connector and Claude Code call the same server from Anthropic's clients.

Only with explicit approval. Most tools are reads. submitSitemap and deleteSitemap wait for approval and are inverses. This is not a Google Ads impact/undo product. Default Search Analytics uses finalized data (~2–3 day lag). inspectUrl covers one URL at a time.

Google does not publish an official Search Console MCP in the public sources used here.

Connect Google Search Console to Codex

Most tools are reads. submitSitemap and deleteSitemap wait for approval and are inverses. This is not a Google Ads impact/undo product.

Most tools are reads. submitSitemap and deleteSitemap wait for approval and are inverses. This is not a Google Ads impact/undo product.