How to Connect Google Ads to Claude (2026 Guide)

You connect Google Ads to Claude with an MCP (Model Context Protocol) server that bridges Claude to the Google Ads API. Once connected, Claude can read your campaigns, audit performance, draft ad copy, pause wasteful keywords, and bulk-update bids — all from a normal chat or coding session, no spreadsheets, no Google Ads UI clicking.

The fastest way is the open-source NotFair MCP server. It works with Claude Desktop, Claude Web, Claude Cowork, Claude Code, ChatGPT (via Codex connectors), Cursor, Windsurf, and any other MCP-compatible client. Setup takes about 5 minutes and starts at notfair.co/connect. This guide walks through every supported path, the exact errors you will hit if something goes wrong, and what changes in your day-to-day once Claude has access.

What you need before you start

You need three things: a Google Ads account with at least one active customer ID; a Claude client (Claude Desktop, Claude Web, Claude Cowork, Claude Code, ChatGPT with Codex connectors, or any MCP-compatible IDE like Cursor or Windsurf); and about 5 minutes for the OAuth handshake and the connector install.

• No developer token required — NotFair handles the Google Ads API token on your behalf, so you skip the 1–2 week Google approval process.
• No coding background required — the recommended path is point-and-click through Claude's built-in connector UI.
• No paid plan required — NotFair is free during the public beta, and there is a demo mode with sample data if you do not have a Google Ads account yet.

If your team uses a manager (MCC) account, sign in with the Google identity that has client access — not just MCC access. NotFair will surface both direct customers and clients linked under a manager during account selection.

How Claude actually connects to Google Ads

Claude does not talk to Google Ads directly. It talks to an MCP server, which talks to the Google Ads API on your behalf. The chain looks like this: you to Claude, Claude to the NotFair MCP server, NotFair to the Google Ads API.

MCP is Anthropic's open standard for letting AI agents call external tools safely. NotFair implements ~40 Google Ads tools — listCampaigns, pauseKeyword, runScript, bulkUpdateBids, addNegativeKeyword, and more — and exposes them through the MCP protocol. Claude reads the tool list, picks the right one for what you ask, and the server enforces auth and guardrails before anything touches your account.

The implication: you authenticate once on the server side, and every Claude client you connect afterwards reuses that auth. You do not paste API keys directly into Claude.

Connect Google Ads to Claude Desktop (recommended)

This is the path most users should take. It uses Claude's built-in Connectors UI — no config files, no terminal.

Step 1 — Sign in to NotFair with Google

Go to notfair.co/connect and click Sign in with Google. Use the Google identity that has access to your Google Ads account. On the consent screen, keep the "See, edit, create, and delete your Google Ads accounts and data" checkbox checked. If you uncheck it, NotFair has no permission to read your campaigns and the next step will fail.

Step 2 — Pick which Ads accounts Claude can manage

After OAuth, NotFair lists every Google Ads customer ID your account can reach — direct accounts and any clients under a manager (MCC) account, grouped clearly. Tick the accounts you want Claude to manage. You can add more or remove access later from the dashboard.

Step 3 — Add the NotFair connector in Claude Desktop

Stay on the Claude Desktop tab at notfair.co/connect/claude-connector. Click Add to Claude — this deeplinks into Claude Desktop and installs the connector with your auth token preconfigured. If the deeplink does not open (older Claude Desktop builds), copy the connector URL shown on the page and add it manually in Claude Desktop under Settings, Connectors, Add custom connector.

Step 4 — Verify it works

Open a new Claude conversation and ask for an audit. Claude should respond with a tool call to NotFair, return spend, conversion, and waste numbers, and offer next actions.

Connect Google Ads to Claude Code (CLI)

For developers and agency teams who live in the terminal. Claude Code installs the AdsAgent plugin in one command, which bundles the NotFair MCP server config plus three skills: /ads, /ads-audit, and /ads-copy.

claude plugin install nowork-studio/adsagent-plugin

On first run, Claude Code prompts you for an API key. Generate one at notfair.co/connect/claude-code (after the OAuth step above) and paste it in — or set it as an environment variable so future sessions pick it up automatically.

