NotFair
Approval-gated Google Ads MCP with hosted OAuth, 121 Google Ads tools, and logged, reviewable writes for campaigns, keywords, budgets, bids, ads, and assets.
เซิร์ฟเวอร์ MCP แบบโฮสต์
npx add-mcp 'https://notfair.co/api/mcp/notfair'ติดตั้งลง Claude Code, Codex, Cursor และอื่นๆ
เอกสาร
Google Ads MCP server
Google Ads MCP Server for any AI client.
NotFair is a hosted Google Ads MCP server for live campaign analysis and approved changes. Connect your ad account to Claude, Codex, Cursor, or a compatible MCP client, then investigate performance and review the next action.
Start free — 300 operations/moView setup guide
No credit card required · Read live data, approve every write
Works with
Google Ads MCP
Live
MCP endpoint
https://notfair.co/api/mcp/notfair
OAuth 2.0Streamable HTTP
Live tools
121
New to MCP? Read the spec at modelcontextprotocol.io.
30-second setup video
Connect Claude to Google Ads
Watch the complete NotFair setup—from choosing your ad account to confirming the connection inside Claude.
Customer reviews
What customers say
“It was the worst of times, then it was the best of times thanks to NotFair”
Daryl W.Runs two medical clinics in Washington State
Read his review on Trustpilot(opens in a new tab)
“Our agency's efficiency has increased a lot since using the tool.”
Pammer PPCGoogle Ads agency · Switzerland
Read their review on Trustpilot(opens in a new tab)
Read Daryl’s full storyAll NotFair reviews on Trustpilot(opens in a new tab)
Choose your connection
Which Google Ads MCP server do you need?
A Google Ads MCP server lets an AI client query your ad account through the Google Ads API. Some servers also expose campaign changes. Choose based on the work you need to do, the client you use, and who will maintain the connection.
| Option | Best fit | What to expect |
|---|---|---|
| Google’s official MCP | Read-only reporting with an engineering owner | Operate the server and supply Google Ads API credentials. Google’s setup documentation |
| NotFair | Hosted account analysis and reviewed campaign changes | Connect selected accounts through Google sign-in. NotFair operates the API integration; supported changes require approval. |
| Community or custom server | Source control and a tailored deployment | Capabilities vary. Your team verifies maintenance, credentials, account access, and write behavior. |
Choose your AI client
Claude.ai, Desktop & Cowork
Install the published Notfair connector.
Claude Code
Use the separate NotFair plugin setup.
Codex
Connect through the Codex MCP setup guide.
ChatGPT
Check plan eligibility and custom MCP availability before connecting.
Cursor, OpenClaw & Hermes
Follow the setup instructions for your MCP client.
Read the full Google Ads MCP comparison →
Tools exposed
121 What your AI client can read, diagnose, and stage
Read tools provide live account context. Write tools stage campaign edits for review — every write requires explicit human approval before it hits the Google Ads API.
| Tool | Type | What it does |
|---|---|---|
runScript | Read | Sandboxed JS with GAQL fan-out — every analytical read goes through this one tool. |
getRecommendations | Read | Google's optimization suggestions with estimated impact. |
getKeywordIdeas | Read | Keyword Planner search volume, competition, and CPC estimates. |
getChanges | Read | NotFair's own change log — undoable with one call. |
reviewChangeImpact | Read | Before/after impact analysis on recent edits. |
getResourceMetadata | Read | GAQL schema discovery for custom queries. |
| and more account, keyword, search-term, ad, and change-history tools |
Ready to wire up your client?
Sign in with Google, pick the ad accounts your agent can see, then add the hosted MCP endpoint to your client.
Start free — 300 operations/moOr follow a per-client setup guide
FAQ — NotFair MCP server
Common questions about authenticating, configuring, and using the NotFair Google Ads MCP server.
What is the NotFair Google Ads MCP server?
It is a hosted Model Context Protocol server that exposes your Google Ads account to MCP-compatible AI clients. Read tools provide live campaign context for diagnosis; write tools stage fixes that you approve before they run.
Which MCP clients are supported?
Claude.ai users install the published Notfair connector from Claude's directory. Claude Code, OpenAI Codex CLI, Hermes Agent, OpenClaw, Cursor, Cline, and custom MCP clients connect to the appropriate hosted NotFair MCP endpoint.
Do I need to self-host anything?
No. The server is hosted at https://notfair.co/api/mcp/notfair. You just point your client at it and authenticate.
How does authentication work?
OAuth 2.0 with PKCE is the recommended flow — Claude.ai and Codex run it automatically. For clients that don't support OAuth, you can use a Bearer token via the Authorization header. Generate either at notfair.co/connect.
Is the MCP server free?
Yes. Connecting and running a free Google Ads audit is free with no credit card. Paid plans unlock higher usage limits and team features.
Can the AI write to my account through this server?
Only with your explicit approval. Write tools propose changes, the client surfaces them, and you confirm before anything hits the Google Ads API. Read access is unrestricted; write access is gated.
Do I need my own Google Ads developer token?
No. NotFair hosts the Google Ads API integration and OAuth flow. You authorize the Google account and choose eligible ad accounts; you do not create a Cloud project, submit a developer-token application, or paste Google credentials into your AI client.
Does NotFair support Google Ads manager accounts (MCCs)?
Yes. NotFair discovers eligible client accounts beneath manager accounts and supports explicit per-call account routing so the agent can identify the intended client before reading data or staging a write.
Do both notfair.co and www.notfair.co MCP URLs work?
Yes. The apex notfair.co origin is canonical for new connections, while both origins remain supported for backward compatibility. OAuth discovery preserves the exact requested origin so RFC 9207 issuer matching succeeds on either hostname.
Per-client setup guides
Walkthroughs for each supported client.
[
×
Claude × Google Ads
Set up the NotFair Google Ads MCP in Claude.
Read setup guide](https://notfair.co/google-ads-claude-connector-setup-guide)[
×
Claude Code × Google Ads
Set up the NotFair Google Ads MCP in Claude Code.
Read setup guide](https://notfair.co/google-ads-claude-code-plugin-setup-guide)[
×
Codex × Google Ads
Set up the NotFair Google Ads MCP in Codex.
Read setup guide](https://notfair.co/google-ads-codex-mcp-setup-guide)[
×
Cursor × Google Ads
Set up the NotFair Google Ads MCP in Cursor.
Read setup guide](https://notfair.co/mcp/cursor?platform=google_ads)[
×
OpenClaw × Google Ads
Set up the NotFair Google Ads MCP in OpenClaw.
Read setup guide](https://notfair.co/mcp/openclaw?platform=google_ads)[
×
Hermes × Google Ads
Set up the NotFair Google Ads MCP in Hermes.
Read setup guide](https://notfair.co/mcp/hermes?platform=google_ads)
Evidence, not a feature checklist
Compare the full path from OAuth to impact review
See 7 Google Ads MCP servers compared on developer-token setup, write access, approval controls, manager-account routing, provenance, and undo—plus public prompts you can rerun yourself.
Hosted OAuth, no developer tokenWhat NotFair hosts and what the account owner authorizes.Approval, impact, and undoThe six-checkpoint safety contract for production writes.