Connect Google Search Console to ChatGPT. For your whole team.
Search Console has no MCP server of its own. The community ones run on one Google login or a service-account key that sits in every person's client config. Loopthink holds one service account with restricted rights on your property, gives every ChatGPT user in your team their own login, and lets SEO, Content and Management pull exactly the reports their role allows.
Free for your own server · Team from €99 · EU-hosted
Google Search Console in a chat client, today.
Today a team that wants Search Console in an AI client either adds every colleague as a user on the property, or one person's Google login ends up in a shared MCP config. The first means Full or Owner rights for people who only need a chart. The second means a key file that can also submit and delete sitemaps, and no record of who asked which query.
One matrix for Google Search Console. Roles across, tools down.
| Tool | SEO | Content | Management |
|---|---|---|---|
| Performance: queries & pages | SEO may use Performance: queries & pages | Content may use Performance: queries & pages | Management may use Performance: queries & pages |
| Countries & devices | SEO may use Countries & devices | Content may not use Countries & devices | Management may use Countries & devices |
| URL inspection | SEO may use URL inspection | Content may use URL inspection | Management may not use URL inspection |
| Sitemaps | SEO may use Sitemaps | Content may not use Sitemaps | Management may not use Sitemaps |
| Write actions off by default | SEO may not use Write actions | Content may not use Write actions | Management may not use Write actions |
Masked for every role: nothing personal by default; query strings that contain names or emails are masked.
You set this once. Every ChatGPT user in your team gets exactly this.
Once on the Google Search Console side, once in ChatGPT.
On the Google Search Console side
Google Cloud service account, Restricted user on the property
- 1
Google Cloud Console → IAM & Admin → Service Accounts → Create service account. Then Keys → Add key → Create new key → JSON. Enable the Search Console API on the project.
- 2
Search Console → your property → Settings → Users and permissions → Add user. Enter the service account's email and choose Restricted.
- 3
Paste the JSON key into Loopthink and pick the property. The key never reaches the AI client.
In ChatGPT
Custom connector, OAuth
- 1
An admin turns on Developer mode: Settings → Apps → Advanced settings. On Enterprise and Edu, admins first grant it under Permissions & Roles → Connected Data.
- 2
Workspace settings → Apps → Create: paste your Loopthink connector URL, choose OAuth, click Scan Tools, then Create. Publish the draft under Workspace settings → Apps → Drafts.
- 3
Each team member picks Loopthink from the tools menu in a chat, or @mentions it, and signs in once with their own account.
Full MCP apps are available on ChatGPT Business, Enterprise and Edu; Pro can connect read-only MCP servers in developer mode. Published apps show up in every member's Apps settings with the label custom.
Steps checked against the vendor documentation on 17 September 2026: Search Console API reference · Users and permissions · Service account keys · Developer mode and MCP apps in ChatGPT · Connectors in ChatGPT
Loopthink sits in between: it holds the key, shows ChatGPT a normal login, and applies your roles on every call.
Four checks between ChatGPT and Google Search Console.
- 01
Identify
OIDC/SSO against your own IdP, including Microsoft Entra. The call runs as the person who made it, never as a shared service account.
- 02
Authorize
Per-role, per-tool, read or write. Anything not explicitly granted never shows up in the tool list in the first place.
- 03
Mask
Field-level masking and pseudonymization applied on your side, before the result travels. The model never sees the raw field. Composio, AnythingMCP and both provider tunnels have no field-level masking at all.
- 04
Log
Who asked, which tool, which records, which fields were masked. One audit trail across every AI client, exportable for review.
What people actually ask ChatGPT about Google Search Console.
- SEO
“Which queries lost the most clicks in the last 28 days compared with the 28 before?”
- Content
“Is /blog/pricing-guide indexed, and what does Google say about the page?”
- Management
“Clicks and impressions this month versus last month, by country?”
Each question runs as the person who asked it, with that person's role. A Content colleague asking the SEO question gets the tools their own role allows, not an error, not more.
Four ways to put Google Search Console into ChatGPT.
| Native Google Search Console connector | Build it yourself | Enterprise gateways1 | Loopthink | |
|---|---|---|---|---|
| Per-user identity | One personal login, all its rights | Only if you build it | Yes | Yes, every call runs as the person who asked |
| Tool-level roles | No | Your code | Yes | Yes, write off by default |
| Field masking | No | Your code | Not documented | Yes, before the model sees the data |
| Published price | Included in your Google Search Console plan | Your engineers' time | Contact sales | Free, Team from €99 |
| EU company | No | Whatever you are | Mostly US | Yes, Germany |
Native Google Search Console connector: No official Google MCP server for Search Console. Community servers run on one OAuth login or a service-account key in the client config, sitemap writes included.
1 MintMCP, MCP Manager, Pomerium
Coming from one of them? Composio alternative · MintMCP alternative · MCP Manager alternative · AnythingMCP alternative
Also for
Connect another system to ChatGPT
Before you connect.
- Does every team member need their own Google Search Console account?
- No. Loopthink holds one key or token for Google Search Console. Your people sign in to Loopthink with their own identity, and every call to Google Search Console is logged under their name. Seats in Google Search Console stay where they are today.
- Who has to add the connector in ChatGPT?
- One person with the right to add connectors in your ChatGPT workspace, once. After that every team member enables it for themselves. Nobody pastes a key, nobody edits a config file.
- Where does the Google Search Console key live?
- In Loopthink, encrypted, in the EU. It never reaches ChatGPT and never reaches the people using the connector. Rotate it in Google Search Console whenever you like and paste the new one once.
- Can somebody write to Google Search Console from the chat?
- Not unless you switch it on. Write actions are a separate row in the permission matrix and are off for every role by default. If a role needs one write tool, you grant that one tool to that one role.
- What does the model see?
- The result of the tool call, after masking. Fields you mark as personal, such as emails, names or card details, are masked before the answer travels to ChatGPT. The model gets the numbers, not the people.
- Is there an audit trail?
- Yes. Who asked, which tool, which parameters, which fields were masked, when. One log across every client your team uses, exportable for review.
- What does it cost?
- Free for one person and your own MCP server, forever. Team starts at €99 per month and covers the built connector, per-person identity, roles, masking and audit for the whole team. Prices are on the pricing page, no call needed.
- We already run our own MCP server for Google Search Console. 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.
Google Search Console in ChatGPT, with rules.
One key in Loopthink, one login per person, one matrix that decides who may do what.
Free for your own server · Team from €99 · EU-hosted