# 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.

Source: https://elaichi.ai/connectors/googlesearchconsole/

## Facts

| | |
| --- | --- |
| Application | Google Search Console |
| Category | Analytics |
| AI tools | 10 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Google Search Console is connected

- 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.

## Connect Google Search Console in Elaichi

This happens once for the organization, before any client is involved.

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

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Google Search Console tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Google Search Console MCP connector for Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

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

## Connect Google Search Console to any MCP client

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

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

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete data and remove access", which you tick yourself. Calling a Google Search Console tool needs "Run your connected tools". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Run your connected tools, which can also delete in connected apps and cannot be undone.

## What teams do with Google Search Console through Elaichi

### See which queries moved after a release

SEO. 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.

### Learn what a page really ranks for

Content. 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.

### Confirm a new page is indexed

Web. 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.

### Report landing page search traffic weekly

Marketing. 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.

### Pull a client's numbers before the call

Client services. 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.

### Get a plain summary of search performance

Leadership. 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.

## 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.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## 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 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.

### 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.

## All 10 Google Search Console tools

Every tool below is callable through https://api.elaichi.ai/mcp once Google Search Console is connected, subject to the toolbox it is in and the restrictions on the caller.

- **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.
- **Get single Google Search Console sitemap by ID** (Get). Get a single sitemap in Google Search Console by id (the sitemap's feedpath URL). Returns the sitemap resource including path, lastSubmitted, isPending, isSitemapsIndex, type, lastDownloaded, warnings, errors, and contents. Required: id, site_url.
- **Google Search Console sitemaps submit** (Action). Submit a sitemap for a site in Google Search Console so Google crawls and processes it. Returns an empty 204 response on success. Required: feedpath (the URL of the sitemap to add), site_url.
- **Delete a Google Search Console sitemap by ID** (Delete). Delete a sitemap from a site in Google Search Console by id (the sitemap's feedpath URL). Returns an empty 204 response on success. Required: id, site_url.
- **List all Google Search Console search analytics** (List). Query Google Search Console search traffic data for a property, grouped by dimensions you define. Returns rows with keys, clicks, impressions, ctr, and position, sorted by clicks descending. Required: site_url, startDate, endDate. Max 25,000 rows per request; Search Console may return only top rows, not all data.
- **Google Search Console URL inspection search** (Search). Inspect a URL's index status in Google Search Console. Returns the UrlInspectionResult object detailing the URL's index status. Required: inspectionUrl, siteUrl. Only the version in Google's index is checked; live URL testing is not supported.