AnythingMCP and Loopthink are both German, both connect Google Ads and Search Console to Claude and ChatGPT, and both start at €19 a month. If you are choosing between the two for your marketing data, the differences are not in the price. They are in who sets up Google, what the tools can write, and what reaches the model.
Where the two are alike
Credit first, because it is earned. AnythingMCP from helpcode.ai GmbH logs every tool call with input, output, duration and status, has roles (admin, developer, viewer) with tools whitelisted per role, runs its cloud in Frankfurt, and offers a Community Edition under AGPL-3.0 that you can host yourself at no cost. It connects to claude.ai and ChatGPT over OAuth and to other clients with an API key. Its Google Ads connector is read-only: its own FAQ says there is no tool to pause, create or edit anything. That is a sound default and more than most options in our Google Ads comparison offer.
We have a general side-by-side of the two platforms on AnythingMCP alternative. This article is only about Google.
Difference one: who brings the Google OAuth client
AnythingMCP's Google Ads guide starts in the Google Cloud Console: create a project, configure a consent screen, create a web OAuth client, paste its ID and secret, then authorize with your Google user. The guide is careful and correct, including a warning that matters: a consent screen left in Testing mode revokes the refresh token after seven days, and the connector stops working a week later.
In Loopthink there is no Cloud project on your side. You press Connect Google account, Google shows its consent screen for our verified app, and you pick the accounts. The access level for the Google Ads API sits with our Cloud project. That is less control (you cannot raise your own quota tier) and much less setup, and no seven-day expiry to forget about.
If your IT wants every OAuth client in your own Google organization, AnythingMCP's model fits that, and self-hosting it fits even better.
Difference two: what the Search Console tools can write
AnythingMCP's Search Console connector has eleven tools, and four of them write: submit a sitemap, delete a sitemap, add a site, remove a site. Per-tool whitelisting lets an admin switch them off for a role, so this is manageable. But the Google token behind the connector carries the permission either way.
Loopthink signs in to Search Console with the read-only scope, so the token cannot write, whatever a tool or a model tries. Each property publishes a performance and a sitemaps tool and nothing else. If you need sitemap submissions from a chat, that is a reason to choose AnythingMCP. If you do not, a read-only token is the simpler guarantee.
Difference three: the search terms
Neither platform can change what Google returns, but each decides what goes on to the model. AnythingMCP has per-tool response mapping that can drop fields or replace them with placeholders, which you configure per tool. In Loopthink the search terms of the Search Console QUERY dimension stay off until you switch them on, and then roles decide who gets them; field masking by name works the same way across every connector, Google Analytics' user dimensions included.
Difference four: one Google account, many people
Both platforms connect Google through one authorizing account, as does every other hosted option we have looked at. Google Ads and Search Console see that account. What differs is how much the platform knows about the person in front of it. AnythingMCP's Cloud plans include users with roles; SSO and SCIM come with self-hosting or Enterprise. In Loopthink every chat user signs in as themselves on every plan, and from €49 you can bring your own identity provider.
Side by side
| AnythingMCP | Loopthink | |
|---|---|---|
| Google OAuth client | Your own, in your Cloud project | Ours, verified by Google |
| Google Ads tools | 17, read-only | Report and GAQL query per account, read-only by default; optional changes that can never enable a campaign |
| Search Console writes | 4 tools: sitemaps and sites | None, read-only scope |
| Google Analytics 4 | Listed, no guide found | Yes, read-only scope |
| Search terms to the model | Configurable response mapping | Off until enabled, then by role |
| Self-hosting | Yes, AGPL Community Edition | No; outbound-only runner for internal systems |
| Entry price | Starter €19 for one user, 7-day trial | Free for two connectors; Pro €19 for five people |
Sources: anythingmcp.com, its Google guides and pricing page, and the README on GitHub, as read on 17 October 2026. AnythingMCP shows prices including VAT for EU consumers; ours are net.
Which one fits
Choose AnythingMCP if you want to self-host, keep the Google OAuth client in your own organization, or build connectors for internal systems in a visual builder. Choose Loopthink if you want Google connected in a minute with a token that cannot write, the search terms held back by default, and your team signed in person by person from the first plan.