NotFairNotFair
Start now

Co-founders

Does Claude Work With Google Search Console?

Yes. Claude can use Google Search Console through MCP. NotFair is a hosted option with 10 Search Console tools, OAuth setup, and approval-gated writes that match this platform's real lifecycle.

Tong Chen and Yuting Zhong|

Yes — Claude can work with Google Search Console through an MCP (Model Context Protocol) server. Anthropic does not publish a first-party Google Search Console connector. Google does not publish an official Search Console MCP in the public sources used here. NotFair provides a hosted Streamable HTTP server so Claude Desktop, Claude Code, Claude Cowork, and other MCP-compatible Claude surfaces can use the accounts you authorize.

Which Claude products work with Google Search Console?

  • Claude.ai, Claude Desktop, and Claude Coworkinstall the published Notfair connector and complete NotFair OAuth.
  • Claude Codeadd the hosted MCP URL (`https://notfair.co/api/mcp/notfair`) with HTTP transport.
  • Confirm the particular Claude surface and plan you use supports remote MCP before troubleshooting the account connection.

What you need to make it work

  • A Google Search Console account Claude is allowed to see.
  • NotFair hosts Google OAuth for Search Console. You authorize verified properties; you do not create a Cloud project for the MCP client.
  • A Claude surface that supports the MCP transport you selected.
  • About five minutes for the NotFair connection. NotFair advertises 10 Search Console tools, measured from the production registrar and guarded by a drift test.

What safety looks like when Claude can write

Read access and write access are not the same. 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. Claude does not receive your platform password or raw refresh token.

What does not work

  • Claude cannot read Google Search Console by URL or screenshot. Pasting a dashboard URL does nothing without an MCP connection.
  • A Claude surface that does not support the selected MCP transport cannot connect through that server.
  • Do not assume Google Ads impact snapshots or undo exist on this platform. NotFair only claims the lifecycle documented above.

How does Claude actually talk to Google Search Console?

Claude does not call the Google Search Console API directly. It calls the MCP server you configured, which calls Google Search Console on your behalf. With NotFair that server is hosted: NotFair hosts Google OAuth for Search Console. You authorize verified properties; you do not create a Cloud project for the MCP client. In every case the server—not Claude itself—owns the provider API interaction.

FAQ

Move from article to live account work

Connect your account first, then use an MCP client to turn the article workflow into a reviewed account action.

FAQ

Common questions about Model Context Protocol.

Anthropic does not publish a Google Search Console server. Google does not publish an official Search Console MCP in the public sources used here. Claude uses whichever compatible MCP server you configure, including NotFair.

NotFair advertises 10 Search Console tools, measured from the production registrar and guarded by a drift test.

Supported writes exist. 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.

Tool call inputs and outputs flow through Claude the same way any conversation does. Anthropic's data retention policies apply. NotFair only sends the records Claude requests via tool calls — not a full account dump.