How to connect ChatGPT to Google Ads

Adding it to ChatGPT

Two prerequisites and no more: a Google login that can already open the advertising account, and a ChatGPT plan carrying custom MCP connectors. None of the API plumbing is yours to arrange — no token, no Cloud project, no OAuth client — though the API access page sets out what those are and the cases where you would want your own regardless.

The Google sign-in is handled once for every client on the MCP server page rather than repeated here. The connector URL is the same for everyone — https://mcp.adcopilot.cloud/mcp — and the rest of this page is ChatGPT alone.

1. Add it in ChatGPT as a custom MCP connector. In ChatGPT's settings, find where connectors are listed and add a custom one. It asks for a label, which can be anything you will recognise, and the server URL: paste https://mcp.adcopilot.cloud/mcp — the same URL for everyone, with no key or token in it. There is no client ID or secret to supply.
2. Sign in with Google when prompted. The first time ChatGPT uses the connector it opens Google's own sign-in. Approve the Google account that has your Google Ads access and pick the accounts the connector is allowed to reach. AdCopilot never sees your password. Everything up to this point is the same whichever assistant you are wiring up, so it is written out once on the MCP server page.
3. Enable it for the conversation and ask what it can see. Saving a connector makes it available, not active. Open a chat, switch the connector on for that conversation, and ask which advertising accounts are visible. What comes back should match the accounts that Google login can already open.

https://mcp.adcopilot.cloud/mcp

Which plans have custom MCP connectors

Availability is the part of this page most likely to be out of date, so here is what is stable enough to be worth writing down, and no more than that.

• It depends on your plan. Custom MCP connector support has been shipped progressively rather than all at once, across both the consumer plans and the work ones. The reliable test is not a comparison table but your own settings: if you can find where connectors are listed, you have it.
• Some accounts have to switch the capability on first. On those, the option to add a custom connector does not appear until it is enabled in settings. Where that switch lives and what it is called has moved more than once, which is exactly why we are not naming a path.
• On a shared workspace it may not be yours to decide. Business and enterprise accounts generally leave connector availability with whoever administers the workspace. A missing or greyed-out option on a company account is more often a policy than a fault, and the fix is a conversation rather than a setting.

If none of that gets you there, nothing is lost. The connector is a plain MCP server over streamable HTTP, so the same address works in Claude, and in Gemini CLI, Copilot, Cursor and OpenCode.

Turning it on for a conversation

This is the one to read even if you skip the rest. Saving a connector makes it available. It does not make it active. Each conversation you want it in has to have it switched on, usually from a menu on the composer, and a chat where it has not been switched on behaves exactly like a chat where the connector was never added: no tools, no accounts, no error worth reading.

That is the single most common reason a correctly configured connector appears not to work, and it accounts for more support questions than every genuine misconfiguration put together. If ChatGPT tells you it has no access to your advertising account, check this before you check the address or your Google sign-in.

It is also the right default. A connector that can change a live advertising account should not be silently in scope for every conversation you have, including the ones about something else entirely.

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 needs nothing but reading, so each works on either tier. It is worth spending a week on questions before instructions: you find out how the account really looks before you ask for anything to change.

What ChatGPT can and cannot change

On the full tier, which is what the pilot runs on, it has thirty-two tools — 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. On the read-only tier it has three, none of which alters anything. Each of them is listed, with what it actually does, on the MCP server page.

It never has 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. Whether that fence is enough, and what else stands behind it, is the whole of the security page.

Access comes back three ways, none of which we have to agree to: revoke AdCopilot on your Google account's third-party access page, delete the connector inside ChatGPT, or ask us to switch your connection off. The security page covers what each one does and how quickly.

If it seems not to work

Below are the ones peculiar to ChatGPT. Everything generic — a mistyped address, the wrong Google sign-in, the read-only tier — sits on the MCP server page instead, since it behaves identically wherever you connect from.

• Saved, but ChatGPT says it has no ads access. The connector is almost certainly not switched on for that conversation. This is the first thing to check and the last thing people check.
• No option to add a custom connector. Either the plan does not offer it, the capability has not been switched on for the account, or a workspace administrator has decided the question. All three are covered above.
• It answers without using the connector. Phrase the request so the connector is the only sensible route: name it, and ask for figures rather than views. A reply containing nothing you could trace back to a row in the account is usually a reply that never made the call.
• It works for you and not a colleague. Connectors are per person, and so is Google access. Their connector runs under their Google sign-in and reaches what that login reaches — which is the point, and is set out on the team access page.

Frequently asked questions