# Can Claude Access Google Ads? Yes — Here's How

Claude reads and edits Google Ads through a custom MCP connector — on Claude Desktop, claude.ai and Claude Code. The mechanism and the setup steps.

Questions · Published 2026-08-10, updated 2026-11-11.

> Yes. Claude can access Google Ads on every major surface — Claude Desktop, claude.ai in the browser, and Claude Code — through a custom MCP connector, such as AdCopilot by Atromx (adcopilot.cloud), authorised with your own Google sign-in. Once connected, Claude reads live performance and makes changes with a permission prompt per write; set the read-only tools to Always allow and reports stop asking. Anthropic never receives your Google password; the connector holds a revocable OAuth token, and you can withdraw access from your Google account at any time.

Claude and Google Ads are a natural pairing for a structural reason:
Anthropic published the [Model Context Protocol](https://modelcontextprotocol.io)
in November 2024, and Claude has supported custom connectors longer than any
other major client. Ads access is not a bolt-on trick — it uses the
mechanism Claude was built around.

## The answer and the mechanism

Claude accesses Google Ads through a custom MCP connector. The quickest
way in is AdCopilot's plugin for Claude, which adds the URL for you; press
Connect and approve, with your own Google account behind it. From then
on Claude holds a live line to the account. Claude asks before each tool
the first time; set the connector's read-only tools to Always allow and
reads run without asking, while Claude still asks before each write, naming the exact tool call, when Write/delete tools are on Needs approval, which is where they start; AdCopilot proposes each change first either way.

Two properties of the mechanism do most of the reassuring. Access rides
your own Google sign-in, so Claude sees the accounts your Google account
can see, plus, for reads, what a teammate's login opens if your workspace
owner shares it with you. Every change runs on your own login, so it lands
in Google's change history attributed to you. And the authorisation is a standard Google OAuth grant — revocable from
your Google account's security page at any moment, no vendor cooperation
required.

## Which Claude surfaces work: Desktop, web, Code

The same connector address works across Claude's surfaces, per Anthropic's
[custom connectors guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp):

| Surface | Fit for ads work |
| --- | --- |
| Claude Desktop | The everyday home — settings UI for connectors, approvals as native prompts |
| claude.ai (browser) | Same conversations without an install; useful on machines you don't own |
| Claude Code | Terminal-native; strongest when ads work sits next to scripts and files |

Setup differs by a few clicks per surface. A connector added on claude.ai
also shows in Claude Desktop under the same account; the
[Claude connection guide](https://adcopilot.cloud/connect-claude-to-google-ads) has that path step
by step, with screenshots, and in Claude Code it is the same plugin (two typed
commands) or one command by hand.

## What Claude can read and change once connected

Reads cover the account as Google exposes it: campaign and keyword
performance, search terms, change history, budgets, assets, geo and device
breakdowns — answered in plain language, current at query time.

Writes, through AdCopilot's 77 exposed Google Ads tools (as of v2.46.25), include adding keywords and
negative keywords, creating campaigns (search and Performance Max, paused
by default), building ad groups and responsive search ads, and adjusting
budgets, schedules, geo targets and device bids. Deletion is not in the
list by design: the four remove tools are never exposed, and a status change to
REMOVED is refused server-side. The blast radius of a bad approval is
a change the account itself can put back — a pause, a budget, a bid, a keyword — never a deletion.

## What Anthropic sees and does not see

Three different parties handle three different things, and conflating them
causes most of the worry.

Anthropic sees the conversation — your prompts and the data Claude pulled
into it. Whether that conversation can train models depends on plan:
consumer plans carry a model-training choice under the
[August 2025 consumer-terms update](https://www.anthropic.com/news/updates-to-our-consumer-terms);
commercial plans are excluded by default, per Anthropic's
[training policy](https://privacy.claude.com/en/articles/10023580-is-my-data-used-for-model-training).

Anthropic never sees your Google password — no party does; OAuth replaces
it. The connector stores exactly one credential, an encrypted Google refresh
token. Queries run live against your account; audit reads are cached for up
to an hour and a saved audit's findings, with up to 10 example rows each, for
180 days; each tool call is logged; and your workspace's business profile is
kept until its owner deletes it. The full three-party map lives in
[what data the AI actually sees](https://adcopilot.cloud/questions/what-data-does-the-ai-see-google-ads),
every record and its period in the [privacy policy](https://adcopilot.cloud/privacy), and the
connector side in the [security page](https://adcopilot.cloud/security).

## Setup pointers per surface

The five-minute version, whichever surface you use:

1. Start free at AdCopilot; the connector URL is the same for everyone —
   there is no per-user key to copy.
2. Claude Desktop or claude.ai — Customize, Plugins, find AdCopilot and
   press Add, then Connect on the plugin's Connectors tab. The "Add custom
   connector" form opens already filled in: press Continue, leave the
   sign-in settings as they are, press Add, and approve. Where plugins are
   not allowed, add it by hand instead — Customize, Connectors, + Add, "Add
   custom connector", name it AdCopilot and paste the URL. Optionally set
   the read-only tools to Always allow so reports stop asking. Claude Code —
   install the same plugin, or add it as an MCP server in config; the
   [multi-client guide](https://adcopilot.cloud/mcp-clients) shows both.
3. Open a conversation and ask for a 30-day account overview. It is a
   read: no change to the account, and it proves the whole pipe in one
   message.

## What to ask Claude in the first session

The first conversation sets the working pattern, and the right pattern is
reads before writes. Three openers that earn their place:

```text
Give me an account overview for the last 30 days: campaigns with spend,
conversions and cost per conversion. Flag anything structurally odd.
```

```text
Which search terms spent money in the last 30 days without converting?
Rank by cost, top 20, with the campaign each appeared in.
```

```text
Summarise the change history for the last month — what changed, when,
grouped by type. I want this account's recent story.
```

All three are reads: no changes, no risk, and together they show
whether the agent's reasoning deserves a next step. When it does, the
first write worth approving is a short negative-keyword list drawn from
the second prompt — small, evidenced and recoverable, which is exactly
the shape a first approval should have.

First-session advice is otherwise the same on every surface — reads
first, small recoverable writes second, trust on evidence throughout.
When you are ready to connect,
[the free trial](https://app.adcopilot.cloud/signup) takes a Google sign-in and
gives you five days on the full Pro plan for your first workspace, no card to start (one is needed after 1,000 operations), then, without a card, it drops to the Free plan (one account) rather than cutting off.

## Questions

### Does Claude have a built-in Google Ads connector?

Not built in, but AdCopilot's plugin is listed in Claude's plugin directory: under Customize, then Plugins, add AdCopilot and press Connect on its Connectors tab. Claude opens its Add custom connector form with the address already filled in, so you press Continue, then Add, and approve. Adding the address yourself as a custom connector still works, and is the route where plugins are not allowed.

### Which Claude plan do I need?

Any, including Free: we added the AdCopilot plugin on a Free Claude account in October 2026, and AdCopilot as a custom connector on Free and on Max in September. A Team or Enterprise organisation may not allow plugins, and adding custom connectors may be kept to its owners, so an owner may need to add it first. Plan gates change, so check Anthropic's current connectors article before deciding.

### Does my ads data train Claude?

Plan-dependent. Since Anthropic's August 2025 consumer-terms update, Free, Pro and Max conversations are used for model training only when the model-improvement setting is on — a choice made at sign-up and changeable in privacy settings. Commercial plans — Team, Enterprise, API — are excluded by default. The connector trains nothing either way; it caches audit reads for up to an hour and keeps a saved audit's findings for 180 days, and what reaches Anthropic is the conversation, under whichever policy your plan carries.

---

This is the markdown copy of https://adcopilot.cloud/questions/can-claude-access-google-ads. The index of the site's pages is https://adcopilot.cloud/llms.txt.
