Google Ads in Claude. In five minutes.
Sign in with Google, paste one URL into Claude, ask. Reports only by default, hosted in the EU, no developer token.
Free for 2 connectors, no card · Pro €19 · EU-hosted
“Which search terms spent more than €100 last week without a single conversion?”
Three search terms, €444 last week, no conversion:
| Search term | Cost | Clicks | Conv. |
|---|---|---|---|
| mcp gateway open source | € 184 | 71 | 0 |
| claude enterprise connector | € 142 | 55 | 0 |
| chatgpt intranet plugin | € 118 | 49 | 0 |
Want me to list the campaigns they sit in?
- read-only
- logged
Three steps. The third one is asking.
- 1
Sign in with Google
Pick the ad accounts your team may see. Loopthink publishes reporting tools only, changes stay off.
- 2
Paste one URL into Claude
Add a custom connector with a name and the URL. That is the whole form.
- 3
Ask
"Which search terms spent more than €100 last week without a single conversion?" Every answer comes from your data, every call is logged.
Show all steps
- 1
Start with a workspace in Loopthink. Its servers, its members and its key are separate from every other one.
- 2
Add a server and pick Google Ads as its connection.
- 3
Press Connect Google account.
- 4
Sign in with Google. The consent screen asks for the Google Ads scope and nothing else.
- 5
Tick the accounts or properties your team may report on. Each one publishes its own read-only tools.
- 6
Copy the workspace connector URL.
- 7
In Claude, open Settings, then Connectors, then Add custom connector.
- 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
Continue opens a page of options. Scroll down past it and change nothing: Claude 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
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.
Steps checked against the vendor documentation on 17 September 2026: Google Ads API MCP server · Google Ads Query Language · Account access levels · API access levels · Get started with custom connectors using remote MCP · Use connectors to extend Claude's capabilities
What people actually ask Claude about Google Ads.
- Marketing
“Which search terms spent more than €100 last week without a single conversion?”
- Finance
“Spend this month by campaign, against each campaign's monthly budget?”
- Management
“Cost per conversion this quarter versus last quarter?”
Google has an MCP server for Ads. Why Loopthink?
Google's own Ads MCP server runs on your laptop. It needs a cloud project, a developer token and a Python install, and it does not work in Claude in the browser. It also runs on one person's credential.
Loopthink runs hosted and gives Claude a URL. Every colleague signs in with their own account and sees only what you ticked.
Before you connect.
- Does every team member need their own Google Ads account?
- No. One Google sign-in in Loopthink covers the whole team, and it is the only Google account involved. Your people sign in to Loopthink with their own identity, every call is logged under their name, and the seats in Google Ads stay exactly where they are today.
- Who has to add the connector in Claude?
- One person with the right to add connectors in your Claude workspace, once. After that every team member enables it for themselves. Nobody pastes a key, nobody edits a config file.
- Where does the Google Ads key live?
- There is none, and that is the point. A Google sign-in grants Loopthink access to the Ads API, which is stored encrypted in the EU, is never returned by the API and never reaches Claude or the people using the connector. You revoke it any time at myaccount.google.com/permissions, and nobody has to rotate or paste anything.
- Can somebody change a campaign or a budget from the chat?
- Only if you allow it, and nothing is ever switched on. By default the connection publishes no write tools and the gateway lets only the reporting endpoints through; the Ads API has no read-only scope to ask for, so the limit sits in the gateway. Tick Allow changes on a connection and each account gets one change tool: it creates and edits budgets, campaigns, ad groups, ads and keywords, and pauses them. Nothing is enabled or removed, so a new campaign starts paused and going live stays a click in Google Ads. Billing, users and account settings stay out of reach, every change is validated by Google first, and the audit log keeps each value before and after.
- What does it cost?
- Free for one person and two connectors, no card. Pro is €19 a month for up to five people and every connector on the site, with roles, field masking and a 30-day audit. Team is €49 for ten people and adds your own REST APIs and SQL databases, your own domain and your own identity provider. No call needed.
- We already run our own MCP server for Google Ads. Does it still work?
- Yes. Point it at Loopthink and it inherits the same login, roles, masking and audit. Nothing on the server has to change.
One matrix for Google Ads. Roles across, tools down.
| Tool | Marketing | Finance | Management |
|---|---|---|---|
| List accessible accounts | Marketing may use List accessible accounts | Finance may use List accessible accounts | Management may use List accessible accounts |
| Report per account | Marketing may use Report per account | Finance may use Report per account | Management 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 metadata | Finance may not use Field metadata | Management may not use Field metadata |
| Write actions off by default | Marketing may not use Write actions | Finance may not use Write actions | Management 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 Claude user in your team gets exactly this.
Google Ads runs on the free tier: two connectors for one person, no card. Roles, a login for every colleague and field masking start at €19 a month with Pro. See the plans
Also for
Connect another system to Claude
Google Ads in Claude, in five minutes.
One sign-in in Loopthink, one URL in Claude, one login per colleague.
Free for 2 connectors, no card · Pro €19 · EU-hosted