QuerySail: Google Search Console MCP logo

QuerySail: Google Search Console MCP

Hosted, read-only MCP access to Google Search Console traffic, URL inspection, comparisons, and sitemap data.

Install QuerySail: Google Search Console MCP

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://mcp.querysail.com/gsc/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpointLive · 8h agoLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 8h ago · Nov 18, 2026, 19:45 UTC

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://mcp.querysail.com/gsc/mcp

Overview

QuerySail: Google Search Console MCP connects AI clients to Google Search Console through a hosted Streamable HTTP endpoint and OAuth 2.1. It provides read-only tools for traffic reporting, period comparisons, URL indexing checks, property discovery, and sitemap review. Reach for it when you want to investigate organic search performance in natural language without installing a local server or managing a Google API key. Google Search Console access must be connected through a QuerySail account.

Use cases

  • Analyze pages and queries driving Google search traffic
  • Compare organic performance across reporting periods
  • Inspect indexing and canonicalization for URLs
  • Review submitted sitemaps and processing issues

Key features

  • Read-only Google Search Console access
  • Performance metrics with multiple dimensions and filters
  • Period comparisons for queries, pages, countries, and devices
  • Batch inspection of up to 20 URLs
  • Sitemap status, counts, errors, and warnings

Tools5

What QuerySail: Google Search Console MCP lets your agent do. Expand a tool for its parameters.

Self-reported~196 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

10/10 checks healthy over the last 45d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit15d agoMost recent push to the default branch.
MaintenanceActively maintainedStatus declared by the project or listing owner.
Availability100%Our rolling endpoint + install checks that succeeded.
Tools exposed5Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How QuerySail: Google Search Console MCP works

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.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about QuerySail: Google Search Console MCP

QuerySail: Google Search Console MCP is an MCP server that connects AI clients to Google Search Console through a hosted Streamable HTTP endpoint. Its main tools list properties, retrieve and compare performance, inspect up to 20 URLs, and review submitted sitemaps using read-only access.

You do not install a local server; add the hosted endpoint to your MCP client and sign in. Use https://mcp.querysail.com/gsc/mcp, then connect a Google account through QuerySail. Clients limited to local commands can use the mcp-remote Node.js bridge.

Yes, it works with Cursor through an HTTP MCP entry in `~/.cursor/mcp.json`. Add the QuerySail endpoint as the server URL, then complete the QuerySail and Google sign-in flow when prompted.

No, QuerySail is read-only and cannot request indexing, submit sitemaps, or change Search Console settings. It can inspect URL indexing status and report submitted sitemap details, including read times, URL counts, errors, and warnings.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewQuerySail: Google Search Console MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/querysail-google-search-console-mcp?style=directory)](https://allmcps.com/mcp/querysail-google-search-console-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/querysail-google-search-console-mcp"><img src="https://allmcps.com/api/badge/querysail-google-search-console-mcp?style=directory" alt="QuerySail: Google Search Console MCP on AllMCPs" /></a>