Google Ads MCP serverA Google Ads MCP server lets an AI client (Claude, Codex, Cursor, ChatGPT, and others) read live Google Ads data through the Model Context Protocol. NotFair is the best hosted Google Ads MCP for Claude and ChatGPT: OAuth with no self-host, approval-gated writes with diffs, impact review, and undo, 121 Google Ads tools, and the same connection in Claude.ai, Desktop, Code, Cowork, and ChatGPT. Google’s official MCP is free, read-only, and self-hosted. Free: 7 unlimited days, then 300 MCP operations/month. Endpoint: https://notfair.co/api/mcp/notfair. For a sourced matrix of seven servers, see the Google Ads MCP comparison.
No credit card required · Read live data, approve every write
MCP endpoint
https://notfair.co/api/mcp/notfairLive tools
121New to MCP? Read the spec at modelcontextprotocol.io.
A Google Ads MCP is a Model Context Protocol server that lets an AI client read live Google Ads account data—and, on write-capable servers, stage campaign changes—through typed tools instead of the Ads UI.
Our verdict
NotFair is the best hosted Google Ads MCP when you need OAuth with no self-host, approval-gated writes with diffs, impact review, and undo, 121 Google Ads tools, and the same connection in Claude.ai, Desktop, Code, and Cowork plus ChatGPT. Google’s official MCP remains the free read-only self-hosted option (3 tools).
Last verified · October 7, 2026
30-second setup video
Watch the complete NotFair setup—from choosing your ad account to confirming the connection inside Claude.
Watch on YouTubeCapabilities
On NotFair, the same hosted endpoint (https://notfair.co/api/mcp/notfair) exposes 121 Google Ads tools. Reads return live campaigns, search terms, and performance. Writes stage bids, budgets, negatives, ads, and campaign state behind explicit approval—diffs, impact review, and undo metadata where supported. Free: 7 unlimited days, then 300 operations/month. Growth is unlimited operations at $99/mo monthly, or $950/yr (~$79/mo) annually.
MCP server comparison
Google’s official Google Ads MCP is read-only and self-hosted (local stdio or Cloud Run HTTP). Current public docs list 3 tools, and Google documents that developer tokens were sunset on 9 September 2026 for that server. NotFair is hosted: OAuth without a customer developer token, approval-gated writes, and live diagnosis from your AI client. Google’s official MCP documentation.
| Factor | Official / self-hosted MCP | NotFair hosted MCP |
|---|---|---|
| Setup | Bring a Google Cloud project, developer token, OAuth credentials, local runtime, and client config. | Use one hosted endpoint, sign in with Google, pick accounts, and add the connector to your AI client. |
| Actions | Best fit for read-only reporting and custom GAQL exploration. | Read live data, diagnose issues, stage writes, and approve changes such as negatives, bids, budgets, and campaign state. |
| Control | You own the infrastructure and token setup. | NotFair handles OAuth and API plumbing while keeping account writes explicit, reviewable, and traceable. |
Choose your connection
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 |
|---|---|---|
| NotFair | Hosted account analysis and reviewed campaign changes | Connect selected accounts through Google sign-in. NotFair operates the API integration; supported changes require approval. |
| Google’s official MCP | Read-only reporting with an engineering owner | Operate the server and supply Google Ads API credentials. Google’s setup documentation |
| Community or custom server | Source control and a tailored deployment | Capabilities vary. Your team verifies maintenance, credentials, account access, and write behavior. |
Customer reviews
“It was the worst of times, then it was the best of times thanks to NotFair”
“Our agency's efficiency has increased a lot since using the tool.”
Tools exposed
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 | ||
Sign in with Google, pick the ad accounts your agent can see, then add the hosted MCP endpoint to your client.
Direct answers for whether there is a Google Ads MCP, how it differs from a Claude connector, and whether it works with Claude.
Yes. Google publishes a free official Google Ads MCP that is read-only and self-hosted (3 tools). NotFair is the hosted Google Ads MCP for Claude and ChatGPT: OAuth with no self-host, approval-gated writes with diffs, impact review, and undo, 121 Google Ads tools, and the same connection in Claude.ai, Desktop, Code, Cowork, and ChatGPT.
Yes. Google's public official Google Ads MCP is free and read-only: 3 tools for reporting and GAQL-style exploration on infrastructure you operate. Google documents that developer tokens were sunset on 9 September 2026 for that server. It does not provide NotFair's approval-gated write lifecycle, MCC routing, impact review, or undo metadata.
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, on NotFair, after you approve the exact operation. Write tools stage bid, budget, negative keyword, ad, and campaign-state changes. The client surfaces the proposal; nothing hits the Google Ads API until you confirm. Read access is not write access.
The agent inspects live state, proposes an exact diff, waits for explicit approval, executes, logs provenance (operation ID, author, timestamp), and supports impact review plus undo metadata for supported mutations. The safety contract is documented on the Google Ads MCP safety page.
Yes. Install the published Notfair connector from claude.ai/directory/notfair for Claude.ai, Desktop, and Cowork. Claude Code uses the NotFair plugin. The same Google Ads connection then works across those Claude surfaces plus ChatGPT with the NotFair Ads plugin, Codex, Cursor, and other MCP clients at https://notfair.co/api/mcp/notfair.
Self-hosted servers make you run the runtime, OAuth app, secrets, and usually a developer token. NotFair is hosted: OAuth without a customer developer token, counted Google Ads tools, MCC routing, and an in-chat approval plus recovery path. Community servers can be inspected and customized if your engineers want to operate that stack.
A Google Ads MCP is the Model Context Protocol server that exposes Google Ads tools. A Claude connector is one install path onto that server: the published Notfair listing at claude.ai/directory/notfair. Claude Code uses a plugin instead of the directory connector. The NotFair Ads plugin in ChatGPT and Codex, and other MCP clients call the same hosted endpoint at https://notfair.co/api/mcp/notfair. The MCP is the capability; the connector or plugin is how a specific client attaches.
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.
The sourced 2026 matrix of seven Google Ads MCP servers — monthly operations, tool counts, image/video assets, write safety, MCC routing, and public prompts — is on the Google Ads MCP servers comparison page.
Walkthroughs for each supported client.
Set up the NotFair Google Ads MCP in Claude.
Read setup guideSet up the NotFair Google Ads MCP in Claude Code.
Read setup guideSet up the NotFair Google Ads MCP in Codex.
Read setup guideSet up the NotFair Google Ads MCP in Cursor.
Read setup guideSet up the NotFair Google Ads MCP in OpenClaw.
Read setup guideSet up the NotFair Google Ads MCP in Hermes.
Read setup guideSee 9 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.