# Connect Google Ads to ChatGPT and Claude

A numbered how-to: start free, add AdCopilot to ChatGPT and to Claude as a plugin, sign in with Google, run a first command.

Tutorials · Published 2026-08-18, updated 2026-11-16.

> Start free at adcopilot.cloud. In ChatGPT or Claude, add the AdCopilot plugin, which carries the connector URL — https://mcp.adcopilot.cloud/mcp — then sign in with your own Google account and authorize read/write scope. Run a read command to confirm, then request a change — AdCopilot proposes it first, and for a hard stop you set your AI client to ask before AdCopilot's write tools. ChatGPT's own plan and workspace rules apply. The 5-day trial for your first workspace covers the full Pro plan and needs a card once it has used 1,000 operations; after that, without a card, it drops automatically to the Free plan, not a lockout.

Connecting Google Ads to ChatGPT and Claude takes five ordered steps and
about ten minutes: start free, add the MCP connector URL, sign in with your
own Google account, and run a first command. The same URL works in both apps,
and it runs
[the full Google Ads toolset](https://adcopilot.cloud/google-ads-mcp-server) from plain-language
prompts. One thing to set expectations up front — this executes on your
command, not on a schedule while you sleep, and AdCopilot proposes each write first.

## Step 1 — Start free and note the connector URL

Go to [adcopilot.cloud](https://app.adcopilot.cloud/signup) and start the
free five-day trial for your first workspace — the full Pro plan, no card to start (one is needed after 1,000 operations). When the trial ends without a card it
drops automatically to the Free plan (one account), not a lockout. The
connector URL is the same for everyone:
`https://mcp.adcopilot.cloud/mcp`. There is no key to copy — what
identifies you is the Google sign-in you complete in Step 3. In most
clients you paste this same URL; in ChatGPT and Claude the AdCopilot plugin
fills it in for you.

## Step 2 — Add the connector in your client

Both ChatGPT and Claude take AdCopilot as a plugin from their own plugin
directories, and the plugin fills the address in for you.

- **In ChatGPT:** open
  [the AdCopilot plugin in ChatGPT](https://chatgpt.com/plugins/plugin_asdk_app_6ac147f11c0081919882be44a32f3948)
  and press Install plugin. Press Connect for the AdCopilot app and approve on AdCopilot's
  page. If ChatGPT doesn't offer you the plugin, add the address yourself
  instead: Plugins, then Add, then Add custom MCP server, with the address in
  its Server URL field. The steps move as the app updates, so the current
  ones are kept on [the ChatGPT setup page](https://adcopilot.cloud/connect-chatgpt-to-google-ads).
- **In Claude:** add the AdCopilot plugin. Open Customize, then Plugins,
  find AdCopilot and press Add (or use the plugin link on the setup page),
  then press Connect on the plugin's Connectors tab. Claude's Add custom
  connector form opens with the name and this address already filled in:
  press Continue, leave the sign-in settings as they are, press Add, and
  approve. If your organisation does not allow plugins, add the address
  yourself instead: Customize, then Connectors, + Add, Add custom connector,
  name it AdCopilot and paste the URL. Step-by-step with current screenshots
  lives on [the Claude setup page](https://adcopilot.cloud/connect-claude-to-google-ads).

You do not need a different address per app — the identical URL works in
each. If you use other clients too, the same connector works across
[every MCP client](https://adcopilot.cloud/mcp-clients).

A note on Microsoft Copilot: adding an arbitrary remote MCP connector as a
custom connector, the way Claude and ChatGPT allow, is not how consumer
Copilot works today. MCP reaches Copilot through Copilot Studio and Microsoft 365
Copilot agents, which is still rolling out — so if Copilot is your goal,
plan for that path rather than expecting parity with the two clients above.

## Step 3 — Sign in with your Google account and authorize scope

The first time the connector runs, it walks you through Google sign-in.
Use your own Google account — the one with access to the ad accounts you
manage. Google's consent screen shows the read/write scope the connector
requests; approve it there. This is standard Google OAuth: you are granting
access under your own login, and you can revoke it from your Google account
security settings at any time. Nothing is stored as a shared password.

Once authorized, the connector can see the accounts your Google login can
see — the same list you would find in the Google Ads UI. In a team, a
teammate's login the workspace owner shares with you adds accounts to read.

## Step 4 — Run a first read command

Confirm the connection with a read before you change anything. In the chat,
ask:

```text
List the Google Ads accounts you can see.
```

Then a real reporting question against one account:

```text
In account <account>, what did we spend in the last 7 days, by campaign,
with conversions and cost per conversion? Just show me, don't change anything.
```

These are reads — no change to the account, no risk, immediate answers
(Claude asks once per read tool unless you set its read-only tools to Always
allow). Check the
numbers against the UI once. That quick calibration is what makes you trust
the approvals that come next, because you have seen the connector read your
account correctly.

## Step 5 — Make one approved change

Now ask for a change. In a ChatGPT Business, Enterprise or Edu workspace,
the admin decides which of a plugin's actions run; if you added AdCopilot to
ChatGPT by hand as a custom MCP server, OpenAI gives full MCP to Business,
Enterprise and Edu, and on a personal plan that one may only read, so make the
change in Claude instead. Something small and recoverable is the right first
move:

```text
In account <account>, add "free" and "cheap" as negative keywords to the
Brand campaign.
```

AdCopilot proposes the write and shows you what it is about to make — the tool, the account, the exact values. For a hard stop, set your AI client to ask before AdCopilot's write tools: Needs approval in Claude; in Cursor, set the run mode to Allowlist and keep them off the allowlist (Cursor's cloud agents never ask). That prompt is the client's own setting, not a step on AdCopilot's server: the connector proposes, and your AI client asks you before it executes if it is set to ask before AdCopilot's write tools. The sane policy is to
graduate boring reads to always-allow while keeping budgets, statuses, and
anything spend-affecting on manual approval every time. There is a fuller
[approval workflow guide](https://adcopilot.cloud/tutorials/approval-workflows-for-ai-ads-changes)
for teams.

## What it can and cannot do

Two honest boundaries worth internalizing:

- **It runs on your command.** It acts when you ask, inside a session, and AdCopilot proposes each write first. It makes no changes on a schedule.
  AdCopilot's own daily check-in email reads the account once a day and
  changes nothing; you can pause it on the Check-ins page. A routine inside
  your assistant is a recipe you paste into your AI client's scheduler, and
  it reads and reports.
- **It can never delete.** The five destructive remove tools are never
  exposed to the AI, and an instruction to remove a campaign, ad or keyword is refused server-side. It
  can pause, adjust, and create across the 77 Google Ads tools it exposes as
  of v2.46.25 — 29 that read and 48 that write, every Google Ads tool its
  underlying server implements except those five — but there is no delete
  path for it to take.

## You're connected

That is the whole flow: start free, add the URL in ChatGPT or Claude, Google
sign-in, first read, first approved change. From here you drive the account
in plain language, and AdCopilot proposes each write first. AdCopilot is built by Atromx Intelligence and
is not affiliated with Google, Anthropic, or OpenAI — you sign in under your
own Google account, and every change lands in Google Ads change history
under your name.

## Questions

### Does this connect to both ChatGPT and Claude?

Yes — the same MCP connector URL works in both, and in both the AdCopilot plugin carries it, so there is nothing to paste. Either way it takes a few clicks, and you sign in with your Google account once per client. There are per-client walkthroughs at /connect-chatgpt-to-google-ads and /connect-claude-to-google-ads for the exact menu paths, which shift as each app updates its UI.

### Can the connector change my account on its own overnight?

No. It executes on your command inside the chat, AdCopilot proposes each write first, and your AI client asks before it runs if it is set to ask before AdCopilot's write tools; a tool set to always allow runs without asking. It makes no unattended changes. The only things it runs on its own are read-only: a daily check-in email that reads the account once a day, a Monday summary and, where Search Console is connected, a daily check of your sites that your assistant tells you about. None of them changes anything; you can pause the two emails on the Check-ins page, and disconnecting Search Console stops the site check. A routine inside your assistant is a recipe you paste into your AI client's scheduler, and it reads and reports.

### What can it never do to my account?

It can never delete. The five destructive remove tools are not exposed to the AI at all, and any instruction to remove a campaign, ad or keyword is refused server-side, so a misread prompt cannot erase a campaign, ad, or keyword. As of v2.46.25 the connector exposes 77 Google Ads tools, 29 that read and 48 that write: every Google Ads tool its underlying server implements except those five. It can pause, adjust, and create, but the delete path simply does not exist for it.

---

This is the markdown copy of https://adcopilot.cloud/tutorials/how-to-connect-google-ads-to-chatgpt-and-claude. The index of the site's pages is https://adcopilot.cloud/llms.txt.
