# QuerySail: Google Search Console MCP [Verified owner] [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/GidianB/querysail-gsc  
**GitHub Stars:** 0  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/querysail-google-search-console-mcp

## Description
Hosted, read-only Google Search Console MCP server for ChatGPT, Claude, Codex, Cursor, and VS Code. Query search traffic, inspect URLs, compare performance, and review sitemaps using natural language.

## Tools
Capabilities this server exposes over MCP:

- **list_properties** — Lists the Search Console properties your connected Google accounts can read, with exact IDs and permission level.
- **get_performance** — Clicks, 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_performance** — Compares 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_urls** — Inspects up to 20 URLs: whether each is on Google, why not, last crawl, robots.txt and noindex blocking, and the canonical Google chose.
- **list_sitemaps** — Lists submitted sitemaps with when Google last read them, URL counts, errors and warnings.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "querysail-google-search-console-mcp": {
    "url": "https://mcp.querysail.com/gsc/mcp"
  }
}
```

## Documentation

## What QuerySail: Google Search Console MCP does

QuerySail provides AI clients with read-only access to Google Search Console data. It can identify the properties available to connected Google accounts, retrieve search performance metrics, compare reporting periods, inspect individual URLs, and list submitted sitemaps.

Performance reports include clicks, impressions, click-through rate, and average position. Results can be summarized or broken down by date, hour, query, page, country, device, or search appearance. The service supports web, image, video, news, Discover, and Google News result types.

URL inspection covers up to 20 URLs in one request. Results can show whether a URL is indexed, why it is not indexed, the latest crawl information, robots.txt or noindex blocking, and the canonical URL selected by Google.

## How it works

The hosted MCP endpoint is `https://mcp.querysail.com/gsc/mcp` and uses Streamable HTTP with OAuth 2.1 dynamic client registration. After connecting a supported client, sign in to QuerySail and authorize access to Google Search Console. Google access uses the `webmasters.readonly` scope, so the tools can retrieve reporting and inspection data without changing Search Console configuration.

No local package or API key is required for the hosted connection. The first connection in each client opens a browser-based sign-in flow. Clients that only support local commands can connect through the `mcp-remote` bridge, which requires Node.js.

## Setup and configuration

Create a QuerySail account at `querysail.com`, connect a Google account with access to the relevant Search Console properties, and add the endpoint as a remote MCP server. Claude Code and Codex provide command-line setup commands; Cursor, VS Code, and Cline accept HTTP server configuration. Claude Desktop can use a custom connector. A Claude Code plugin is also available and adds a Search Console analysis skill.

The same endpoint can be added through the client-specific connector or MCP settings interface. For local-command-only clients, configure `mcp-remote` with the hosted URL rather than installing QuerySail itself.

The service offers a seven-day free trial with no card required, followed by an $8/month plan. Account disconnection and deletion are available through QuerySail.

## Tools and capabilities

- `list_properties` returns readable Search Console property IDs and permission levels.
- `get_performance` retrieves search metrics with date, hour, query, page, country, device, and search-appearance dimensions and filters.
- `compare_performance` compares a previous period, matching weekdays from the prior year, or custom date ranges, highlighting gains and losses by query, page, country, or device.
- `inspect_urls` checks indexing status and related crawl, blocking, and canonical details for up to 20 URLs.
- `list_sitemaps` reports submitted sitemaps, last-read times, URL counts, errors, and warnings.

## Limitations and notes

All tools are read-only. QuerySail cannot submit sitemaps, request indexing, or modify Search Console settings. Search Console generally retains about 16 months of data, while hourly reporting covers only the most recent 10 days. Google returns only the top rows for query and page breakdowns, so detailed reports may not include every result.

The repository's files are MIT licensed, while use of the hosted QuerySail service is governed by its terms.

_Full upstream README: https://allmcps.com/mcp/querysail-google-search-console-mcp/readme_

