Claude is already good at reasoning about advertising. It can critique your keyword list, rewrite your headlines, and explain why your CPCs crept up. What it cannot do out of the box is see your Google Ads account, and it certainly cannot touch it. Connect Google Ads to Claude and the conversation changes shape entirely: "why is this keyword bleeding money" becomes a question Claude answers from your actual account data, and "launch a Search campaign on those five keywords at $40 a day" becomes an instruction, not a to-do item.
This guide walks through the full setup using AdWhispr's MCP server, which we build. We will also cover the other ways to connect Google Ads to Claude, because a few of them are genuinely good at what they do, and it helps to know which job each one is built for. The short version of the difference: reporting connectors pipe your metrics into Claude for analysis, official platform MCPs manage your account, and AdWhispr is the only connection that combines your account, competitor intelligence, and the ability to launch campaigns in one place.
What you need
Two things, both free to start:
- An AdWhispr account. The free plan needs no credit card and includes enough agent calls to confirm everything works and run a real research pass.
- Claude. The connector works in Claude on the web, the Claude desktop app, and Claude Code. Any plan that supports custom connectors will do.
You will also want access to a Google Ads account, but that comes later. The Claude connection and the ad account connection are two separate steps, and the first one works fine without the second.
How to connect Google Ads to Claude, step by step
The connection runs through MCP (Model Context Protocol), the standard that lets Claude call external tools. AdWhispr exposes its tools through a hosted MCP server, so there is nothing to install for the standard route.
Step 1: Add AdWhispr as a custom connector
In Claude, go to Settings, then Connectors, then Add, then Add custom connector. Paste this as the connector URL:
https://adwhispr.com/api/mcp
Give it the name AdWhispr so it is easy to spot in the tool list later.
Step 2: Authorize the connection
Click Connect. Claude opens an AdWhispr sign-in window. Approve it, and the connector goes green.
This is a normal OAuth handshake. AdWhispr never sees your Claude conversation, and Claude never sees your AdWhispr password.
Step 3: Confirm it works
Start a new chat and ask Claude to list its AdWhispr tools. You should see research tools, creative tools, and the Google execution tools: connect_ad_account, launch_search_campaign, launch_pmax_campaign, get_account_performance, and the campaign management set. If Claude answers from general knowledge instead of calling a tool, start a fresh chat and name AdWhispr explicitly in the prompt.
Using Claude Code instead? One command replaces the settings screen: claude mcp add --transport http adwhispr https://adwhispr.com/api/mcp. And if you prefer a local server config for Claude Code or the desktop app, npx adwhispr-mcp-server config emits the config block. We wrote a dedicated walkthrough in how to connect your ad accounts to Claude Code.
Link your Google Ads account
This is the step that turns Claude from an analyst into an operator. Do it only for an account you are happy to have an assistant work on.
- Ask Claude: "Connect my Google Ads account." That runs
connect_ad_account, which returns an authorization link. - Approve access in Google. Open the link, sign in with the Google account that has access to your ads, and approve the permissions. This is standard OAuth: AdWhispr receives scoped access to the ad account, never your Google password, and it cannot reach other Google services.
- Confirm which accounts are available. Ask "Which ad accounts can I launch into?" That runs
list_ad_accounts. If you manage several accounts under one login, this is where you confirm you are pointing at the right one.
You can revoke access at any time from your Google account's connected-apps settings, which immediately stops any further campaign actions. The full walkthrough with screenshots lives at how to connect your Google Ads account.
Six prompts to run on day one
Start with reads. They are the fastest way to feel what a Claude Google Ads MCP connection actually does, and they touch nothing.
1. Find the wasted spend.
Pull my account performance for the last 30 days and tell me
where I'm wasting money. Be specific about which keywords.
get_account_performance includes per-keyword diagnostics, so Claude can point at the exact keywords burning budget without converting, not just wave at a campaign total.
2. Diagnose quality scores.
Which of my keywords have low quality scores, and what is
dragging each one down?
The same diagnostics surface quality score components and first-page bid estimates per keyword, which is the difference between "improve your ads" and "this keyword's landing page experience is the problem."
3. See what a competitor bids on.
What keywords is [competitor] bidding on that I'm not?
research_competitor_keywords pulls competitor keyword intelligence conversationally. This is the tool that reporting connectors and official platform MCPs simply do not have. We wrote a full post on competitor keyword research with an AI assistant.
4. Research before you spend.
Research keywords around [my product category], show me search
volumes, and pick the five that fit my brand best.
research_keywords works from a seed term or your own product, so the campaign you launch next is built on data instead of guesses.
5. Check their creative, not just their keywords.
Show me [competitor]'s longest-running Meta ads and summarize
the angles they keep paying for.
The Meta and TikTok ad library research runs through the same connector. Keywords tell you where competitors spend; long-running creative tells you what messaging survives. If you want the fuller picture of who you are actually bidding against, pair this with our guide to Google Ads Auction Insights.
6. Launch.
Launch a Search campaign on those five keywords at $40 a day,
targeting the US.
launch_search_campaign builds the campaign, and launch_pmax_campaign does the same for Performance Max. Check the budget, geography, and keywords on what it assembled before you approve it. Research to live campaign, one conversation.
Other ways to connect Google Ads to Claude
Honesty section. The search results for this topic are full of data connectors, and for the job they do, they work.
Reporting connectors: Windsor.ai, Porter Metrics, Supermetrics, Zapier. These pipe your Google Ads metrics into Claude (or into a warehouse or sheet Claude can read) for analysis. If your only goal is "let Claude analyze my numbers," they do that job, and some cover dozens of ad platforms in one subscription. Where they stop is exactly where the interesting part begins: they are one-directional. Claude can see your data and tell you what to change, and then you go change it yourself in Ads Manager.
Google's official MCP. Google offers an official MCP server for the Google Ads API. It manages your own account, and being first-party is a real advantage for account operations. What it has no concept of is anyone else's account: zero competitor data, no ad library research, no competitor keyword intelligence. That gap comes up constantly among practitioners running ads through Claude, because "manage my account" was never the whole job. Knowing what to run is.
AdWhispr. Your account (performance reads, per-keyword diagnostics, keyword research), plus competitor intelligence (Meta and TikTok ad libraries, competitor keywords), plus execution (Search and PMax campaign launch, budgets, pause and resume) behind one connector.
| Reporting connectors | Google's official MCP | AdWhispr | |
|---|---|---|---|
| Read your account metrics | Yes | Yes | Yes |
| Per-keyword diagnostics in chat | Partial, depends on setup | Yes | Yes |
| Competitor keyword research | No | No | Yes |
| Meta / TikTok ad library research | No | No | Yes |
| Launch campaigns from chat | No | Yes | Yes |
| Best for | Dashboards and reporting | Account operations | Research to launch in one loop |
For a deeper buyer's checklist on the whole category, see our Google Ads MCP guide.
A note on safety
Connecting Claude to a live ad account sounds scarier than it is in practice, because nothing here is autonomous. Campaign launches, budget changes, pauses, everything that touches money happens only when you ask for it. You name the daily budget in the instruction, you see the assembled campaign before it goes live, and nothing spends without your instruction. Reading competitor ads uses public ad-library data and touches no account at all. And the connection itself is revocable in one click from Google's side.
FAQ
Is there an official Google Ads MCP?
Yes. Google offers an official MCP server for the Google Ads API, and for pure account management it is a legitimate option. Its limitation is scope: it can only see the account you connect. It has no competitor data of any kind, no ad library research, and no keyword intelligence about anyone but you.
Can Claude launch Google Ads campaigns?
Yes, through an MCP server with execution tools. With AdWhispr connected, launch_search_campaign and launch_pmax_campaign create real Search and Performance Max campaigns from chat, both generally available. Reporting connectors like Windsor.ai or Supermetrics cannot do this; they are read-only by design.
Do I need to install anything to connect Google Ads to Claude?
Not for the standard route. AdWhispr's MCP server is hosted, so on Claude web or desktop you paste https://adwhispr.com/api/mcp as a custom connector URL and authorize via OAuth. Claude Code users add it with one command, and npx adwhispr-mcp-server config generates a local config block if you prefer that route.
Can it spend money without me approving it?
No. You set the daily budget in the instruction, the campaign runs on that budget, and nothing launches without you asking for it. You see what was built before it goes live, and you can pause, resume, or change budgets from the same chat.
Where this leaves you
Most ways to connect Google Ads to Claude give you a smarter dashboard: your numbers, explained well. That is useful, and if reporting is the whole job, the connectors that specialize in it are fine choices. But the loop that actually moves an account forward is research, then decision, then execution, and today only one connection puts all three in the same conversation. Claude reads your per-keyword diagnostics, checks what your competitors bid on and what creative they keep paying for, and then launches the campaign you agreed on, without you opening Ads Manager once.
Start free at adwhispr.com, no card required, and run your first account read today.