Fennec SEO · Agent tools

Your Search Console data. In your agent.

Connect your own Google account, choose a Search Console property, and ask your agent to investigate search performance, sitemaps and indexing signals.

Read-only access
Google OAuth
Remote HTTP

Choose your agent Explore the tools

One connection for your GSC workflow

MCP server URL

https://gsc.yusihk.com/mcp

Add this address in your agent’s MCP settings. Sign in through Google when the agent asks you to connect.

Server name: fennec-gsc
Transport: Streamable HTTP / remote HTTP
Authentication: OAuth · sign in with Google
Google permission: webmasters.readonly

You do not need to create a Google Cloud project or enter a Google client ID, client secret, API key or bearer token.

From connection to a useful answer

1
Add the server
Choose a client below and add the MCP URL.
2
Authorize with Google
Review the app name and read-only permission shown by Google, then select your account.
3
Choose your property
Ask the agent to list accessible sites. Use the exact siteUrl returned for subsequent requests.

01 / CONNECT

Connect your agent

Choose the setup for the application you use. Custom MCP availability can depend on your client version, plan and workspace policy. After sign-in, list your sites to confirm the connection.

CodexCLI · IDE · desktop

Run the add command in your terminal, then start OAuth login.
Complete Google sign-in in the browser. Use codex mcp list or /mcp to check the connection.
In the desktop app, you can also add a remote server in MCP settings using the URL above.

Terminal

codex mcp add fennec-gsc --url https://gsc.yusihk.com/mcp
codex mcp login fennec-gsc
codex mcp list

Official setup guide

Claude CodeHTTP server · browser sign-in

Run the command below to add the remote HTTP server.
Open Claude Code and run /mcp. Select the server and follow the authentication flow.
Return to the conversation and ask it to list your Search Console properties.

Terminal

claude mcp add --transport http fennec-gsc https://gsc.yusihk.com/mcp

Official setup guide

Cursor.cursor/mcp.json

Add this entry in .cursor/mcp.json for the project, or ~/.cursor/mcp.json for your user.
Open Cursor’s MCP settings and connect the server. Complete the browser OAuth flow when prompted.
Enable the server’s tools for the agent before your first request.

mcp.json

{
  "mcpServers": {
    "fennec-gsc": {
      "url": "https://gsc.yusihk.com/mcp"
    }
  }
}

Merge this server entry into your existing configuration; keep any other servers you already use.

Official setup guide

VS Code / Copilot.vscode/mcp.json

Add the configuration below to .vscode/mcp.json in your workspace.
Start the server from the configuration’s controls or MCP commands, and complete sign-in when prompted.
In agent chat, enable the GSC tools in the tools picker.

mcp.json

{
  "servers": {
    "fennec-gsc": {
      "type": "http",
      "url": "https://gsc.yusihk.com/mcp"
    }
  }
}

Merge this server entry into your existing configuration; keep any other servers you already use.

Official setup guide

ClaudeWeb · desktop · custom connector

Open Customize → Connectors → Add custom connector, where your account permits it.
Use the name Fennec SEO GSC and server URL https://gsc.yusihk.com/mcp.
Choose OAuth sign-in and automatic client registration if a registration method is requested. Complete Google sign-in, then enable the connector in your chat. Organization owners may need to add it first.

Official setup guide

ChatGPTCustom MCP · workspace access

Open the MCP or custom connector controls available in your ChatGPT settings. Your workspace may need to enable custom MCP connections.
Add a remote server named Fennec SEO GSC using https://gsc.yusihk.com/mcp and OAuth authentication.
Save, connect and complete Google sign-in. Enable the connection’s tools for the conversation. If your account does not expose custom MCP setup, use one of the other clients above.

Official setup guide

02 / TOOLS

Five tools. Your own authorized properties.

The connector reads Google’s official Search Console APIs. It cannot edit properties, submit or delete sitemaps, request indexing, or change your website.

gsc_list_sites

Choose a property

List accessible sites and permission levels, including URL-prefix and domain properties.

gsc_site_overview

Get an overview

Summarize performance for a property with an explicit date range.

gsc_query_search_analytics

Investigate performance

Query clicks, impressions, CTR and position by page, query, device, country and date.

gsc_list_sitemaps

Review sitemap processing

Read submitted sitemaps, processing details, warnings and errors.

gsc_inspect_url

Inspect Google’s indexed version

Read indexing, crawl and canonical information. This is not a live URL test.

03 / ASK

Start with a concrete question

Connect and choose

List the Search Console properties I can access and let me choose one. Use its exact siteUrl in later requests.

Compare performance

For my selected property, compare the latest two complete 28-day windows using final Web Search data. State the date ranges, clicks, impressions, CTR and average position; keep site-wide changes separate from page-level diagnoses.

Find a page to investigate

For my selected property, find pages with impressions but few clicks in the latest complete 28 days. Show the page and visible query evidence before suggesting a title change. Explain top-row and missing-row limits.

Check indexing evidence

Inspect the indexed version of a URL I provide in my selected property. Report the crawl, indexing and canonical findings, and say which checks still require a live test.

Your account controls the access

Google handles sign-in. The connector uses your authorization credentials to read GSC data and return it to your agent; the agent application also processes the returned data. Only properties available to the Google account you authorize are accessible.

Connector privacy ↗ Connector terms ↗ Manage Google connections ↗

Search Analytics can return top rows rather than every query. Missing rows are not evidence of no demand. Ask for explicit dates and dataState; an indexing inspection describes Google’s recorded version, and a successful read does not guarantee indexing or rankings.

Connection questions

Why does the server URL return 401 in my browser?

The MCP endpoint requires an OAuth access token. Add it through your agent’s MCP settings and use the sign-in flow; opening the URL directly is not a connection test.

A site is missing. What should I check?

Confirm that you authorized the correct Google account and that it already has access to the property in Search Console. URL-prefix and domain properties have different siteUrl values.

I signed in, but the tools are missing.

Check that the server is enabled in the client and the tools are enabled for this conversation. Reopen or refresh the client’s connection view; some clients need a new conversation to load new tools.

Can I connect any agent?

Use a client with remote HTTP MCP and OAuth support. The setup examples follow the linked client documentation; each client still needs a successful sign-in and tool call to confirm access in your environment.

GSC management →AI SEO →Agent SEO audit →SEO audit →GSC performance guide →

Your Search Console data. In your agent.

One connection for your GSC workflow

From connection to a useful answer

Add the server

Authorize with Google

Choose your property

Connect your agent

Five tools. Your own authorized properties.

Choose a property

Get an overview

Investigate performance

Review sitemap processing

Inspect Google’s indexed version

Start with a concrete question

Connect and choose

Compare performance

Find a page to investigate

Check indexing evidence

Your account controls the access

Connection questions

Turn evidence into the next check

Privacy & Cookies

Privacy & Cookies

gdpr.settings