Connect Google Ads to Claude Code

Let Claude pause spend, adjust budgets, and update bids in Google Ads. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Google Ads to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Google Ads, you add a Google Ads MCP server: a small hosted service that exposes Google Ads's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Google Ads account. No API keys pasted into config files.

claude mcp add --transport http google-ads https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Google Ads once connected?

Full read-write Google Ads access lets Claude pause a wasteful campaign, shift a daily budget, adjust a bid or target, edit ad copy, and update negative keyword lists once you approve. The optimization work that used to mean tabbing through the Ads UI happens where the account already lives.

Pause or enable campaigns and ad groups based on performance you define
Adjust daily budgets or campaign budget caps with your sign-off
Update bids or bid targets on keywords and ad groups
Add negative keywords to a shared list to cut wasted spend
Edit responsive search ad headlines and descriptions in a draft
Apply or remove labels to organize campaigns for reporting

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Google Ads access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Google Ads API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Google Ads changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Google Ads connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Google Ads connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Google Ads account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Google Ads's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Google Ads?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Google Ads account it signs in with. Revoking access is one click in Google Ads.

More on the Google Ads connector

Google Ads connector for claude.ai Braze + Claude Code Iterable + Claude Code Customer.io + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us