Google Ads MCP serverGoogle 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.
No credit card required · Read live data, approve every write
MCP endpoint
https://notfair.co/api/mcp/notfairLive tools
119New to MCP? Read the spec at modelcontextprotocol.io.
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.
- Cursor, OpenClaw & Hermes
- Follow the setup instructions for your MCP client.
Tools exposed
119What 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.
FAQ — NotFair MCP server
Common questions about authenticating, configuring, and using 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.
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.
No. The server is hosted at https://notfair.co/api/mcp/notfair. You just point your client at it and authenticate.
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.
Yes. Connecting and running a free Google Ads audit is free with no credit card. Paid plans unlock higher usage limits and team features.
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.
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.
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.
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 guideClaude Code × Google Ads
Set up the NotFair Google Ads MCP in Claude Code.
Read setup guideCodex × Google Ads
Set up the NotFair Google Ads MCP in Codex.
Read setup guideCursor × Google Ads
Set up the NotFair Google Ads MCP in Cursor.
Read setup guideOpenClaw × Google Ads
Set up the NotFair Google Ads MCP in OpenClaw.
Read setup guideHermes × Google Ads
Set up the NotFair Google Ads MCP in Hermes.
Read setup guideCompare the full path from OAuth to impact review
See six 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.