# Troubleshooting Your Google Ads Connector

Google Ads MCP connector troubleshooting: no tools listed, account limits after the trial, revoked access, wrong account, rate limits — each with its fix.

Tutorials · Published 2026-08-10, updated 2026-11-13.

> Connector problems sort into five buckets: the client cannot see the tools (config or transport, fixed in the client), an account is outside your plan's limit or a paid subscription lapsed (enforced server-side — the trial itself never locks you out, it just drops to the Free plan), Google access was revoked (fixed by signing in with Google again, same seat, same Google account), the wrong account is visible or one is missing (you connected the wrong Google sign-in, the account sits under a manager, or no login you use opens it), or you hit a rate limit (wait, then narrow the queries). Work them in that order.

When a Google Ads connector misbehaves, the fault is in one of three
places: the client (config, transport, mode), the connector (trial,
revocation, scoping, limits), or the Google account behind it. This page
is the catalogue — symptom, cause, fix — ordered by how often each one
is actually the answer. The product docs have a troubleshooting section
too: [troubleshooting in the docs](https://adcopilot.cloud/docs/troubleshooting/).

## The client lists no server, or a server with no tools

**Symptom.** Your MCP client shows nothing, or shows `adcopilot` with
zero tools.

**Cause.** Client-side, almost always: a mistyped address, the wrong
transport field, invalid JSON, or the wrong chat mode. The connector URL is
`https://mcp.adcopilot.cloud/mcp` — the same for everyone, so a wrong one is a
typo rather than a missing key.

**Fix.** Re-paste the URL `https://mcp.adcopilot.cloud/mcp`, then check the
client-specific trap: Gemini CLI needs the field
[`httpUrl`, not `url`](https://adcopilot.cloud/tutorials/gemini-cli-google-ads-setup); Cursor
needs [Agent mode and valid JSON](https://adcopilot.cloud/tutorials/cursor-google-ads-setup);
Claude Code wants `--transport http` on
[the add command](https://adcopilot.cloud/tutorials/claude-code-google-ads-workflow), plus
`--scope user` — without it the server only shows in the folder you added
it from; Claude takes it through the AdCopilot plugin or as a custom
connector (see the Claude section below); ChatGPT
takes it through the AdCopilot plugin or as a custom MCP server (see its section below). Restart the client after
any config edit — most read config at startup. The per-client shapes are
collected on [the clients page](https://adcopilot.cloud/mcp-clients).

## ChatGPT: the four places people get stuck

ChatGPT takes AdCopilot as a plugin: open
[the AdCopilot plugin in ChatGPT](https://chatgpt.com/plugins/plugin_asdk_app_6ac147f11c0081919882be44a32f3948),
press Install plugin, then Connect for the AdCopilot app, and approve on
AdCopilot's page. The [ChatGPT setup page](https://adcopilot.cloud/connect-chatgpt-to-google-ads)
has every step, and the docs have the
[full step-by-step](https://adcopilot.cloud/docs/connect/chatgpt/). These
are the four snags on that path, in the order you meet them.

**The plugin is not offered to you, or says Disabled by admin.** OpenAI says
whether you can install and use a plugin depends on your ChatGPT plan,
workspace, role and region. In a Business, Enterprise or Edu workspace the
admin decides which plugins members can install, so ask them. If ChatGPT
doesn't offer it at all, you can still add AdCopilot by hand as a custom MCP
server: Plugins, then Add, then Add custom MCP server.

**The sign-in was interrupted.** If you closed the tab before pressing
Approve, open Settings, then Plugins, choose the AdCopilot plugin and press
Connect. ChatGPT goes back to AdCopilot's page; press Approve.

**ChatGPT reads but will not change anything.** In a work workspace, the admin
may allow the AdCopilot app's read actions and not its write actions. If you
added AdCopilot by hand as a custom MCP server, OpenAI's limits for those
apply: full MCP, tools that change things included, is for Business,
Enterprise and Edu, and Pro gets read and fetch, so on a personal plan
ChatGPT may let AdCopilot read your account but not change it. Reads still
work; for a change, use Claude. OpenAI states those limits for custom MCP
servers, and the plugin is the other way in.

**ChatGPT searched the web instead of using AdCopilot.** Start the message by
typing **@** and picking AdCopilot from the list that appears, then type your
question. ChatGPT uses an installed plugin on its own when it fits, but
picking it with @ makes it use AdCopilot for that turn; without it, ChatGPT
may decide to search the web.

## Claude: the four places people get stuck

Claude adds AdCopilot through its plugin: under Customize, then Plugins,
add AdCopilot, then press Connect on the plugin's Connectors tab. Claude's
"Add custom connector" box opens with the name and the URL already filled
in; press Continue, leave the sign-in settings as they are, press Add, and
approve. The
[Claude setup page](https://adcopilot.cloud/connect-claude-to-google-ads) has every click with
screenshots, and the docs have the
[full step-by-step](https://adcopilot.cloud/docs/connect/claude/). These
are the four snags on that path.

**There is no "Customize" in your sidebar.** Claude lays these screens out
differently between accounts. Skip the menus: this link opens AdCopilot's
plugin page in Claude straight away —
[open the AdCopilot plugin in Claude](https://claude.ai/new#customize/plugins/id/c9bfd1ff-d329-4949-91fb-dc97116194ae%40anthropic-plugin-directory).
If it does not, use the custom-connector fallback instead:
[claude.ai/new?modal=add-custom-connector](https://claude.ai/new?modal=add-custom-connector#customize/connectors/yours)
opens the "Add custom connector" box on every layout we have seen; name it
AdCopilot and paste `https://mcp.adcopilot.cloud/mcp`. Sign in to Claude
first if it asks.

**You added AdCopilot by hand before.** There is no second connector to
add. Claude links the plugin to the connector you already have, because
the URL is the same, so Connect may not show our Approve page at all. If
AdCopilot's tools look out of date afterwards, open Customize, then
Connectors, then adcopilot, press Disconnect, and connect again.

**Claude asks permission before every report.** Claude starts AdCopilot's
read-only tools on "Needs approval", so the first run of each one stops
to ask. Open Customize, then Connectors, then adcopilot, and under "Tool
permissions" set the "Read-only tools" group to "Always allow". Leave
"Write/delete tools" on "Needs approval": AdCopilot proposes each change first, and that setting makes Claude ask you before it runs; either way, AdCopilot can't delete anything except a negative keyword.

**You use Claude through a Team or Enterprise organisation.** The
organisation may not allow plugins, and adding custom connectors there may
be kept to its owners. If you cannot add AdCopilot yourself, ask an owner
to add it for the organisation; each person then presses Connect and
approves under their own sign-in. We cannot change that setting from our
side. Where plugins are off but custom connectors are allowed, add it by
hand: [claude.ai/new?modal=add-custom-connector](https://claude.ai/new?modal=add-custom-connector#customize/connectors/yours)
opens the "Add custom connector" box; name it AdCopilot and paste
`https://mcp.adcopilot.cloud/mcp` (if your browser's autofill list covers
the URL box, press Esc first). On a personal account, the plugin and
custom connectors both work on the Free plan.

## Every call fails with an account-limit or subscription message

**Symptom.** Tools list fine, but calls for a particular account return
an error saying it is outside your plan's account limit, or that a paid
subscription has lapsed.

**Cause.** The trial is five days on the full Pro plan for your first workspace; when it ends
without a card, the workspace drops automatically to the Free plan — one account keeps
working at Free's limits, not a lockout, but any other accounts you
connected during the trial go quiet until you upgrade. The same happens
before the end if the trial has used 1,000 operations with no card: it
pauses on Free's limits, and adding a card on the Billing page switches
the other accounts back on. Separately, if a
paid subscription's billing period ends without renewing, the connector
keeps working through that period and then stops for the accounts it
covered.

**Fix.** Nothing in the client will help — the state lives on the
server. Sign in to your dashboard to see which plan is active and which
accounts it covers; starting or resuming a paid plan restores the rest
immediately, with no re-configuration on the client side.

## Google access revoked — auth errors on every call

**Symptom.** Calls fail with an authorisation error against Google, on a
connector that previously worked.

**Cause.** The stored Google credential was invalidated. Common
triggers: you removed AdCopilot under your Google account's third-party
access, a workspace admin policy did, or a password-reset/security event
rotated your grants. This is Google's revocation model working as
intended — you can withdraw access at any time without asking anyone.

**Fix.** Reconnect from your AI client — or the reconnect prompt in your
dashboard — and complete Google's sign-in again **with the same Google
account**. Same seat, history intact, and nothing to re-paste; the URL never
changed. A reconnect from a different Google account is refused by design: the
connector verifies identity, so a colleague cannot quietly re-point your seat
at their credentials. The full revocation model is on
[the security page](https://adcopilot.cloud/security).

## The wrong account is visible — or the right one is missing

**Symptom.** `List the accounts you can see` returns somebody's personal
test account, an unexpected MCC tree, or is missing the client account
you manage.

**Cause.** Usually one of three: you were signed into the wrong Google
account in the browser when you connected (the classic — most people are
signed into several); the account is a client under a manager account
(the list holds the accounts your sign-in opens directly, and those shared
with you through a teammate's login, while client accounts under a manager
are listed under **Ad accounts** in your dashboard); or neither the Google
account you connected nor a teammate's login shared with you for that
account has access to it. Named customer IDs never take an account off
this list: if support has held your seat to some, accounts outside them
still appear here, and a call that names one is refused.

**Fix.** For the first: reconnect via your dashboard using the right
Google account — for a different identity that means a fresh connector,
since reconnect protects the original identity. For the second: check the
client account is listed and switched on under **Ad accounts**, then ask
about it by its customer ID; the call goes through the manager by itself.
For the third: get access granted in Google Ads itself, then ask again — no
connector-side change needed. For a refusal that names an account outside
your named customer IDs, the workspace owner can ask support to change them.

## Rate limited

**Symptom.** A run of rapid calls starts returning a rate-limit refusal,
usually mid-way through a large scripted job.

**Cause.** Per-connector rate limits, deliberately part of the
[security model](https://adcopilot.cloud/security) — they cap the blast radius of a runaway
loop, yours or an agent's.

**Fix.** Wait briefly and continue; limits recover on their own. Then
shape the work to need fewer calls: one GAQL query returning a table
beats thirty single-entity look-ups, and scheduled jobs should run the
[compact report pattern](https://adcopilot.cloud/tutorials/claude-code-google-ads-workflow)
rather than enumerating the account. If a legitimate workload hits
limits repeatedly, tell us — that is a conversation, not a workaround.

## Writes refused when reads work fine

**Symptom.** Reports flow, but every mutate is refused.

**Cause.** Either the connector was configured with narrowed access, an
org admin flipped the per-connector kill switch, or the Google account
itself has read-only rights in that Ads account. And if the refused call
was a delete: that is permanent design, not configuration — see the FAQ
below. In a team there is one more: an account you read only through a
teammate's login the workspace owner shares with you. A Google Ads change
always runs on your own login, so it is refused with "Not changed: account
… is reached here only through a teammate's shared Google login".

**Fix.** Check the connector's status and scope in the dashboard, ask
your org admin what they have narrowed, and verify your own role in
Google Ads. For a shared login, connect your own Google login that has
access to the account, or ask a teammate whose login reaches it to make
the change. The refusal always has a reason, and the reason is recorded.

## Still stuck — bring the audit trail

Every call through the connector is logged — tool, account, success or
refusal, reason, timestamp — which means support conversations start
from evidence rather than guesswork. Write to
**support@adcopilot.cloud** with the approximate time of the failing call and
what the client displayed; the log usually names the cause in one look.
And if the connector is fine but the account work is the puzzle, the
[prompt library](https://adcopilot.cloud/tutorials/prompt-guidelines-for-google-ads-ai) is the
better page to be on.

## Questions

### My connector worked yesterday and fails today with nothing changed — most likely cause?

Revoked or expired Google-side access. Removing AdCopilot from your Google account's third-party access, a Google Workspace policy change, or a security event on the Google account all invalidate the stored refresh token. The fix is to reconnect in your client and re-consent with the same Google account; the connection starts working again, seat and history intact.

### Does reconnecting change my connector address or lose my history?

No. Reconnect restores the same connection — same seat, same audit history — by replacing the stored Google credential. The URL never changes anyway; it is the same for everyone. The only requirement is identity: the reconnect must use the same Google account that created the connection, and a reconnect attempt from a different Google account is refused. Nothing needs re-pasting into your clients.

### The agent refuses to delete things — is that a fault?

It is the design working. The four remove tools are never exposed to hosted connectors, and any mutate carrying a REMOVED status is refused server-side in any letter case. No configuration enables deletion, on any plan. If cleanup is the goal, pause instead — a paused item can be re-enabled, and pausing covers every legitimate tidy-up a delete would have done.

---

This is the markdown copy of https://adcopilot.cloud/tutorials/troubleshooting-your-ads-connector. The index of the site's pages is https://adcopilot.cloud/llms.txt.
