Google Search Console

GSC CONNECT · READ-ONLY MCP

Your search data.
Your AI agent.

Bring Google Search Console into your agent workflow. Connect your own Google account to explore queries, pages and indexing with official data.

Google OAuthOfficial Google API5 read-only tools

ONE HOSTED ENDPOINThttps://gsc.yusihk.com/mcp

Streamable HTTP · OAuth 2.0

Connection steps →

CONNECT YOUR WAY

Start with the client you use.

The same MCP endpoint serves compatible clients. The connection and browser authorization flow are handled by your client.

Codex

Native MCP + plugin

Connect with native MCP and OAuth, or install the complete Codex plugin with its bundled Skill.

Connection steps

Claude Code

Remote HTTP + OAuth

Use Claude Code's HTTP MCP connection, then complete Google authorization from /mcp.

Connection steps

DeepSeek Harness

OAuth client required

Use an OAuth-capable MCP client or adapter. A URL-and-headers-only setup cannot complete this service's Google login.

Connection steps

Client names and logos identify the relevant products. They do not imply endorsement by their owners.

DOWNLOADS · 0.2.2

A connector, a Skill, or both.

Codex Plugin · 0.2.2

Codex connector package

A local marketplace with the remote MCP configuration, GSC Skill, icons and English / Traditional Chinese usage instructions.

Download plugin ZIP ↓

Agent Skill · 0.2.2

Standalone GSC Skill

Add GSC task and recovery guidance to an agent that supports Skills. Private data still needs an OAuth-capable MCP connection.

Download Skill ZIP ↓

The packages contain no credentials or server source. Existing installations using this endpoint already receive hosted service updates.

Full installation and upgrade guide ↗SHA-256 checksums ↗

QUICK START

Connect once. Choose a property. Ask a question.

Use Remote HTTP or Streamable HTTP. Leave Bearer token, custom headers, OAuth client ID, client secret, and resource fields empty; let the client handle OAuth.

Server URLhttps://gsc.yusihk.com/mcp

Connect in Codex

For the packaged route, unzip the download, keep the hidden .agents folder, open the extracted folder in desktop Codex and install Google Search Console Connect from the GSC Connect local marketplace. Start a new chat after connecting.

Or add the remote server with a supported Codex CLI:

codex mcp add google-search-console --url https://gsc.yusihk.com/mcp
codex mcp login google-search-console

Complete the Google login when prompted. If the server is already configured, use its Reconnect control instead of adding a duplicate.

Official client instructions ↗

Connect in Claude Code

Add the remote HTTP server, then open /mcp inside Claude Code and follow the browser authentication prompt.

claude mcp add --transport http google-search-console https://gsc.yusihk.com/mcp

/mcp

Choose the Google account with access to your Search Console property. These commands are for Claude Code; other Claude clients have their own connector controls.

Official client instructions ↗

Connect in DeepSeek Harness

First choose an MCP client plugin that supports browser OAuth, PKCE and client registration. The built-in bridge documented below exposes URL and headers configuration; those fields alone do not complete this service's OAuth flow.

In your OAuth-capable MCP client, add a remote HTTP server named google-search-console.
Set the server URL to https://gsc.yusihk.com/mcp and choose OAuth / browser authorization.
Complete Google authorization, enable its tools and ask for your Search Console properties.

Check the official MCP bridge documentation or review a community OAuth client such as dsh-mcp-manager. Community plugins are separate from the Codex ZIP offered here.

Official MCP bridge ↗Community OAuth client ↗

Five tools. Clear boundaries.

gsc_list_sites

List properties and permission levels.

gsc_site_overview

Summarize performance for a chosen property and date range.

gsc_query_search_analytics

Explore queries, pages, devices, countries and dates.

gsc_list_sitemaps

Read submitted sitemap processing status.

gsc_inspect_url

Read Google's indexed URL version. This is not a live URL test.

Put the data to work.

Compare the latest 28 complete days with the previous 28 days for this property.
Find high-impression pages with low CTR. Separate ranking, query mix and small samples.
Inspect this URL's Google index status and explain the canonical Google selected.

Your account. Read-only access.

Google authorization requests webmasters.readonly. This service cannot edit properties, submit or delete sitemaps, request indexing, transfer ownership or retrieve your Google password. Search Analytics may return top rows and omit low-volume queries.

When the connection needs attention.

Authentication expired?

Normal token expiry is handled by a refresh attempt. If Google rejects the saved authorization, use Reconnect for this MCP server, finish Google authorization and ask for the property list again. Prompt timing depends on the client.

Connected, but no tools?

Check the client's MCP status and start a new chat if it requires one to load newly connected tools. Installation, Google authorization and a successful data read are separate steps.

A property is missing?

Use a Google account that already has access to the property in Search Console. Repeated authorization does not grant new property permissions.

Network error or rate limit?

Try again after the connection recovers or the retry interval passes. Server configuration errors and temporary outages are not fixed by repeated Google consent.