Does connecting the MCP give Claude control of every client account?

It has access to accounts linked under the manager account you authorized, just like your own login does. You direct actions at one client at a time, and the MCP sets the correct customer IDs behind the scenes, you're never editing an account you don't already have access to.

Do I need to know the Google Ads API to use it?

No. You describe what you want in plain language'pause campaigns pacing over budget,' 'add these negatives everywhere'and the MCP handles the API calls, account switching, and customer IDs for you.

Manage a Google Ads Manager Account (MCC) From Claude

Q: Can Claude change my campaigns without me confirming?

No. Every write is previewed as a dry run showing the exact before-and-after, and nothing is committed until you approve it. Reads happen freely; changes always pass through the approval gate.

VigilDog Team · September 29, 2026 · 6 min read

If you run an agency or manage multiple Google Ads accounts, your manager account (MCC) is where the whole operation lives, and where most of the repetitive clicking happens. Connecting an Ads MCP lets you drive that manager account from Claude in plain language, from cross-account reports to bulk edits. Here's how it works, and how the guardrails keep it safe.

What an MCC is, and why running it from Claude helps

A Google Ads Manager Account (MCC, short for My Client Center) is an umbrella account that links and controls many individual Ads accounts under one login. Agencies live in MCCs: one place to switch between clients, roll up performance, and manage access without juggling separate credentials.

The friction is that day-to-day MCC work is repetitive and spread across accounts, pulling last week's numbers for twelve clients, hunting for wasted spend, pausing the same underperformer in three places. Doing that in the Google Ads UI is a lot of clicking. Connecting an Ads MCP lets you manage a Google Ads MCC from Claude in plain language: ask 'show me every account where CPA rose more than 20% week over week,' get an answer, then act on it in the same window.

How the Ads MCP connects to your manager account

The VigilDog Ads MCP is a server that speaks the Model Context Protocol, sitting between Claude and the Google Ads API. You authorize it once with OAuth against the Google account that has access to your MCC. From then on, Claude can call the MCP's tools, list accounts, read performance, edit campaigns, and the MCP translates those into authenticated Google Ads API calls on your behalf.

Because the connection is scoped to your manager account, everything below it is reachable through the same authorization. You're not pasting API keys into a chat window; the MCP holds the credentials and Claude only ever sees the tool results. Our guide on running Google Ads from Claude walks through the initial connection step by step.

How an Ads MCP runs a change safely

Picking the right account: manager vs client IDs

The one concept that trips people up is which customer ID an action targets. In Google Ads API terms, the manager account is the login-customer-id, the account you authenticated through, while each client account has its own customer ID. A request operates on a specific client ID but is authorized via the manager above it.

In practice, you tell Claude which client you're working on ('switch to the Acme account') and the MCP sets the right IDs behind the scenes. If you ever hit a permission error, it's almost always because the target account isn't actually linked under that MCC, or the link is still pending acceptance, check the account hierarchy first.

Everyday MCC workflows from Claude

Once connected, the tasks that used to eat an afternoon become a short conversation:

Cross-account reporting: 'Rank all accounts by spend this month and flag any where conversions dropped.'
Waste hunting: 'Find search terms across every account with over $50 spent and zero conversions in the last 30 days.'
Bulk hygiene: 'Add these five negative keywords to the brand campaign in each client account.'
Budget checks: 'Which campaigns are pacing to overspend their monthly budget?'
Client-ready summaries: 'Draft a plain-English performance recap for the Acme account for last month.'

Guardrails: dry-run and approval before anything changes

Handing an AI write access to live ad accounts sounds risky, and it would be without guardrails. The VigilDog Ads MCP defaults to read-only comfort: any change is previewed as a dry run first, showing exactly what would happen, which campaign, which budget, the before and after, and nothing is committed until you approve it.

That approval gate is what makes MCC-scale automation safe. Claude can propose pausing eight campaigns across five accounts, but you see the full list and confirm before a single edit lands. It's the speed of automation with the control of doing it by hand. When you're ready to connect your manager account, start here.