loopthink
Connect · Google Search Console

Connect Google Search Console to your AI client. For your whole team.

Search Console has no MCP server of its own. The community ones run on one Google login or a key file that sits in every person's client config, and they carry the write methods along with the reports. Pick the client your team uses:

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

Your AI clientGoogle Search Console

“Which pages lost the most clicks in the last 28 days?”

Used site_acme_com_search_analytics from Google Search Console

Three pages are down against the 28 days before:

PageClicksChangePosition
/pricing412−1188.8
/blog/rollout-guide268−7411.3
/integrations197−537.4

Want the queries behind them? Those are masked for your role.

  • read-only
  • as s.keller
  • queries masked
An example answer in an AI client: the question “Which pages lost the most clicks in the last 28 days?” is answered from Google Search Console through the tool site_acme_com_search_analytics, and the call was read-only, as s.keller, queries masked.

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 Search Console as its connection.

  3. 3

    Press Connect Google account.

  4. 4

    Sign in with Google. The consent screen asks for the Google Search Console 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 Search Console, whichever client asks.

ToolSEOContentManagement
List properties SEO may use List propertiesContent may use List propertiesManagement may use List properties
Performance per property SEO may use Performance per propertyContent may use Performance per propertyManagement may use Performance per property
Sitemaps per property SEO may use Sitemaps per propertyContent may not use Sitemaps per propertyManagement may not use Sitemaps per property
Search terms (QUERY) SEO may use Search terms (QUERY)Content may not use Search terms (QUERY)Management may not use Search terms (QUERY)
Write actions off by defaultSEO may not use Write actionsContent may not use Write actionsManagement may not use Write actions

Masked for every role: search queries, the text real people typed, until an admin enables the QUERY dimension on the connection.

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