How to Connect Google Ads to Grok 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 Grok account. Custom connectors on grok.com need a SuperGrok plan, either standalone or through X Premium+. On a Grok Business or Enterprise seat, a team admin provisions the connector instead, see the note in the next section. 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 custom connector in Grok

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. 2Go to grok.com/connectors and select New Connector.
3. 3Choose Custom.
4. 4Paste in your server address and complete the authentication step so Grok can reach it. SourcetoMCP runs its own OAuth, so there is no client ID or secret to enter.
5. 5Approve access when Grok asks for it, the same as you would for any other connector.

On a Business or Enterprise plan, a team admin adds the connector first, from console.x.ai's Grok Business → Connectors, choosing Add Connector, then Other, and pasting the same server address. Once it's provisioned, each team member opens grok.com/connectors themselves and signs in with their own SourcetoMCP account, so a 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 Grok about your Google Ads account

Once it's added, SourcetoMCP is available to Grok in any conversation, there is no separate toggle to switch on per chat. Grok discovers the tools the server exposes and calls them the same way it uses any of its built-in connectors.

With both pieces connected, Grok 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. 1Break down spend and conversions across my Search, Display and Performance Max campaigns this month.
2. 2Show me search terms that got clicks but no conversions in the last 30 days.
3. 3Which ad groups have the worst Quality Score, and why?
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 Grok 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.

New Connector → Custom isn't available on grok.com: custom connectors need a SuperGrok plan on an individual account. On a Business or Enterprise seat, a team admin has to provision the connector first from console.x.ai before it shows up for anyone else.

Grok says it can't find the tool or has no data: check the connector still shows as connected under grok.com/connectors. If it does, 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 Grok's access entirely from the Connect an agent page. In Grok, open grok.com/connectors and remove it. On Business and Enterprise, a team admin removes it for everyone from console.x.ai.

Still stuck?

Reach us at [email protected].