If I connect an MCC, can Claude see every client?

Not until you tick them. Connecting a Google MCC lists what the token can reach and leaves every account unticked. The gateway answers only for the IDs you tick. The same rule applies to a Meta Business Manager. Un-ticking removes access on the next call rather than hiding a row the assistant might still name.

Can run_tool bypass the allowlist?

No. The ticked-account allowlist is checked server-side on every call, including calls routed through run_tool. search_tools, describe_tool and run_tool are routing tools, not a second permission system. If the inner tool names an unticked account, the call is refused with the allowed list named in the refusal.

Can an agent tick accounts for me?

No. Ticking accounts is human-only, like platform OAuth. Dashboard WebMCP tools, when they appear, are read only and will not grow a tick action. An agent should prepare the list, then hand you the dashboard link. If a vendor promises an agent can grant account access, that is a different product and a different risk.

Does this apply to Search Console and GA4?

Yes. Search Console properties and GA4 properties are accounts in the same picker. Connecting a Google identity that can see fourteen GA4 properties does not expose fourteen properties. You tick the property the assistant may query. The check is the same server-side rule as Google Ads customer IDs.

What happens if I untick during a chat?

The next call against that ID is refused. In-flight results from the previous call are already in the thread; we do not reach into the assistant to erase them. Spend, impressions and conversions are not stored here, so the next question cannot reread an unticked account. Untick before you share the connector with a broader seat.

Is this the same as a viewer seat?

No. Seats are people on your Get MCP Ads organisation. The allowlist is account IDs the gateway may touch, for every seat. A viewer seat still cannot write, and still cannot see unticked accounts. Free is one ad account and read only; Agency raises the account and seat caps. See pricing rather than treating the allowlist as a plan.

Markdown

How-to5 min readUpdated 30 Aug 2026

What a ticked-account allowlist is (and why MCC OAuth is not enough)

Connecting a Google MCC or a Meta Business Manager does not expose the client accounts under it. After OAuth, every account starts unticked. The gateway answers only for the IDs you tick, and the check runs server-side on every call, including calls routed through run_tool. That is 1 product rule, not a UI filter.

By The Get MCP Ads teamPublished by BENLY HLG30 Aug 2026

What this is about

Read this in

ChatGPT Claude Perplexity Gemini

Each one opens that assistant with this URL and asks it for a summary.

On this page

Why is MCC OAuth not enough?
Where is the check enforced?
When should you not rely on a hosted allowlist?
Questions

Key takeaways

OAuth on an MCC or Business Manager proves who you are, not which client the assistant may see.
After connect, the dashboard lists what the token can reach and every account starts unticked.
The allowlist is checked server-side on every call, including calls routed through run_tool.
Un-ticking an account removes access on the next call rather than hiding a row.
An agent cannot tick accounts. That step is human-only, like platform OAuth.
There is no X Ads source to tick. Microsoft Advertising is soon: OAuth exists, tools do not.

Why is MCC OAuth not enough?Link to this section

A Google MCC or a Meta Business Manager can sit over dozens of client accounts. The token the platform issues after OAuth can often list all of them. If the MCP server forwarded that list to the assistant, every client would be one prompt away. That is the default shape of many ads APIs. It is the wrong shape for an agency desk.

Get MCP Ads splits the two decisions. OAuth answers who connected the platform. The ticked-account allowlist answers which account IDs the gateway may use. Connecting does not tick. An agent cannot tick. See account scoping.

Where is the check enforced?Link to this section

On the server, on every tool call. Hiding a row in the dashboard is not the control. If the assistant names an unticked ID, the call is refused and the allowed list is named in the refusal. Routing through run_tool does not get around it. list_accounts only returns ticked accounts.

Connect the platform in the Get MCP Ads dashboard and complete OAuth as the account owner.
Open the account picker for that platform. Every account starts unticked.
Tick only the client accounts this assistant may reach.
Paste the hosted MCP URL into your MCP client and ask something that names a ticked account.
Untick an account when the job ends; the next call is refused for that ID.

When should you not rely on a hosted allowlist?Link to this section

You run a local MCP as the ads user on a machine that should see everything that token sees. Then the API's own ACL is the allowlist, and you operate that risk.
You need a source we do not ship. There is no X Ads. Microsoft Advertising has no tools yet, so ticking nothing there is not a workaround.
You are on Free and expected a write. Writes are absent, allowlist or not.

The URL is still https://mcp.getmcpads.com/mcp. The allowlist is not a second URL. It is a check on the first.

Get MCP Ads

Two ways to run Google Ads over MCP

Hosted
Google Ads MCP Server
38 tools behind one hosted URL, 7 of them writes that describe the change before they apply it. Nothing to install, and no key to paste.
Start free The server page
Open source, Apache 2.0
Run it yourself
The same server, published as a package you can read, audit and host on your own machine. No account, and no gateway in the path.
@getmcpads/google-ads-mcp-server
Repository

Questions

Answered in one paragraph each

Spec

Product: Get MCP Ads
Category: hosted MCP gateway
Protocol: MCP (Model Context Protocol)
Live sources: 6: Meta Ads, Pinterest Ads, Google Ads, TikTok Ads, Search Console, Google Analytics 4
Auth: OAuth 2.1 + dynamic client registration
Transport: HTTPS, streamable HTTP
Endpoint: https://mcp.getmcpads.com/mcp
Account access: ticked-account allowlist, checked server-side
Account access: ticked-account allowlist, checked server-side including run_tool
Pricing: Free 0 (1 ad account, 1 seat, 200 tool calls per period, read only). Pro 39 per month. Team 99 per month. Agency 199 per month.

Sources

Who wrote this

Written by the team that ships Get MCP Ads, the hosted MCP gateway this page describes. Every count on the page is read from the tool catalogue rather than typed out, so it cannot drift from what the gateway serves. BENLY HLG publishes the site; Get MCP Ads is a separate product from Benly and does not read Benly data.

This page as Markdown: /articles/ticked-account-allowlist.md. Every page under /articles answers to Accept: text/markdown as well.