Google Ads Claude connector
In 2026, connect Google Ads to Claude with NotFair: install the published connector from claude.ai/directory/notfair (Claude.ai, Desktop, Cowork) or the Claude Code plugin, then OAuth your ads accounts—no developer token. Claude reads live campaigns via 121 tools and stages bid, budget, negative, and ad writes with diffs, impact, and undo until you approve. Free: 7 unlimited days, then 300 ops; Growth $99/mo or $950/yr.
Last verified · October 9, 2026
Not affiliated with Google or Anthropic. OAuth setup. Human approval on every write.
How it works
On Claude.ai, Claude Desktop, or Cowork, open claude.ai/directory/notfair and connect the published Notfair listing. No Client ID, Secret, or MCP URL to paste. Team and Enterprise orgs may need an owner to approve the connector first.
In Claude Code, add the NotFair marketplace, install the plugin, reload, then run /google-ads. Other MCP clients can add the hosted NotFair endpoint after you OAuth. The plugin guide has the slash commands.
Sign in to NotFair with the Google identity that can see your ads. Keep the Google Ads permission checked. Pick customer IDs—including MCC clients. No customer developer token is required.
Ask Claude to list connected Google Ads accounts and show each customer ID. Then request a 30-day campaign report before reviewing any write.
Bid, budget, negative, and ad changes stay staged until you approve. Claude shows the exact diff and expected impact; supported mutations keep undo metadata. Nothing hits the Google Ads API without that step.
What you get
Once connected, Claude has live access to your account. No more exporting CSVs, copying tables into chat, or working from screenshots. Ask a question, get a specific answer backed by real data.
Ask Claude what is wrong. It checks campaign structure, keyword health, search term quality, impression share, and ad copy — then gives you a prioritized fix list.
In testing, mature accounts often have clear problems hiding in search terms, structure, match types, and budget allocation. Asking "what should I fix?" surfaces them immediately.
NotFair never commits a change without your explicit approval. Claude shows you what it wants to do, you say yes or no. Human always in control.
Use the published connector in Claude.ai, Claude Desktop, and Cowork. For Claude Code, follow the separate plugin guide.
MCP tools exposed
NotFair exposes a focused set of MCP tools. Read tools give Claude live account context. Write tools let Claude propose changes — each requiring your explicit approval before execution.
| Tool | Type | What it does |
|---|---|---|
runScript | Read | Sandboxed JS with GAQL fan-out — every analytical read (campaigns, search terms, performance) goes through this one tool |
listKeywords | Read | Inspect keyword bids, Quality Scores, and impressions |
getChanges | Read | Review recorded changes and available undo details |
getRecommendations | Read | Google's optimization suggestions with estimated impact |
bulkUpdateBids | Write | Adjust keyword bids in bulk — reviewable before they apply |
pauseCampaign | Write | Pause an underperforming campaign through Claude |
addKeywordToNegativeList | Write | Block a wasted search term at the campaign or account level |
createAd | Write | Write and launch new ad copy through natural conversation |
Full tool reference at the Google Ads MCP server page.
If setup fails
These are the four failures people actually hit. Fix them, then retry the live-read prompt before approving any write.
You signed in with the wrong Google identity. Use the Workspace email that owns or can access the ads account, not a personal Gmail that was never added to Google Ads.
The MCC login has no linked clients yet. Link a client in Google Ads first, or sign in with a Google identity that has direct (non-manager) access.
The Google Ads permission checkbox was unchecked on the consent screen. Retry OAuth and leave “See, edit, create, and delete your Google Ads accounts and data” checked.
The connector or plugin is installed but the client has not reloaded tools. Fully quit and reopen Claude Desktop or Claude Code—not just a new chat. MCP tools register at startup.
Whether Claude works with Google Ads, how approval gates work, and how to set up Claude.ai versus Claude Code.
Yes. Claude works with Google Ads through MCP. The published NotFair connector for Claude (Desktop, Web, Cowork) connects via OAuth in minutes with no customer developer token. Claude can audit search terms, surface wasted spend, and stage bid, budget, negative, and ad changes that you approve before they hit the Google Ads API.
Google's official Google Ads MCP is free and read-only. NotFair is a hosted connector with approval-gated writes, MCC routing, impact review, and undo metadata where supported. Use official when you only need reporting; use NotFair when Claude must propose live account changes you still control.
Write tools stage the exact operation. Claude shows the target and intended change; nothing hits the Google Ads API until you approve. Provenance is logged, and supported mutations keep inverse-operation metadata for undo.
Claude.ai, Claude Desktop, and Cowork install the published Notfair connector from Claude's directory. Claude Code uses a separate plugin marketplace guide. Both share the same NotFair workspace and Google Ads accounts after you connect.
Ask Claude to list connected accounts, audit the last 30 days, show wasted search terms, and propose one reversible improvement with current versus proposed values. Approve only what you understand. The connector setup guide has troubleshooting.
You OAuth a Google account you already have permission to use. NotFair hosts the API integration; the MCP client does not receive your Google password or raw refresh token. Writes stay approval-gated. NotFair is independent of Google and Anthropic.
Free includes 7 unlimited days, then 300 MCP operations per month. Growth is unlimited operations at $99/mo monthly, or $950/yr (~$79/mo) annually. No credit card to start. AI-client subscriptions (Claude, Codex, Cursor) are separate. See the pricing page.
Explore the full NotFair workflow for Google Ads and Claude.
Sourced comparison of directory listings, official MCP, and reporting connectors for hosted OAuth and approval-gated writes in Claude.
Learn how NotFair's MCP server exposes your Google Ads data and actions to any MCP-compatible AI client.
The AI-powered Google Ads agent — connect your account and let Claude diagnose issues, recommend fixes, and manage approved changes through conversation.
Install the connector, verify your account, and review your first recommendation.
Published Claude connector. Google sign-in. Reviewed changes.
