How to Connect Google Ads to Claude with MCP?

Before you start

You'll need a SourcetoMCP account with at least one brand created, a Google account with access to at least one Google Ads account, and a Claude account. Custom connectors work on Free, Pro, Max, Team and Enterprise, though Free accounts are limited to one at a time. An account owned by a manager account (MCC) works too: SourcetoMCP resolves the managing account and retries under it, so there is no login customer id for you to find.

Connect Google Ads to SourcetoMCP

1. 1From your dashboard, go to Connectors → Add a connection.
2. 2Find the Google Ads card and select Connect.
3. 3Sign in with the Google account that has access to the account you want. This opens Google's own consent screen on accounts.google.com and asks you to approve access to your Google Ads data. This covers both reading performance data and making changes on your behalf, since SourcetoMCP can do both.
4. 4Back in SourcetoMCP, choose which account(s) to connect. Each one shows up with its real name and customer ID (e.g. “Acme Co (624-809-0961)”). Then confirm. They show up on your Connections page.

Add SourcetoMCP as a connector in Claude

1. 1In SourcetoMCP, open Connect an agent from the dashboard sidebar and copy your server address (it looks like https://sourcetomcp.com/api/mcp).
2. 2In Claude, open Customize, then Connectors.
3. 3Select +, then Add custom connector.
4. 4Paste in your server address. You can leave Advanced settings alone, because SourcetoMCP runs its own OAuth and never needs a client ID or secret from you.
5. 5Click Add.
6. 6The first time Claude uses it, you'll be asked to sign in to SourcetoMCP and approve access, the same OAuth approval you'd see connecting any other app. After that it reconnects on its own.

On a Team or Enterprise plan, only an Owner can add a connector, from Organization settings, then Connectors. Everyone else then opens Customize → Connectors and clicks Connect to sign in with their own SourcetoMCP account, so each person only ever reaches the sources their own account can see.

Once approved, the connection appears under Active connections on the Connect an agent page in SourcetoMCP, so you can see exactly what has access at any time.

Ask Claude about your Google Ads account

Adding the connector makes it available, and you still switch it on per conversation. In a chat, select the + button, choose Connectors, and toggle SourcetoMCP on.

Claude shows a panel for each tool call, named in plain English, so you can see which data it pulled and check the numbers came from your account rather than from the model.

With both pieces connected, Claude can query campaign, ad group and keyword performance, dig into search terms, check Quality Score, and review Google's own recommendations, and act on what it finds if you ask. Try something like:

1. 1How did my Search campaigns perform last week compared to the week before?
2. 2Show me search terms that got clicks but no conversions in the last 30 days.
3. 3What's dragging down my Quality Score in my worst-performing ad groups?
4. 4Find negative keyword candidates from my worst-performing search terms and add them.

The first three are read-only reports. The last one is a write action. See the note below on how SourcetoMCP handles those.

A note on write actions

Unlike a read-only connector, Google Ads through SourcetoMCP can create and change real things in your account: campaigns, ad groups, keywords, budgets, negative keywords and more. Campaigns cover seven channel types, Search, Display, Shopping, Video, Performance Max, Demand Gen and App, each created with a bidding strategy Google Ads accepts for that type. New campaigns and ad groups are created paused by default, so nothing starts spending without an explicit follow-up action, and Claude will tell you what it's about to change before it does anything irreversible. Worth reading its proposed action before confirming, the same as you would for any assistant with write access to a live ad account.

Troubleshooting

My account isn't in the list when connecting: the signed-in Google account doesn't have access to that Google Ads account. Add it under Google Ads' own Tools & Settings → Access and security, then reconnect.

There is no Connectors option under Customize: on Team and Enterprise plans an Owner adds connectors for the whole organisation. Ask an Owner to add it from Organization settings → Connectors, and it will then show up for you to connect.

Claude won't let you add another connector: Free accounts can keep one custom connector at a time. Remove the one you have, or move to Pro or Max.

Claude says it can't find the tool or has no data: check SourcetoMCP is toggled on for that conversation under the + menu. If it is, confirm the connection still shows under Active connections in SourcetoMCP, then remove and re-add it to trigger a fresh approval.

Revoking access

You can disconnect from either side. In SourcetoMCP, remove the account from your Connections page, or revoke Claude's access entirely from the Connect an agent page. In Claude, open Customize → Connectors and remove it. On Team and Enterprise an Owner removes it for everyone from Organization settings → Connectors.

Still stuck?

Reach us at [email protected].