Can my team share one Google Search Console connection?

Yes. One person connects Google Search Console in Elaichi and shares it with a team, and nobody else ever handles a Google credential. Each teammate still signs in to Elaichi as themselves, so every question asked of Google Search Console is logged under their own name.

Analytics

Google Search Console MCP connector

The Google Search Console connector brings your sites, sitemaps, search analytics, and URL inspection results into Claude, ChatGPT, Cursor, and the Elaichi Agent, so each person asks about search performance inside their own Google access.

Connect on Elaichi How to connect

How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
One address. https://api.elaichi.ai/mcp, the same for every user.
Their own access. An agent never gets more than the person it acts for.

10 tools

How to connect

How to connect Google Search Console to Claude, ChatGPT or Cursor

Two steps, about a minute.

In Elaichi

Connect Google Search Console once

Open Connections, choose Add connection, and pick Google Search Console.
Optionally set Share with to give a team access, then press Connect.
Approve it in Google Search Console. Google Search Console's own window opens. Whoever approves it decides what this connection can reach.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

google search console

All categories

Google Search Console

Allium

Amplitude

Artie

AthenaHQ

Botify

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Google Search Console MCP connector for Claude

1

Open Customize, then Connectors.
2

Press Add.
3

Name it, paste the MCP server URL, then Continue.

https://api.elaichi.ai/mcp
4

Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Google Search Console MCP connector for Claude Code

1

In a terminal, run claude mcp add with the endpoint.

https://api.elaichi.ai/mcp
2

Start Claude Code and run /mcp.
3

Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Google Search Console MCP connector for ChatGPT

1

Open Plugins, then press the + button.
2

Name it and paste the endpoint into Server URL.

https://api.elaichi.ai/mcp
3

Leave Authentication on OAuth, then tick the risk acknowledgement.
4

Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Google Search Console MCP connector for Cursor

1

Open ~/.cursor/mcp.json.
2

Add the endpoint under mcpServers.

https://api.elaichi.ai/mcp
3

Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Google Search Console to any MCP client

1

Add the endpoint as a remote MCP server.

https://api.elaichi.ai/mcp
2

Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Connect Google Search Console on Elaichi See pricing

Use cases

What teams do with Google Search Console through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

SEO

See which queries moved after a release

Ask for clicks, impressions, and average position by query for the two weeks either side of a site change. Spot the pages that gained or lost ground without exporting a spreadsheet.
Content

Learn what a page really ranks for

Before rewriting an article, pull the queries that already bring it impressions in Google Search Console. Keep the wording that works and fix the headings that do not.
Web

Confirm a new page is indexed

Run a URL inspection on the page you shipped this morning and get back its index status and last crawl. If it is missing, submit the sitemap that covers it from the same conversation.
Marketing

Report landing page search traffic weekly

Ask for clicks and impressions on the campaign landing pages for the last seven days, grouped by page. Paste the answer straight into the Monday update.
Client services

Pull a client's numbers before the call

List the client's sites in Google Search Console and summarize search performance for each one in plain language. Walk into the review already knowing which site needs attention.
Leadership

Get a plain summary of search performance

Ask how organic search is trending across every site the company owns and get an answer in sentences rather than charts. Follow up with one more question instead of opening another tool.

Try asking

“Which queries lost the most clicks on our site this month?”
“Is our pricing page indexed, and when was it last crawled?”
“List every sitemap we have submitted and flag any with errors.”

See all 10 Google Search Console tools below

Compare

Elaichi vs Zapier MCP vs Composio for Google Search Console

All three can connect Google Search Console to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Google Search Console, by what to check
What to check	Elaichi	Zapier MCP	Composio
Where the AI connects	One address for the whole organization. `https://api.elaichi.ai/mcp`	A server per member, created at sign-in.	An MCP endpoint per team, or an SDK.
Control over Google Search Console tools	Allow or restrict single Google Search Console tools, per role or user.	App and action restrictions on the account.	Role permissions, down to the action.
Record of calls	One audit entry per Google Search Console call.	A History tab of tool calls.	A log of every tool call.
Single sign-on	SAML or OIDC, plus SCIM, on Gold.	SAML on Enterprise.	SAML and OIDC on Enterprise.
Price	$15 per user per month.	2 tasks per successful call.	Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Google Search Console tools for your AI agents

