mcpField
Q
QuerySail: Google Search Console

QuerySail: Google Search Console

Remote
querysail.comBusiness & Marketing0Updated today

About QuerySail: Google Search Console

QuerySail: Google Search Console is a hosted, read-only MCP server for querying Search Console data in natural language. It also supports URL inspection, sitemap review, and period comparisons.

Key features

  1. 01Query clicks, impressions, and rankings
  2. 02Filter by query, page, or device
  3. 03Compare performance across periods
  4. 04Inspect URL indexing status
  5. 05Review submitted sitemaps

Use cases

  1. 01Analyze changes in search traffic
  2. 02Find queries with impressions
  3. 03Investigate indexing and canonical URL status

MCP support

A hosted Streamable HTTP endpoint exposes read-only Search Console tools to MCP clients using OAuth 2.1 authentication.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.querysail.com/gsc/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

QuerySail: Google Search Console MCP server

QuerySail logo

QuerySail is a hosted, read-only MCP server for Google Search Console. Connect it to ChatGPT, Claude, Codex, Cursor or VS Code, sign in, connect your Google account once, and ask about your search traffic in plain language. There is nothing to install and no API key to paste.

This repository holds the public listing files (MCP Registry server.json, a Claude Code plugin, client configs). The service itself is hosted at querysail.com; its source is not published here.

Tools

All tools are read-only. QuerySail cannot submit sitemaps, request indexing or change any Search Console setting.

ToolWhat it does
list_propertiesLists the Search Console properties your connected Google accounts can read, with exact IDs and permission level.
get_performanceClicks, impressions, CTR and average position, as totals or by date, hour, query, page, country, device or search appearance, with filters. Covers web, image, video, news, Discover and Google News results.
compare_performanceCompares two periods (previous period, same weekdays a year earlier, or custom dates) and lists the queries, pages, countries or devices that gained or lost the most.
inspect_urlsInspects up to 20 URLs: whether each is on Google, why not, last crawl, robots.txt and noindex blocking, and the canonical Google chose.
list_sitemapsLists submitted sitemaps with when Google last read them, URL counts, errors and warnings.

Example prompts

  • Which of my pages got the most clicks from Google in the last 28 days?
  • What changed in my search traffic compared with the previous 28 days?
  • Is my homepage indexed on Google, and which canonical did Google choose?
  • Which queries rank on page two for my blog, sorted by impressions?

Setup

You need a QuerySail account with Google Search Console connected: sign up at https://querysail.com. Each client below opens a browser window to sign in the first time.

Claude Code
claude mcp add --transport http --scope user querysail-gsc https://mcp.querysail.com/gsc/mcp

Then run /mcp, choose querysail-gsc and sign in. Or install it as a plugin, which also adds a Search Console analysis skill:

/plugin marketplace add querysail/querysail-gsc
/plugin install querysail-gsc@querysail
Claude Desktop and claude.ai

Open Customize → Connectors, select + Add → Add custom connector, name it QuerySail and paste https://mcp.querysail.com/gsc/mcp as the server URL.

ChatGPT

Turn on Developer mode under Settings → Security and login, go to chatgpt.com/plugins, select the plus button and paste the endpoint as the connection URL.

Grok

Go to grok.com/connectors, select New Connector → Custom, paste https://mcp.querysail.com/gsc/mcp as the MCP server URL and sign in. On Grok Business and Enterprise plans a team admin first adds it at console.x.ai under Grok Business → Connectors.

Codex
codex mcp add querysail-gsc --url https://mcp.querysail.com/gsc/mcp
codex mcp login querysail-gsc
Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "querysail-gsc": { "url": "https://mcp.querysail.com/gsc/mcp" }
  }
}
VS Code

Run MCP: Add Server, choose HTTP and paste the endpoint, or add to mcp.json:

{
  "servers": {
    "querysail-gsc": { "type": "http", "url": "https://mcp.querysail.com/gsc/mcp" }
  }
}
Clients that only run local commands

Use the mcp-remote bridge (needs Node.js):

{
  "mcpServers": {
    "querysail-gsc": { "command": "npx", "args": ["mcp-remote", "https://mcp.querysail.com/gsc/mcp"] }
  }
}

Data and limits

License

The files in this repository are MIT licensed. The QuerySail service is subject to its terms.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.