Google Search Console vs QuerySail: Google Search Console MCP
A side-by-side look at the Google Search Console and QuerySail: Google Search Console MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
G
Google Search ConsoleMarketing · Local subprocess (stdio)Google Search Console: 37 tools, every API endpoint, hourly data, history beyond 16 months.53GoodAuth: not declaredVerdict: choose Google Search Console for marketing work as a local process; choose QuerySail: Google Search Console MCP for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
GChoose Google Search Console when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You want tools like
performance_overview, hourly_performance, data_freshness.
Choose QuerySail: Google Search Console MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
list_properties, get_performance, compare_performance.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | G Google Search Console | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 53/100 · Good | 77/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 2 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 17 | 5 |
| Full listing | View Google Search Console | View QuerySail: Google Search Console MCP |
Tools & capabilities
Google Search Console tools 17
performance_overview*"How did example.com do in the last 6 months, month by month?"*hourly_performance*"Show the last 24 hours"* · *"Show last week as Tehran days"*data_freshness*"Is yesterday's data complete yet?"*build_query_regex*"Give me a regex for خرید خودرو that matches every spelling"*sync_history*"Sync the last 16 months of example.com"*history_status*"What history do I have saved?"*history_sql*"Run this SQL on my history: …"*inspect_url*"Is /new-article/ indexed? What canonical did Google pick?"*inspect_urls*"Inspect these 30 URLs"*indexing_summary*"Which of these pages have indexing issues?"*inspection_quota*"How many inspections do I have left today?"*list_sitemaps*"List my sitemaps and their errors"*- +5 more on the listing page
QuerySail: Google Search Console MCP tools 5
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.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Google Search Console
{
"mcpServers": {
"google-search-console-8": {
"command": "uvx",
"args": [
"gsc-mcp-full"
]
}
}
}
QuerySail: Google Search Console MCP
{
"mcpServers": {
"querysail-google-search-console-mcp": {
"url": "https://mcp.querysail.com/gsc/mcp"
}
}
}
Frequently asked questions
Google Search Console is categorized under Marketing and uses a local stdio subprocess. QuerySail: Google Search Console MCP belongs to Marketing and uses a remote HTTP/SSE transport. Pick Google Search Console for marketing work and QuerySail: Google Search Console MCP for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Google Search Console has no declared pricing — check the project's own site. QuerySail: Google Search Console MCP is listed as a paid service. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add google-search-console-8 and querysail-google-search-console-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Search Console has a quality signal of 53/100 (Good) with 1 views, 0 installs and 2 GitHub stars. QuerySail: Google Search Console MCP has 77/100 (Great) with 3 views, 0 installs and 0 GitHub stars.