10 tools are ready to call through Elaichi's MCP endpoint the moment you connect Google Search Console, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Google Search Console gets you

6 screens from the product, each doing one job for your Google Search Console account.

The agent

Ask about search performance in plain language.

Three starter prompts pull live clicks, impressions, and index status from Google Search Console.

sites
sitemaps
search analytics
url inspections

Ask Elaichi to work across your apps.

Which queries lost the most clicks on our site this month?

Is our pricing page indexed, and when was it last crawled?

List every sitemap we have submitted and flag any with errors.

Also runs in Claude, ChatGPT or Cursor

MCP clients

One endpoint connects Google Search Console everywhere.

Claude, ChatGPT, and Cursor share one governed endpoint, with no SDK and no shared API key.

ElaichiMCP clients

Claude

ChatGPT

Cursor

Copy the endpoint

https://api.elaichi.ai/mcp

Client	Connected by	Status	Last used
Claude	E Emily Carter	• Connected	4 minutes ago
Cursor	M Megan Brooks	• Connected	2 hours ago
ChatGPT	R Ryan Hayes	• Connected	Yesterday

Tool catalog

10 tools cover Google Search Console without code.

Sites, sitemaps, search analytics, and URL inspection, all cataloged with no connector code to write.

List all Google Search Console sites
Get single Google Search Console site by ID
Create a Google Search Console site
Delete a Google Search Console site by ID

ElaichiTools

Tool	Action	Description
List all Google Search Console sites	List	List the Google Search Console sites the authenticated user has access to, together with each site's permission level. Returns: siteUrl, permissionLevel.
Get single Google Search Console site by ID	Get	Get a single Google Search Console site by id — the site's URL as defined by Search Console (e.g. http://www.example.com/ for a URL-prefix property or sc-domain:example.com for a Domain property). Returns: siteUrl, permissionLevel. Required: id.
Create a Google Search Console site	Create	Add a site to the user's Google Search Console sites. Returns an empty response body on success. Required: site_url (e.g. http://www.example.com/ for a URL-prefix property or sc-domain:example.com for a Domain property).
Delete a Google Search Console site by ID	Delete	Remove a site from the user's Google Search Console sites by id (the site URL, e.g. sc-domain:example.com). Returns an empty 204 response on success. Required: id.
List all Google Search Console sitemaps	List	List the sitemaps submitted for a site in Google Search Console, including entries from a sitemap index file. Returns: path, lastSubmitted, isPending, isSitemapsIndex, lastDownloaded, warnings, errors, contents. Required: site_url.

Toolboxes

Each team works from its own toolbox.

SEO, Content, and Web each get a toolbox scoped to their Google Search Console work.

SEO
Content
Web
Marketing

ElaichiToolboxes

Name	Source template	Tools	Created
SEO toolbox Google Search Console · queries, clicks, and positions	Google Search Console starter	18	Mar 4, 2026
Content toolbox Google Search Console · pages and the queries that find them	—	9	Mar 2, 2026
Web toolbox Google Search Console · sitemaps and index status	—	24	Feb 27, 2026
Marketing toolbox Google Search Console · campaign landing page traffic	Google Search Console starter	6	Feb 19, 2026
Client services toolbox Google Search Console · client sites and reporting	—	31	Jan 30, 2026
Leadership toolbox Google Search Console · search performance summaries	—	12	Jan 22, 2026

Shared connections

Teammates work through a connection, never a credential.

One person connects Google Search Console and shares it with teams, nobody else handles a login.

SEO
Content
Web
Marketing

ElaichiConnections

Connection	Scope	Status	Access
GO Google Search Console (SEO) Connected by Emily Carter	Personal	• Active	1 team · 6 members
GO Google Search Console (Content) Connected by Jake Morgan	Organization	• Active	3 teams · 24 members
GO Google Search Console (Web) Connected by Megan Brooks	Organization	• Active	2 teams · 11 members
GO Google Search Console (Marketing) Connected by Tyler Reed	Personal	• Needs re-auth	1 team · 3 members
GO Google Search Console (Client sites) Connected by Ryan Hayes	Personal	• Active	Not shared
GO Google Search Console (Leadership) Connected by Ashley Parker	Personal	• Active	2 teams · 9 members