export ADSAGENT_API_KEY=your_key_here

Restart Claude Code, run /ads-audit, and you should see a full account health report with scoring, persona inference, and a prioritized fix list.

Connect Google Ads to ChatGPT or Codex

NotFair also exposes a Codex-compatible MCP endpoint, so the same auth works with OpenAI's Codex CLI and the ChatGPT Codex connector. After signing in, go to notfair.co/connect/codex, copy the MCP server URL and bearer token, then either:

• Codex CLI — add the server to the MCP block in your ~/.codex/config.toml file.
• ChatGPT Codex connector — paste the URL into the Codex connector setup screen inside ChatGPT.

A single Google Ads connection can power both Claude and ChatGPT side by side — useful if your team uses both, or if you want to compare reasoning across models on the same account data.

Connect Google Ads to Cursor, Windsurf, or any MCP client

Any client that speaks MCP can connect to NotFair. Visit notfair.co/connect/any-mcp, copy the server URL and bearer token, and paste them into your client's MCP server config. For Cursor, that is typically the ~/.cursor/mcp.json file.

{
  "mcpServers": {
    "notfair": {
      "url": "https://mcp.notfair.co/v1",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

Restart the client. The NotFair tools should appear in the agent panel. The same pattern works for Windsurf, Cline, and any custom MCP client — only the config file path changes.

What you can do once it is connected

Real prompts that work, with what each one does under the hood:

• Audit my account and find waste — runScript fans out parallel GAQL queries across spend, conversions, search terms, and quality scores, then correlates them in one pass.
• Pause keywords with zero conversions in 90 days — bulkPauseKeywords with a filter expression.
• Write 3 RSA variants for boarding services — createAd with experience-driven copy generation.
• Increase bids 15% on converting keywords — bulkUpdateBids scoped to keywords with at least one conversion.
• What changed in this account last week — getChanges from change history with diff summaries.
• Add 'free' as a negative keyword across all search campaigns — addNegativeKeyword applied at the campaign level.

The first audit is the highest-impact moment. Most accounts surface at least one fixable waste item in the first five minutes — usually a keyword bleeding spend with no conversions, or a search term triggering on intent it should not. Reviewing and approving those fixes recovers more spend than most paid optimization tools surface in their first month.

Common setup errors (and the fix)

These are the four errors users actually hit, in order of frequency. NotFair's connect page handles each with specific guidance — but knowing them ahead of time saves a few minutes.

No Google Ads accounts found for [email]

You signed in with the wrong Google identity. The most common cause is using your personal Gmail when your team's Ads account is on a different Workspace email. Click Use a different Google account and try again with the correct identity.

No client accounts under this manager

You signed in with an MCC (manager) account that does not have any client accounts linked yet. Either link a client in the Google Ads UI first, or sign in with a Google identity that has direct (non-manager) access.

Google Ads access is required

You unchecked the permission checkbox on Google's consent screen. NotFair literally cannot read your campaigns without it. Click the retry button — Google will re-prompt you, and this time leave the box checked.

Claude says "no tools available" after install

The connector was added but Claude has not picked up the tools yet. Quit and reopen Claude Desktop fully — not just a new conversation. MCP tools register at startup. The same applies to Claude Code, Cursor, and Windsurf: a full restart is required after adding a server.

Is it safe to give Claude access to Google Ads?

A reasonable question. Three guardrails that matter:

• OAuth-scoped access — NotFair only gets the Google Ads scope you grant. It cannot read your Gmail, Drive, calendar, or any other Google product. You can revoke access in 5 seconds at myaccount.google.com/permissions.
• Server-side guardrails — destructive actions like deleting a campaign or hard-pausing asset groups require explicit confirmation. NotFair also supports per-account spend caps and a preview-only mode for agencies who want to demo recommendations without execution rights.
• Auditable — every write is logged with full context, queryable through Claude ("what did you change in this account this week?") and reversible through the change-history view in the NotFair dashboard.

The realistic risk is the same risk you would have giving a junior media buyer keyboard access: a misunderstood instruction. Mitigate with the same controls — start with read-only audits, review proposed changes before applying, and keep the change-history tab open so you can roll back quickly if needed.

FAQ