loopthink
Connect · Google Ads

Connect Google Ads to your AI client. For your whole team.

Google's official Ads MCP server is read-only, but it runs on one credential in one person's local config, and the API follows that person's account role. Pick the client your team uses:

Free for 2 servers, no card · Paid plans from €39 · EU-hosted

Your AI clientGoogle Ads

“Which search terms spent more than €100 last week without a single conversion?”

Used acct_7043912886_report from Google Ads

Three search terms, €444 last week, no conversion:

Search termCostClicksConv.
mcp gateway open source€ 184710
claude enterprise connector€ 142550
chatgpt intranet plugin€ 118490

Want me to list the campaigns they sit in?

  • read-only
  • as l.brandt
  • audit logged
An example answer in an AI client: the question “Which search terms spent more than €100 last week without a single conversion?” is answered from Google Ads through the tool acct_7043912886_report, and the call was read-only, as l.brandt, audit logged.

A silent loop through the whole setup. In Loopthink: the server overview, the New workspace dialog, the New MCP server dialog, the connection screen where Google access is granted, Google's own sign-in page, the read-only tools the grant published, and the connector page where the workspace URL is copied. Then in Claude: Settings with Connectors open, the Add custom connector dialog with the name and the URL, the page of options that follows, scrolled down and left untouched because everything on it is detected, and the connector, named after the company, switched on in a chat answering from Google Ads. A cursor moves to the button each screen is about.

  1. 1

    Start with a workspace in Loopthink. Its servers, its members and its key are separate from every other one.

  2. 2

    Add a server and pick Google Ads as its connection.

  3. 3

    Press Connect Google account.

  4. 4

    Sign in with Google. The consent screen asks for the Google Ads scope and nothing else.

  5. 5

    Tick the accounts or properties your team may report on. Each one publishes its own read-only tools.

  6. 6

    Copy the workspace connector URL.

  7. 7

    In Claude or ChatGPT, open Settings, then Connectors, then Add custom connector.

  8. 8

    Give it a name your colleagues will recognise, Acme Group rather than Loopthink, and paste the URL. Those two fields are the whole form.

  9. 9

    Continue opens a page of options. Scroll down past it and change nothing: Claude or ChatGPT has already read the server, so the sign-in and the OAuth client are detected and chosen for you, and there is no client id, no secret and no request header to type. Press Add at the bottom.

  10. 10

    Each colleague connects once with their own account, toggles it on in a chat, and asks. Every call runs as them, with their role, and lands in the audit log.

Who may do what

One matrix for Google Ads, whichever client asks.

ToolMarketingFinanceManagement
List accessible accounts Marketing may use List accessible accountsFinance may use List accessible accountsManagement may use List accessible accounts
Report per account Marketing may use Report per accountFinance may use Report per accountManagement may use Report per account
Query per account (GAQL) Marketing may use Query per account (GAQL)Finance may not use Query per account (GAQL)Management may not use Query per account (GAQL)
Field metadata Marketing may use Field metadataFinance may not use Field metadataManagement may not use Field metadata
Write actions off by defaultMarketing may not use Write actionsFinance may not use Write actionsManagement may not use Write actions

Masked for every role: user emails in change history, customer IDs of accounts nobody ticked.

You set this once. Every user in your team, in every client, gets exactly this.