Claude and Google Ads are a natural pairing for a structural reason: Anthropic published the Model Context Protocol 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. You sign in to a connector service — AdCopilot is one — with your own Google account, receive a private connector address, and paste it into Claude's settings. From then on Claude holds a live line to the account: reads run freely, and every write surfaces as a permission prompt naming the exact tool call before it executes.
Two properties of the mechanism do most of the reassuring. Access rides your own Google sign-in, so Claude can only ever see accounts your Google account can see, and changes land 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:
| 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 — the Claude connection guide covers all three, with the Desktop path, the most common one, step by step.
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 32 exposed tools, 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 remove tools are never exposed, and a status change to REMOVED is refused server-side. The blast radius of a bad approval is a pause or a budget change — both reversible.
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; commercial plans are excluded by default, per Anthropic's training policy.
Anthropic never sees your Google password — no party does; OAuth replaces it. The connector stores exactly one credential, an encrypted Google refresh token, and passes performance data straight through to Claude without retaining it. The full three-party map lives in what data the AI actually sees, and the connector side in the security page.
Setup pointers per surface
The five-minute version, whichever surface you use:
- Sign up with your Google account and copy your private connector address.
- Claude Desktop or claude.ai — Settings, Connectors, "Add custom connector", paste the address. Claude Code — add it as an MCP server in config; the multi-client guide shows the exact snippet.
- Open a conversation and ask for a 30-day account overview. It is a read: no approval, no change, 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:
Give me an account overview for the last 30 days: campaigns with spend,
conversions and cost per conversion. Flag anything structurally odd.
Which search terms spent money in the last 30 days without converting?
Rank by cost, top 20, with the campaign each appeared in.
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 approvals, 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 reversible, which is exactly the shape a first approval should have.
First-session advice is otherwise the same on every surface — reads first, small reversible writes second, trust on evidence throughout. When you are ready to connect, the pilot takes a Google sign-in and gives you seven days with the full toolset on up to five accounts, no card.
Frequently asked questions
Does Claude have a built-in Google Ads connector?
No. Claude's connector directory covers common apps, but Google Ads arrives as a custom connector — you add it yourself by pasting a connector address into Settings, then authorising with Google. Custom connectors are a first-class Claude feature, not a workaround; the address, such as one from AdCopilot, is the only setup there is.
Which Claude plan do I need?
As of August 2026, Anthropic's help centre lists custom remote-MCP connectors as available on Free, Pro, Max, Team and Enterprise plans, with Free limited to a single custom connector. That single slot is enough to run a Google Ads connector. 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 itself retains no performance data either way; what reaches Anthropic is the conversation, under whichever policy your plan carries.
Try it on your own account for a week
The full set of tools for the week, so you can see what it actually does — and it still cannot delete anything. No cost, no card, no contract: you connect your own Google account and can withdraw the access whenever you like.
- Up to 5 accounts
- One week
- Full tools
- No card
- Autonomous agentsLevels of autonomy in Google Ads management, which optimisation work is safe unattended versus which needs approval, and why irreversible actions should not be automated.
- Google Ads MCP serverWhat a Google Ads MCP server is, how free self-hosted servers compare to a hosted one, the full tool list AdCopilot exposes, and what you need to connect.
- Connect ClaudeStep-by-step instructions for adding a Google Ads MCP connector to Claude Desktop, claude.ai and Claude Code, including what to ask it first and how to revoke access.
- Connect ChatGPTStep-by-step instructions for adding a Google Ads MCP connector to ChatGPT, what it can read and change, and how to withdraw access.