Best Claude Connectors for Google Ads (2026): Compared
NotFair is the best Claude connector for Google Ads in 2026 when you need hosted OAuth and approval-gated writes—with diffs, provenance, and undo—inside Claude.ai, Claude Desktop, Claude Code, and Cowork. Install the published Notfair listing from Claude’s directory, or the Claude Code plugin, then connect Google Ads without a customer developer token. Google’s official MCP is a free, self-hosted, read-only three-tool server. Ryze AI and PaidSync publish hosted MCP connections with counted Google Ads writes and different approval models. Reporting connectors such as Adzviser and Coupler.io analyze spend in Claude but do not change campaigns. Windsor.ai and Supermetrics document directory installs plus optional campaign writes with different confirmation models. This matrix is for operators who will ship Google Ads changes from Claude.
Published
· October 5, 2026
Last verified
· October 6, 2026
Products reviewed
· 11
Author
· Tong Chen and Yuting Zhong
Our verdict
What is the best Claude connector for Google Ads in 2026?
NotFair. It is a published Claude directory connector with hosted OAuth, counted Google Ads tools, in-chat approval before every write, MCC routing, impact review, and undo metadata for supported mutations. Other options in this matrix are either read-only, self-hosted, custom-URL MCP, or reporting layers with a different write contract.
Install path, Google Ads tools, and whether Claude can write
“Claude connector for Google Ads” is not one product type. Some listings only query reports. Google’s official server is first-party and read-only. Hosted write connectors differ on whether approval is a server-side gate with a diff and undo, a paused-create plus hub setting, or a prompt the model is told to follow. “Not published” means the vendor’s public documentation does not support a more specific claim.
Published Notfair listing at https://claude.ai/directory/notfair for Claude.ai, Desktop, and Cowork. Claude Code uses the NotFair plugin marketplace. No custom MCP URL, Client ID, or Secret for the directory path.
Not a Claude directory listing. Add a local mcpServers command or a Cloud Run httpUrl in the MCP host config. Designed for developers, not one-click Claude.ai install.
Custom Claude connector (Settings → Connectors → add URL). Ryze’s Claude help states a paid Claude plan (Pro, Team, or Max) is required because the free plan does not support custom connectors.Usage source
14 Google Ads tools (8 read including GAQL and Keyword Planner; 6 approval-gated writes). Same endpoint carries 150+ tools across other platforms.
Yes — documented writes include applyRecommendation, runRawMutate, runRawMutateDelete, custom audiences, and uploadImageAsset.Capability source
Ryze documents per-write approval. runRawMutateDelete is described as irreversible and needing an item-by-item approved list. NotFair-style impact snapshots and undo are not claimed here.
claude.ai (custom connector), Claude Desktop, Claude Code, ChatGPT, Cursor, and other MCP clients
Claude directory: search PaidSync under Connectors, or add https://mcp.paidsync.ai/mcp as a custom remote connector. PaidSync’s docs state this works on every Claude plan, including Free.Usage source
152 Google Ads tools. Docs also list Meta Ads and other platforms on the same login (14 platforms).
Yes — docs describe creating, editing, pausing, enabling, or removing campaigns (Search, Display, Shopping, Video, and Performance Max), plus ad groups, keywords, bids, and reporting.Capability source
Docs say the AI assistant confirms actions before executing them. dry_run can preview a change. NotFair-style in-chat diffs, impact snapshots, and undo metadata are not documented on the pages used here.
Claude.ai (directory or custom URL), Claude Desktop, Claude Code, ChatGPT, Cursor, Windsurf, and other MCP clients PaidSync lists
Published Claude directory listing (search Supermetrics under Customize → Connectors, or supermetrics.com/products/claude). Campaign management is documented as early access on an AI-chats destination; MCP server access is a separate subscription entitlement.Usage source
Claude directory listing currently exposes discovery, query, dashboard, and campaign tools (including campaign_create, campaign_update, campaign_and_resource_get, resources_manage). A Google Ads-only tool count is not published separately from the 200+ source suite.
Yes, after Hub write access: view, create, and update campaigns on Google Ads, Facebook Ads, Microsoft Advertising, TikTok Ads, ChatGPT Ads, and Snapchat. New campaigns are created paused.Capability source
Hub write settings include options from no human approval through all live changes. Changes are logged in Campaign history on the Hub, which documents revert. This is not the same as NotFair’s in-chat diff plus Google Ads impact/undo metadata.
Claude (directory), Gemini, and the Supermetrics MCP server as documented
Claude directory install (search Windsor). Windsor’s Google Ads-to-Claude page advertises a free-forever plan with no credit card.Usage source
Google Ads-specific MCP tool count is not published as a registrar list. The Claude Google Ads page documents 2,500+ fields (495 metrics and 2,047 dimensions on that page) and 30+ write actions.
Yes — pause/enable, budgets, bidding, keywords, negative keywords, campaign/ad group/ad creation, targeting, and Customer Match, as documented on the Claude Google Ads page. New campaigns, ad groups, and ads are created paused.Capability source
Windsor states Claude waits for confirmation before each write. NotFair-style operation provenance, impact snapshots, and undo metadata are not documented on the pages used here.
Claude.ai, Claude Desktop, and Claude Code (Windsor documents a Claude Code plugin as well as the directory listing)
Claude plugin from Connectors, or paste https://mcp.portermetrics.com/mcp as a custom connector. Porter states MCP is included in the Porter plan with no extra MCP fee; Porter bills per connected data-source account.Usage source
MCP server docs list 28 tools (management, analytics, reports, actions, support) plus an action catalog of 750+ operations. A Google Ads-only tool count is not published.
Porter’s Claude help article describes the Claude connection as read-only (list_accounts, list_fields, query_data). The MCP server documentation also exposes execute_action against a catalog that includes ad-platform management. This review does not treat those two pages as the same Claude write contract.Capability source
execute_action is annotated destructive so the client can prompt. This is not documented as NotFair-style diffs, impact review, or undo.
Claude Desktop, Claude Web, Claude Code (`claude mcp add --transport http`), ChatGPT/Codex, Gemini
Claude connector from Coupler’s destination docs (Team/Enterprise may need an admin). Create a data flow with Google Ads → Claude, then install the Coupler.io connector in Claude.Usage source
Google Ads-specific MCP tool count is not published. Coupler documents predefined Google Ads report types (campaign, keyword, search terms, and others) rather than a Google Ads API tool registrar.
Public Google Ads MCP and Claude destination docs describe asking questions and receiving answers. They do not document Ads API campaign writes.Capability source
No Google Ads write lifecycle is published on the pages used here. Data freshness is documented as syncing every 15 minutes (cached).
Claude Web, Desktop, mobile, Cowork, and Claude Code with a single web connector, per Coupler’s Claude destination docs
Open Adzviser in Claude’s Connector Directory and connect. Adzviser documents a $0.99 14-day trial; MCP is included on standard plans after trial.Usage source
Google Ads-specific MCP tool count is not published. Adzviser documents 54 reporting connectors, including Google Ads campaigns, spend, conversions, ROAS, and search terms.
No — Adzviser documents read-only reporting. Campaign edits and write-backs are explicitly not included.Capability source
No mutation surface. Analysis only.
Claude directory; other clients via https://mcp.adzviser.com/http
Custom connector: paste the Composio MCP URL in Claude Customize → Connectors. Hobby plan documents 100,000 tool calls/month with up to 20,000 through Composio-managed apps.Usage source
9 Google Ads tools on the current toolkit page: customer lists, get campaign by id/name, list accessible customers, mutate ad groups, mutate campaigns, and Search Stream GAQL.
Yes — Mutate Campaigns and Mutate Ad Groups are listed. FAQ tells operators to keep an approval step in the prompt for side-effecting actions.
Managed auth and audit trail are documented. In-chat diffs, impact review, and undo are not documented as a Google Ads-specific safety lifecycle. Approval is described as a prompt/agent practice.
Claude Web, Desktop, Cowork, Claude Code, Cursor, ChatGPT, and other frameworks on the toolkit page
Hosted: create an MCP server at mcp.zapier.com, add Google Ads tools, then connect Claude with the generated URL. Local: stdio MCP in Claude Desktop/Code. Claude.ai custom MCP access depends on plan; Zapier notes organization-owner limits for adding servers.Usage source
The Zapier Google Ads connector README describes 13 tools across account hierarchy, GAQL search, campaigns/ad groups/ads reads, performance reports, and managing campaign status, budgets, and conversion actions.
Yes on the connector package — writes go through per-resource mutate endpoints for campaign status, budgets, and conversion actions as documented in that README.
NotFair-style in-chat diffs, impact review, and undo are not documented on the Zapier MCP help article or connector README used here.
Claude web, Desktop, and Code, plus Cursor and other Streamable HTTP clients on Zapier’s MCP help article
NotFair’s Google Ads image tools upload supplied PNG/JPEG assets. Video workflows use existing YouTube video IDs; NotFair does not upload video files to YouTube. Competitor creative claims are taken only from the linked public docs.
Operating model
Operating model: credentials, routing, and what the connector is actually for
Server
Best for
Delivery
Credentials
Safety lifecycle
Multi-account
Clients
NotFair
Our verdict
Operators who want hosted OAuth and approval-gated Google Ads writes in Claude
Hosted remote MCP; published Claude directory listing plus Claude Code plugin
Hosted OAuth; no customer Google Ads developer token
Server-side approval gate with diffs before live writes; operations are logged; supported mutations include impact review and undo.
Manager-account discovery and explicit per-call account routing
Claude.ai, Claude Desktop, Claude Cowork, and Claude Code
Google official MCP
Developers who will self-host a first-party, read-only Google Ads server
Self-hosted local stdio (pipx) or Cloud Run HTTP
Google Cloud project with Ads API access plus OAuth 2.0 or application default credentials. Google documents that developer tokens were sunset on 9 September 2026 for this server.
No mutation surface to guard
Lists directly accessible customers; MCC child access uses GOOGLE_ADS_LOGIN_CUSTOMER_ID. Infrastructure is yours to maintain.
MCP hosts you configure (examples in Google’s guide include Gemini settings.json)
Ryze AI
Teams adding a custom remote MCP URL for Google Ads plus other marketing tools
Hosted remote MCP at connector.get-ryze.ai/mcp
Hosted Google sign-in; Ryze documents no customer developer token or Cloud project
Vendor documents approval-gated writes; deletions are called out as irreversible
Workspace selection during OAuth; MCC-aware account tools are documented on the Google Ads MCP page
Claude, ChatGPT, Claude Code, Cursor, Windsurf, VS Code, and other MCP clients
PaidSync
Teams adding a hosted Google Ads MCP from Claude’s connector directory or a custom URL
Hosted remote MCP at https://mcp.paidsync.ai/mcp
Hosted Google OAuth; PaidSync documents no customer developer token or Cloud project. Docs: an API key works for reports and dry_run preview; applying a Google Ads change requires the sign-in option. Free 15 tasks/month; Pro from $99/month for 600 tasks.
Prompt-level confirmation and dry_run preview; not a NotFair-style server-side Google Ads approval gate with impact/undo
Multiple Google Ads accounts and MCC manager accounts under one PaidSync account are documented
Claude Desktop, claude.ai, ChatGPT, Perplexity, Cursor, Windsurf, Claude Code
Supermetrics
Teams that already use Supermetrics reporting and want Claude to query or manage campaigns through that layer
Claude directory connector plus a separate Supermetrics MCP server for technical hosts
Supermetrics account/team OAuth; Google Ads connected as a data source. Write access is granted in the Supermetrics Hub.
Paused-first creates; Hub-configurable approval; Campaign history on the Hub. Early-access campaign management with documented Google Ads keyword-add caveats.
Account selection in chat; write access only on data-source connections you own
Claude, ChatGPT, Gemini, Microsoft Copilot, and MCP hosts documented by Supermetrics
Windsor.ai
Teams blending Google Ads with many other sources in Claude, with optional write actions
Hosted MCP; published Claude directory listing
Windsor account plus Google Ads OAuth at onboard.windsor.ai
Confirmation before writes; paused-first creates. Claude.com currently annotates the Windsor connector capabilities as Read.
MCC coverage is documented on the Google Ads-to-Claude page
Claude Web, Desktop, Code, ChatGPT, Copilot, and other MCP clients per Windsor MCP docs
Porter Metrics
Teams querying marketing data in Claude through a Porter workspace
Remote MCP at mcp.portermetrics.com/mcp; Claude plugin or custom connector
Porter account (Google SSO documented) plus connected Google Ads in Porter
Claude help: read-only. MCP server: client confirmation on destructive execute_action. Do not assume in-chat Google Ads undo.
list_accounts over Porter-connected sources; 32 connectors documented on the MCP server page
Claude Desktop/Web/Code, ChatGPT, Gemini, MCP Inspector
Coupler.io
Teams that want Claude to query a Coupler data flow rather than the live Ads API
Managed MCP via Coupler data flows with Claude as a destination
Coupler.io account; Google Ads connected as a source in a data flow
Reporting/analysis layer; no published Google Ads mutation gate
400+ Coupler sources can share one MCP; Google Ads is one source among them
Claude, ChatGPT, Perplexity, Cursor, and other destinations Coupler documents
Adzviser
Teams that want hosted, read-only Google Ads reporting in Claude’s directory
Hosted remote MCP; published Claude directory listing
Adzviser workspace OAuth; Google Ads connected inside Adzviser
Read-only by design
Per-workspace connected sources
Claude, ChatGPT, Gemini, OpenClaw, n8n, and other MCP clients Adzviser lists
Composio
Builders connecting many app toolkits, including Google Ads, through Composio MCP
Hosted MCP / Tool Router; custom Claude connector URL from Composio Connect
Composio-managed Google OAuth (optional custom OAuth app in the Composio dashboard)
Prompt-level approval guidance; not a NotFair-style server-side Google Ads approval gate
Multiple named Google Ads connections are documented
Claude, ChatGPT, Cursor, and the other agent frameworks listed on composio.dev/toolkits/googleads
Zapier
Teams routing Google Ads through Zapier MCP or a local Google Ads connector package
Hosted Zapier MCP server (mcp.zapier.com) or local `npx @zapier/google-ads-connector mcp`
Zapier-managed Google OAuth plus an app-level developer token (Zapier-supplied or env vars), per the Google Ads connector README
Standard Zapier MCP tool access; no published Google Ads approval/undo lifecycle comparable to NotFair
Account-hierarchy navigation including manager and client accounts is documented in the connector README
Claude (web, Desktop, Code), Cursor, Copilot Studio, VS Code, Windsurf, per Zapier MCP help
NotFair publishes this comparison and is therefore not a neutral party. Source links are public so every row can be challenged. Cross-platform field or connector totals are not treated as Google Ads-specific tool counts. Other hosted MCP products exist; they are covered on the Google Ads MCP servers comparison and are not recommended here.
Testing method
A benchmark that can be rerun
We review the Claude install path, Google Ads tool surface, write contract, approval/recovery path, and account routing. Marketing claims without a public document, schema, or observable flow are not treated as verified capabilities. Competitor rows were checked against live public docs on 6 October 2026.
Is the connector a published Claude directory listing, a custom remote MCP URL, a local stdio/Cloud Run server, or a plugin?
02
Claude surfaces
Does the same connection work in Claude.ai, Claude Desktop, Claude Cowork, and Claude Code?
03
Tool depth
How many tools are Google Ads-specific rather than a cross-platform reporting total?
04
Writes
Can Claude change live campaigns from chat, or is the connector reporting-only?
05
Safety
Are writes previewed with a diff, bound to explicit approval, logged with provenance, and reversible where the platform supports it?
06
Credentials
Can a non-developer connect with hosted OAuth, or must they supply Cloud/API credentials and operate the runtime?
07
Account routing
Can the agent discover and explicitly target the intended ad account?
08
Capacity
What monthly operation or plan limits are published?
09
Honesty about the job
Does the vendor document a write lifecycle, or only analysis of synced reports?
Test boundary
NotFair was verified against its production Google Ads registrar, hosted OAuth, published Claude directory listing, and Claude Code plugin path. Competitor rows are based on linked public documentation; no competitor Claude workspace was connected and no competitor write was executed for this review.
Decision guide
Choose by operating model
Choose NotFair
You want Claude.ai, Desktop, Cowork, or Code to read live Google Ads and stage approval-gated writes with diffs, provenance, impact review, and undo—without operating Google Cloud credentials or a custom MCP URL.
When Google’s official read-only MCP is enough
You only need free, first-party reporting, already have a Google Cloud project, and will run a local stdio or Cloud Run server yourself. The current public tool surface is three read-only tools. It is not a write path and is not a Claude directory listing.
Reporting-only connectors in this matrix
Adzviser and Coupler.io document Google Ads analysis inside Claude without campaign writes. That is a reporting job. This review recommends NotFair when Claude must change Google Ads, not those reporting layers.
Other operating models in this matrix
Windsor.ai, Supermetrics, Ryze AI, PaidSync, Porter Metrics, Composio, and Zapier publish Claude or MCP connections with different install paths, tool inventories, and write contracts. They are described factually below. This review recommends NotFair for accountable hosted execution in Claude.
Install the published Notfair connector from Claude’s directory, or the NotFair plugin in Claude Code.
Sign in to the NotFair workspace and connect Google Ads through hosted OAuth. A customer developer token is not required.
Ask Claude to list accounts and run a 30-day audit before any write.
A proposed write shows the target and intended change. Execution waits for explicit approval.
The operation records author, ID, timestamp, and provenance. Supported mutations include impact review and undo metadata.
Remote endpoint
https://notfair.co/api/mcp/notfair
Public verification prompts
Use the same prompts on every server
01
List every Google Ads-specific tool in this Claude connection and say which ones can write.
02
Which Claude surfaces is this connector installed on: claude.ai, Desktop, Cowork, and Code?
03
Show the exact install path. Is it a published Claude directory listing, a custom MCP URL, or a self-hosted server?
04
Show my plan, monthly operation limit, operations used, and operations remaining.
05
List every accessible Google Ads account and identify how targeting works.
06
Audit the last 30 days and show the evidence behind the three highest-impact problems. Do not change anything.
07
Propose one reversible improvement with current versus proposed values. Do not execute until I approve.
08
Show the exact preview or diff before changing a budget.
09
After a write, return the operation ID, author, timestamp, and the supported reversal. Do not claim undo unless this platform provides it.
Best Claude connector for Google Ads FAQ
Direct answers for the query “best Claude connector for Google Ads (2026)”—install path, writes, and how NotFair differs from official MCP and reporting connectors.
What is the best Claude connector for Google Ads in 2026?
NotFair is the best Claude connector for Google Ads when the job is live account work with approval-gated writes. It installs from Claude’s published directory (or the Claude Code plugin), hosts OAuth so you do not bring a developer token, exposes counted Google Ads tools, and requires explicit approval before writes, with impact review and undo on supported mutations. Google’s official MCP is the free read-only self-hosted alternative. Reporting connectors analyze spend without changing campaigns.
Does NotFair work in Claude.ai, Claude Desktop, Claude Code, and Cowork?
Yes. Claude.ai, Claude Desktop, and Cowork install the published Notfair connector from Claude’s directory. Claude Code uses the NotFair plugin marketplace. Both paths share the same NotFair workspace and Google Ads accounts after you connect.
Is Google’s official Google Ads MCP a Claude connector?
It is a first-party MCP server, not a published Claude directory listing. Google’s current public release is read-only with three tools (list_accessible_customers, search, get_resource_metadata), runs as local stdio or Cloud Run HTTP, and needs a Google Cloud project plus OAuth or ADC. Developer tokens were sunset on 9 September 2026 for that server. It cannot modify bids, pause campaigns, or create assets.
Can Adzviser, Coupler.io, or similar reporting connectors change Google Ads from Claude?
Not according to the public docs used for this review. Adzviser describes a hosted, read-only reporting MCP and states campaign edits are not included. Coupler.io’s Google Ads MCP page describes asking questions and receiving answers from synced data (15-minute cache), not Ads API writes. Use NotFair when Claude must stage live changes.
How is NotFair different from Windsor.ai or Supermetrics in Claude?
Windsor’s Google Ads-to-Claude page documents 2,500+ fields and 30+ write actions with confirmation, and new campaigns created paused. Supermetrics documents a Claude directory connector with campaign create/update tools, paused-first creates, hub write-access settings (including an option with no human approval), and campaign history undo on the Hub. NotFair is a Google Ads-specific counted tool surface with a server-side in-chat approval gate, diffs, operation provenance, impact review, and undo metadata—not a 200+ source reporting suite.
How do I install NotFair as a Claude Google Ads connector?
Open the published Notfair listing at https://claude.ai/directory/notfair, choose Connect, and complete NotFair sign-in plus Google Ads OAuth. No MCP URL, Client ID, or Secret is required for that path. Claude Code users follow the plugin setup guide instead.
What does NotFair cost for Claude Google Ads work?
Free includes 7 unlimited days, then 300 MCP operations per month. Growth is $99/mo monthly, or $950/yr (~$79/mo) annually with unlimited operations. No credit card to start. Claude’s own subscription is separate.
Was every competitor tested in a live Claude workspace?
No. This review combines public documentation with live production verification of NotFair. Competitor behavior is labeled from vendor documentation or public source listings.
Claude landings, setup, and MCP benchmark
Install NotFair, then use the sourced MCP-server matrix when you need tool-count and asset-level evidence beyond Claude-specific install paths.
