MCP Search Console vs QuerySail: Google Search Console MCP
A side-by-side look at the MCP 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.
Verdict: choose MCP 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?
Choose MCP Search Console when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GSC_ACCOUNTS_CONFIG. - You want tools like
list_accounts, set_default_account, reauthenticate.
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 | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 59/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 | GSC_ACCOUNTS_CONFIG | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 17 | 5 |
| Full listing | View MCP Search Console | View QuerySail: Google Search Console MCP |
Tools & capabilities
MCP Search Console tools 17
list_accountsList all configured GSC accounts and which is the current default.set_default_accountSet the default account used when no account is specified in other tools.reauthenticateForce re-authentication for an account. Clears the cached token and re-runs the OAuth flow (or reloads service account credentials). Useful when a token has been revoked or you need to switch Google accounts.list_propertiesList all Google Search Console properties for the specified account.get_site_detailsGet verification and permission details for a specific GSC property.get_search_analyticsFetch search analytics data (clicks, impressions, CTR, position).get_performance_overviewGet a high-level performance summary: total clicks, impressions, CTR, average position. No dimension breakdown — use get_search_analytics for that.compare_periodsCompare search performance between two date ranges. Returns rows for both periods side-by-side with delta calculations.get_advanced_search_analyticsAdvanced search analytics with dimension filters. filters format: [{"dimension": "country", "operator": "equals", "expression": "usa"}] operators: equals, notEquals, contains, notContains, includingRegex, excludingRegexget_search_by_pageGet search queries driving traffic to a specific page URL.inspect_urlInspect a URL's indexing status, last crawl date, mobile usability, and rich result eligibility.batch_inspect_urlsInspect multiple URLs at once. Returns one result per URL. Maximum 10 URLs per call (GSC API limit).- +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.
MCP Search Console
{
"mcpServers": {
"mcp-search-console": {
"command": "uvx",
"args": [
"mcp-search-console-multi"
],
"env": {
"GSC_ACCOUNTS_CONFIG": "YOUR_GSC_ACCOUNTS_CONFIG_HERE"
}
}
}
}
QuerySail: Google Search Console MCP
{
"mcpServers": {
"querysail-google-search-console-mcp": {
"url": "https://mcp.querysail.com/gsc/mcp"
}
}
}
Frequently asked questions
MCP 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 MCP 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.
MCP 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 mcp-search-console 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, MCP Search Console has a quality signal of 59/100 (Good) with 3 views, 0 installs and 0 GitHub stars. QuerySail: Google Search Console MCP has 77/100 (Great) with 3 views, 0 installs and 0 GitHub stars.