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 from plain-language prompts. One thing to set expectations up front — this executes on your command with an approval on every write, not on a schedule while you sleep.
Step 1 — Start free and note the connector URL
Go to adcopilot.cloud and start the
free seven-day trial for a new workspace — the full Pro plan, no card. When the week ends 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 or token to copy — what
identifies you is the Google sign-in you complete in Step 3. Every later step
pastes this same URL.
Step 2 — Add the connector in your client
Both ChatGPT and Claude accept remote MCP connectors in a few clicks. The address from Step 1 is all either needs.
- In ChatGPT: switch on developer mode first (Settings, then Security and login), then open Plugins, press +, choose Create app, then Create MCP App, and paste your address into the form's Server URL field. The menu path moves as the app updates, so the current click-by-click, with screenshots, is kept on the ChatGPT setup page.
- In Claude: open Customize, then Connectors, press + Add and choose Add custom connector (or use the direct link on the setup page). Name it AdCopilot, paste the same address, press Continue, leave the sign-in settings as they are, press Add, then Connect, and approve. Step-by-step with current screenshots lives on the Claude setup page.
You do not need a different address per app — paste the identical URL in each. If you use other clients too, the same connector works across every MCP client.
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.
Step 4 — Run a first read command
Confirm the connection with a read before you change anything. In the chat, ask:
List the Google Ads accounts you can see.
Then a real reporting question against one account:
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. Something small and recoverable is the right first move:
In account <account>, add "free" and "cheap" as negative keywords to the
Brand campaign.
The client pauses and shows you the write it is about to make — the tool, the account, the exact values — and waits. Nothing happens until you approve. That per-write confirmation is the core safety model: the connector proposes, you approve, then it executes. 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 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, with an approval on every write. It does not run overnight or on a schedule in the shipped product. AdCopilot's own scheduler is on the roadmap; today the routine is a recipe you paste into your AI client's scheduler, and it reads and reports.
- It can never delete. The four destructive remove tools are never exposed to the AI, and a removal instruction is refused server-side. It can pause, adjust, and create across the 54 Google Ads tools it exposes as of v2.16.0 — 16 that read and 38 that write, every Google Ads tool its underlying server implements except those four — 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 approve each write as it comes. AdCopilot is built by Atromx Intelligence and is not affiliated with Google, Anthropic, or OpenAI — you sign in under your own Google account and stay in control of every change.