How to connect ChatGPT to Google Ads

Before you start

• A Google account with access to the ads account. The connector inherits your access exactly; it cannot see more than you can.
• A ChatGPT plan with custom MCP connectors. Support has rolled out progressively across plans and Work accounts. If the setting is not there yet, the same address works in Claude and every other MCP client.
• Nothing to install, and no developer token, Cloud project or OAuth client of your own.

The four steps

1. Sign in with Google. Start the pilot and sign in with the Google account that already has access to your Google Ads accounts. The connector runs under Google's own sign-in and inherits exactly your access, so it can never reach an account you cannot.
2. Copy your private connector address. You are given an address of the form https://mcp.adcopilot.cloud/c/<your key>/mcp. It is unique to you and it is the credential — treat it like a password and do not paste it into a shared document.
3. Add it in ChatGPT as an MCP connector. Open Settings, then Connectors, and add a custom MCP server. Give it a name such as AdCopilot and paste the address. No client ID or secret is needed; the key in the address authenticates the connection.
4. Ask it which accounts it can see. Start a new chat, enable the connector for that conversation, and ask which Google Ads accounts are visible. It should list exactly the accounts your Google login can reach, which confirms the connection before anything is changed.

https://mcp.adcopilot.cloud/c/<your key>/mcp

Where the setting lives

In ChatGPT the connector setting sits under Settings → Connectors, where you add a custom MCP server by name and URL. Once saved, enable it for the conversation you want it in — connectors are not automatically on in every chat, which is a sensible default when one of them can change a live ads account.

OpenAI has moved this setting more than once as the feature matured, so if the wording differs from the above, look for “connectors”, “MCP” or “apps” in settings. The address you paste does not change.

Your first questions

Start with something you can check yourself:

• “Which Google Ads accounts can you see?”
• “Summarise last month's spend and conversions by campaign.”
• “Find search terms from the last 90 days with spend above £50 and no conversions.”
• “Which campaigns are budget-limited?”
• “What changed in this account last week?”

Every one of those runs on the read-only tier. It is worth spending a week there: you find out how the account really looks before anything can act on it.

What ChatGPT can and cannot change

On the read-only tier: three tools, none of which alters anything. On the full tier it gains twenty-nine more — campaigns including Performance Max, ad groups, responsive search ads, keywords and negative keywords, the full asset set and their links, plus geography, ad schedule and device bid adjustments.

It never gains the four destructive tools. Those are filtered out before the model sees the tool list, so “remove” is not a thing it can attempt — which also means a prompt injected into some page it read cannot talk it into one. The complete list is on the MCP server page.

Withdrawing access

• From your Google account's third-party access page, which cuts the credential off at source regardless of what we do.
• Remove the connector in ChatGPT, which stops it being called.
• Ask us to switch the address off — instant, effective on the next request.

If it doesn't connect

• The address must end in /mcp with no trailing slash.
• Copy the whole key. A truncated key and an invalid key are refused identically on purpose, so the response cannot be used to discover which keys exist.
• No accounts listed? The Google login you used probably lacks access. Sign in to Google Ads directly with the same account to check.
• Fewer tools than expected? That is the read-only tier, which is the pilot default and is three tools.
• Connector not offered in your ChatGPT plan? Use Claude, Gemini CLI or Copilot with the same address — the protocol is the same everywhere.

Frequently asked questions