Can Claude actually run my Google Ads, or just read them?

Both, depending on how you connect it. Google publishes an official Google Ads MCP server that is read-only. With a ClientFuse connector key you can additionally enable write actions — creating search campaigns, adding keywords and negatives, pausing or resuming campaigns, and changing budgets. Write actions are off by default and every change requires your explicit confirmation.

Do I need to give Claude my Google password?

No. You authorize access with Google OAuth, the same mechanism agencies use. Claude never sees your password, and you can revoke the connection at any time.

MCP (Model Context Protocol) is an open standard that lets AI assistants call external tools through a structured, permission-scoped interface. An MCP server for Google Ads exposes your ad data and controls as tools Claude can call, instead of you copying numbers into a chat window.

Can Claude spend my money without asking?

No. With ClientFuse, write actions must be explicitly enabled, every change runs as a dry run first, new campaigns are always created paused so a human has to activate them, budget changes are capped, and each executed action is written to an audit log with the confirmation you gave.

Does this work with multiple Google Ads accounts?

Yes. One connector covers every Google Ads and Meta account connected to your ClientFuse profile, which is the main practical difference from a single-account setup — useful if you manage ads for several clients or brands.

How to Have Claude Run Your Google Ads (2026 Guide)

Short answer

Connect Claude to Google Ads with an MCP server. Google publishes an official one that is read-only. To let Claude actually change things — build campaigns, add negatives, adjust budgets — use a connector that supports write actions, such as ClientFuse, and keep the human approval step switched on. Setup takes about two minutes and never involves sharing your Google password.

What you need

A Google Ads account you have access to
Claude — claude.ai, the Claude desktop app, or Claude Code
An MCP server that connects the two (the piece this guide covers)

What MCP actually is

MCP, the Model Context Protocol, is an open standard for letting AI assistants call real tools instead of guessing. An MCP server for Google Ads exposes your accounts as structured, permission-scoped functions — list accounts, pull performance, fetch search terms, add a negative keyword — that Claude can call directly.

The practical difference: instead of exporting a report and pasting it into a chat, you ask a question and Claude queries the live account itself.

Two ways to connect

Option 1: Google's official MCP server (read-only)

Google open-sourced an official Google Ads MCP server. It is free and self-hosted, and it is currently read-only — you can pull performance data, analyse campaigns and generate reports, but you cannot create or modify anything through it. If all you want is analysis, this is a perfectly good place to start.

Option 2: A hosted connector with write actions

If you want Claude to make changes — or you manage more than one account — you need a connector that supports writes and multi-account access. ClientFuse is hosted (nothing to run yourself), covers Google Ads and Meta in one connection, and gates every write behind your explicit approval.

Setting it up

In claude.ai

Connect your Google Ads account to ClientFuse with Google OAuth — no password is shared.
In ClientFuse, open Settings → Integrations and create a connector key. It is shown once, so copy it.
In claude.ai go to Settings → Connectors → Add custom connector.
Paste your connector URL and save.

In Claude Code

One command:

claude mcp add clientfuse-ads --transport http \
  https://app.clientfuse.io/api/mcp \
  --header "Authorization: Bearer YOUR_KEY"

The same server works in Cursor and any other MCP-compatible client.

What to ask once it is connected

Useful starting prompts:

Which of my accounts wasted the most money last week?
Show me search terms that spent over $20 with zero conversions.
My cost per conversion doubled this month — find out why.
Draft a list of negative keywords based on last month's search terms.
Compare this month against last month and tell me what changed.

The wasted-spend question is where most people get value on day one. Claude reads every search term, spots the ones burning budget with nothing to show, and hands you the negative keyword list — a task that is tedious by hand and easy for a model that can read the whole table.

Letting Claude make changes safely

Handing an AI write access to something that spends money deserves real guardrails. The ones that matter, and which ClientFuse enforces server-side:

Off by default. Write actions only exist after you switch them on.
Dry run first. Every change is previewed before it can execute.
Explicit confirmation. Execution requires your approval, recorded with the action.
New campaigns start paused. A human has to activate anything that would begin spending.
Budget caps. Hard ceilings on daily budget and on how much a single change can raise it.
Audit log. Every executed action is stored with its arguments and your confirmation.

A sensible way to start: leave write actions off for the first week and use Claude purely for analysis. Once you trust what it is telling you, turn on writes and begin with reversible changes like negative keywords.

What Claude cannot do

Worth knowing before you start:

It cannot activate a campaign you have not approved.
It cannot exceed your configured budget caps, even if you ask it to.
It cannot access accounts you have not connected.
It is not a substitute for judgement on strategy, offers, or creative.

Frequently asked questions

Can Claude actually run my ads, or just read them?

Both, depending on the connector. Google's official MCP server is read-only. A connector with write support lets Claude build search campaigns, add keywords and negatives, pause or resume campaigns, and change budgets — with approval required on each.

Do I need to share my Google password?

No. Access is authorized through Google OAuth and can be revoked whenever you like.

Can it spend money without asking?

No — assuming your connector enforces confirmation. That is the single most important thing to check before granting write access to any AI tool.

Does it work across several accounts?

Yes. One connection covers every Google Ads and Meta account on your profile, which is the main advantage over per-account setups if you manage ads for multiple clients.

What about ChatGPT?

The same connector works there — see how to have ChatGPT run your Google Ads for the setup and the differences.

Connect Claude to your ad accounts

Google Ads and Meta in one connector. Read-only by default, write actions when you want them, with dry runs, budget caps and an audit log. From $19/month with a 14-day free trial.

See how it works