Google Ads MCP serverGoogle Ads MCP Server for any AI client.
NotFair connects your Google Ads account to Claude, Codex, Cursor, and any MCP client — 111 tools to inspect campaigns, find issues, and stage approved changes.
No credit card required · Read live data, approve every write
MCP endpoint
https://notfair.co/api/mcp/google_adsLive tools
111New to MCP? Read the spec at modelcontextprotocol.io.
Tools exposed
111What 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.
Any client that speaks the MCP Streamable HTTP transport — Claude.ai (Web, Desktop, Cowork), Claude Code, OpenAI Codex CLI, Hermes Agent, OpenClaw, Cursor, Cline, and custom MCP clients. The server URL is the same; only the client-side config differs.
No. The server is hosted at https://notfair.co/api/mcp/google_ads. 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.
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 guide