Setup in five steps
Connect Google Ads in Whathead
On the Integrations page, sign in with a Google user that has access to the Google Ads accounts you want Claude to work on, including any manager account above them.
Open Customize > Connectors in Claude
On claude.ai or Claude Desktop, click "+ Add", then "Add custom connector".
Enter the Whathead URL
Name it Whathead, paste https://www.whathead.com/mcp, click "Continue", review the detected sign-in, click "Continue", then "Add".
Authorize the workspace
Sign in to Whathead in the window that opens and approve. Claude keeps the connection for later chats.
Enable it per conversation
In a chat, click "+" in the lower left, choose "Connectors" and switch Whathead on.
Before you start
Your Whathead workspace needs a plan with MCP: MCP Actions ($39/month), Operator Bundle ($65) or Agency ($249). The $29 Builder plan has no MCP. The 14-day trial allows 1 ad account, 200 MCP reads, 10 write operations and 2 live actions.
Google Ads is not in the Whathead visual builder yet, so Google work happens through chat or the in-app Google reporting page. To limit what Claude can touch, restrict the connector to chosen accounts or tools on /connectors/mcp.
Prompts to paste into Claude
Audit Google Ads account [customer ID] for the last 30 days: cost, conversions, CPA and conversion value per cost by campaign. Flag campaigns limited by budget.
List search terms from the last 30 days that cost more than $50 with zero conversions, grouped by campaign.
Add those search terms as exact-match negatives to a shared list called [name]. Dry run only.
Show month-to-date cost per campaign against its daily budget times days in the month. Flag anything off pace by more than 10%.
Compare CTR for each Demand Gen and YouTube ad in the last 14 days with the previous 14 days and list drops over 25%.
Get keyword ideas for "[seed keyword]" in [country] with average monthly searches and top-of-page bid ranges.
Create a paused Search campaign for [product]: $50 daily budget, one ad group, 10 phrase-match keywords and one responsive search ad. Validate it first.
Raise the budget of campaign [name] by 15% and show me the request before sending it.
Pause keywords with over 1,000 impressions and CTR under 1% in the last 30 days. Wait for my go-ahead.
List open recommendations for this account and tell me which are worth applying and why.
Check which conversion actions are primary and whether any recorded zero conversions in the last 14 days.
What Claude can and cannot do in Google Ads
| Task | Claude via Whathead | Notes |
|---|---|---|
| Run reports with GAQL | Yes | Campaigns, ad groups, keywords, search terms, assets, segments |
| Create campaigns, ad groups, ads and keywords | Yes, dry run first | Ask for PAUSED status to stage them |
| Change budgets, bids and statuses | Yes | With your approval |
| Shared negative lists, assets, Performance Max asset groups | Yes | Through the native v23 services |
| Keyword Planner ideas and Reach Plan forecasts | Yes | Planning reads, no spend |
| Conversion actions, uploads and adjustments | Yes | Check consent and click IDs before uploading |
| Billing setups, budget proposals, removals | Only with confirmed: true | Flagged as confirmation-required RPCs |
| Publish Google campaigns from the visual builder | Not yet | Use chat or the Google reporting page |
| Skip Google policy review | No | Ads are reviewed as usual |
How changes are approved
Each Google Ads write defaults to dry_run: true, so Claude shows the exact v23 request before anything changes. To execute it, Claude calls again with dry_run: false. RPCs that delete, remove, book, move, end or change billing also need confirmed: true, and idempotency keys keep retries from duplicating work. In Claude, keep write tools on "Needs approval" so you see each call.
Troubleshooting
If something does not work:
- Claude cannot find an account: give it the 10-digit customer ID and check that the Google user you connected can open that account.
- A "requires confirmed: true" message is expected for billing and removal RPCs. Reply to confirm if you meant it.
- "Your plan does not include connectors" means the workspace has no MCP plan.
- Sign-in fails: use https://www.whathead.com/mcp exactly. If the default OAuth client option fails, choose "Register automatically"; Whathead supports dynamic client registration.
Frequently asked questions
How is this different from Google's official Google Ads MCP server?
Google's server (googleads/google-ads-mcp, v0.0.6 from 2 November 2026) is free and self-hosted. It reads through GAQL and its few writes cover assets, video uploads and labels; it cannot change budgets or campaign status. Whathead is hosted, uses OAuth and covers budgets, bids, keywords and campaigns, plus other ad platforms.
Do I need a Google Ads developer token?
No. Whathead calls the Google Ads API for you after you connect Google on the Integrations page.
Can Claude manage accounts under a manager (MCC) account?
Yes, if the Google user you connected has access to them. Ask Claude to list accessible accounts first.
Which Claude plans work?
Custom connectors work on Free (one custom connector), Pro, Max, Ultra, Team and Enterprise. On Team, only Owners and Primary Owners can add one.
Can Claude move a Meta campaign into Google Ads?
Yes. Whathead cross-platform transfer supports Google as a target and creates the copy paused by default.
Run it from one workspace
Every plan starts with a 14-day free trial. Only successful live work is metered.
Sources
- Claude Help Center: custom connectors using remote MCP (support.claude.com)
- Claude Help Center: use connectors (support.claude.com)
- Google Ads MCP server (official, GitHub) (github.com)