Audit log

Every Google Search Console call is on record.

When, who, what happened, and which site or sitemap, in an append-only log.

When
Who
What happened
Type

ElaichiAudit log

When	Who	What happened	Type
2 minutes ago Mar 6, 2026, 3:10 PM	E Emily Carter [email protected]	Restriction Created	Access
8 minutes ago Mar 6, 2026, 3:04 PM	J Jake Morgan [email protected]	Restriction Updated	Access
14 minutes ago Mar 6, 2026, 2:58 PM	M Megan Brooks [email protected]	Role Assigned	Access
20 minutes ago Mar 6, 2026, 2:52 PM	T Tyler Reed [email protected]	Google Search Console Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	R Ryan Hayes [email protected]	Google Search Console Sites Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	A Ashley Parker [email protected]	Google Search Console Sites List	Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule starts the weekly search digest.

Search analytics are fetched, grouped by site, drafted into a digest, approved, then posted back.

Google Search Console digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

Run now

✓

Schedule

Every weekday at 8:00 AM

0.2s
✓

Fetch sites

Google Search Console

1.4s
✓

Group by owner

Transform

0.1s
✓

Draft the digest

Agent step

Ran with 4 tools, returned a structured summary

6.2s
Approve the digest

Needs approval

Assigned to Michael Brennan

Approve Deny
Post the digest

Google Search Console

Queued

Collections and dashboards

Search health numbers arrive without being asked for.

Four metrics, a 14 day chart, and a team breakdown, computed with no model involved.

Google Search Console health

Refreshed 4 minutes ago · every 15 minutes · from the sites collection

Live

Sites

1,284 ↓ 12%

Sitemaps

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Sites created

Last 14 days

By team

Share of activity

SEO 34%

Content 27%

Web 21%

Marketing 18%

Related connectors

More from the catalog

Browse all 650+ connectors →

FAQ

Frequently asked questions

How do I connect Google Search Console to Claude?

Connect Google Search Console in Elaichi by signing in with your Google account over OAuth, the same consent screen you see when granting any app access to Google. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude then asks about your sites, sitemaps, and search analytics as you.

Does Google Search Console work with ChatGPT and Cursor as well as Claude?

Yes. Once Google Search Console is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent. You connect Google Search Console once and every client picks it up.

What can an AI agent actually do with my Google Search Console data?

It can list the sites you own in Google Search Console, pull search analytics such as clicks, impressions, click-through rate, and position by query or page, and tell you whether a specific URL is indexed and when it was last crawled. It can also list, submit, and remove sitemaps, and add or remove sites. Short, specific asks such as a page name and a date range get better answers than long paragraphs.

Does connecting Google Search Console give the AI every site in my account?

No. The AI works inside the access of the person who signed in, so it only sees the Google Search Console sites and permission levels that person already has in Google. Elaichi can narrow that further with restrictions, and it can never widen it beyond what Google has granted.

Can I stop an agent from deleting or changing things in Google Search Console?

Yes. Restrictions in Elaichi apply per action, so you can allow reading search analytics and inspecting URLs while blocking the removal of sites or sitemaps. A restricted action is left out of what the AI client can see for Google Search Console and cannot be called, whatever the prompt says.

What happens to a Google Search Console connection when someone leaves?

Offboarding that person in Elaichi ends their access to Google Search Console through every AI client at once. A connection they shared keeps working for everyone else on the team. If you want it gone entirely, disconnecting Google Search Console once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client.

Does the Google Search Console MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Google Search Console is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Google Search Console?

Yes. Both let Claude, ChatGPT or Cursor use Google Search Console. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Google Search Console call.

How is Elaichi different from Composio for Google Search Console?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Google Search Console: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Google Search Console in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Connect Google Search Console Talk to us

Works with: and any other MCP client, or the Elaichi Agent.
When the trial ends: Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.