Google Search Console MCP vs QuerySail: Google Search Console MCP
A side-by-side look at the Google Search Console MCP 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.
Google Search Console MCPMarketing · Local subprocess (stdio)Model Context Protocol (MCP) server for Google Search Console (GSC) inspection, search performance, and sitemaps via NPX. Spawns the Python package through uvx with full stdio passthrough.55GoodAuth: otherVerdict: choose Google Search Console MCP 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?
Choose Google Search Console MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
GSC_SITE_URL, GOOGLE_APPLICATION_CREDENTIALS.
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 | Google Search Console MCP | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 55/100 · Good | 77/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | other | OAuth 2.0 |
| Pricing | Not declared | Paid service |
| Required env vars | GSC_SITE_URLGOOGLE_APPLICATION_CREDENTIALS | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 40 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Google Search Console MCP | View QuerySail: Google Search Console MCP |
Tools & capabilities
Google Search Console MCP tools
No tool names declared yet. Check the project README from 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 MCP
{
"mcpServers": {
"surendranb-google-search-console-mcp": {
"command": "uvx",
"args": [
"google-search-console-mcp"
],
"env": {
"GSC_SITE_URL": "YOUR_GSC_SITE_URL_HERE",
"GOOGLE_APPLICATION_CREDENTIALS": "YOUR_GOOGLE_APPLICATION_CREDENTIALS_HERE"
}
}
}
}
QuerySail: Google Search Console MCP
{
"mcpServers": {
"querysail-google-search-console-mcp": {
"url": "https://mcp.querysail.com/gsc/mcp"
}
}
}
Frequently asked questions
Google Search Console MCP 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 MCP 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 MCP has no declared pricing — check the project's own site. Auth: other. 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 surendranb-google-search-console-mcp 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 MCP has a quality signal of 55/100 (Good) with 1 views, 0 installs and 40 GitHub stars. QuerySail: Google Search Console MCP has 77/100 (Great) with 3 views, 0 installs and 0 GitHub stars.