QuerySail: Google Search Console
com.querysailv1.0.0Updated Oct 4, 2026
Hosted, read-only Google Search Console MCP: performance, comparisons, URL inspection, sitemaps.
Overview
Hosted, read-only Google Search Console access so an assistant can query search performance, compare periods, inspect URLs and list sitemaps.
- What it does
- QuerySail is a hosted, read-only MCP server for Google Search Console. Tools list the properties a connected Google account can read, return clicks, impressions, CTR and average position by date, query, page, country, device or search appearance, compare two periods to show what gained or lost, inspect up to 20 URLs for indexing status and canonical choice, and list submitted sitemaps with errors and warnings. All tools are read-only; it cannot submit sitemaps, request indexing or change Search Console settings.
- When to use it
- Useful when you want to ask about your own search traffic in plain language: top pages by clicks, period-over-period changes, whether a page is indexed and which canonical Google chose, or which queries rank on page two. It suits SEO and content reporting rather than site changes.
- Requirements
- A remote Streamable HTTP endpoint with OAuth 2.1 and dynamic client registration; nothing to install and no API key to paste. You need a QuerySail account with a Google Search Console account connected, and a browser sign-in on first use. Clients that only run local commands need the mcp-remote bridge and Node.js. A 7-day free trial is offered, then $8/month.
Installation
In SourceWeft
- Open QuerySail: Google Search Console in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"gsc": {
"type": "http",
"url": "https://mcp.querysail.com/gsc/mcp"
}
}
}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.
- Endpoint:
https://mcp.querysail.com/gsc/mcp(Streamable HTTP, OAuth 2.1 with dynamic client registration) - Website: https://querysail.com/google-search-console
- Pricing: 7-day free trial, no card required, then $8/month. See https://querysail.com/pricing.
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.
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
Then run /mcp, choose querysail-gsc and sign in. Or install it as a plugin, which also adds a Search Console analysis skill:
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.
Codex
Cursor
Add to ~/.cursor/mcp.json:
VS Code
Run MCP: Add Server, choose HTTP and paste the endpoint, or add to mcp.json:
Clients that only run local commands
Use the mcp-remote bridge (needs Node.js):
Data and limits
- Google access uses the
webmasters.readonlyscope. Refresh tokens are encrypted at rest. You can disconnect Google or delete your account at any time. - Search Console keeps about 16 months of data; hourly data covers the last 10 days; Google returns only top rows for query and page breakdowns.
- Privacy: https://querysail.com/privacy · Terms: https://querysail.com/terms · Support: https://querysail.com/support
License
The files in this repository are MIT licensed. The QuerySail service is subject to its terms.
Source: README.md at commit 62c841c
Tools
0Version history
1- v1.0.0LatestOct 4, 2026

