QuerySail for Google Search Console

Google Search Console MCP Server for ChatGPT, Claude and Codex

QuerySail is a hosted GSC MCP server. Ask about clicks, impressions, queries, pages and index status across every Search Console property you can see, in the AI app you already use.

Independent product, not made by Google. You sign in to QuerySail through our sign-in provider, WorkOS, and grant Search Console access on Google’s own consent screen.

Last updated

What you can ask

Plain questions. Your assistant picks the dates, dimensions and filters, and every answer says what it covers. For worked examples and data limits, read how to connect Search Console to ChatGPT and Claude. To weigh the other options, see the best Google Search Console MCP servers. To find pages close to the top of Google, follow how to find striking-distance keywords. To find pages that compete or slowly lose traffic, read how to find keyword cannibalization and how to find content decay. To turn the numbers into a report each month, follow how to create a monthly SEO report.

Capabilities

What it does

  • Property discovery. Lists the exact Domain and URL-prefix properties your connected Google accounts can read.
  • Performance retrieval. Clicks, impressions, CTR and average position, as totals or broken down by date, hour, query, page, country, device and search appearance, for web, image, video, news, Discover and Google News.
  • Filters and follow-ups. Narrow to specific queries, pages, countries or devices. Ask the next question without re-exporting anything.
  • Clear coverage. Responses state the dates used, whether more rows exist, and when Google may have returned only top rows.

What it does not do

  • It never writes to Google: no editing sites, submitting sitemaps or requesting indexing.
  • It cannot read properties your Google account cannot read.
  • It does not store a performance archive. Data is fetched when you ask, with a short-lived cache.
  • It does not promise rankings, complete query coverage or SEO outcomes. Your assistant interprets the numbers.

Requirements

  • A Google account with access to at least one Search Console property.
  • An AI app that supports remote MCP servers, such as ChatGPT, Claude, Codex, Cursor or VS Code. That app's plan is separate from QuerySail.
  • Search Console exposes roughly the last 16 months of history. QuerySail cannot return older data.

Five MCP tools

Small on purpose, so your assistant picks the right call. All are marked read-only for MCP clients.

list_properties

Lists the Search Console properties your connected Google accounts can read, with their exact IDs, such as sc-domain:example.com or https://example.com/.

get_performance

Search performance for one property: date range, search type (web, image, video, news, Discover, Google News), dimensions (date, hour, query, page, country, device, search appearance), filters, finalized, fresh or hourly data, and 20 to 100 rows per call with paging.

compare_performance

Two periods side by side: the previous period, the same weekdays a year earlier or your own dates. Totals with absolute and percent changes, the click change split into impressions and CTR, and the top gaining and losing queries, pages, countries or devices.

inspect_urls

URL Inspection for 1 to 20 pages of one property: whether each is on Google, the coverage state, robots.txt and noindex blocking, fetch result, last crawl, the canonical Google chose versus the declared one, and detected rich results.

list_sitemaps

The sitemaps submitted for a property, or inside a sitemap index: when Google last read each one, whether it is still pending, error and warning counts, and how many URLs it lists.

Set up in about five minutes

No Google Cloud project and nothing to install. See pricing and usage limits.

  1. Create an account

    Sign up with email. No card needed.

  2. Connect Google

    Approve read-only Search Console access.

  3. Add QuerySail

    Add it to ChatGPT, Claude, Codex or another MCP app and sign in.

  4. Ask away

    Start with your properties, then your first report.

Connect your AI app to the MCP server

You need a QuerySail account with Google connected. Start the free trial, then add this endpoint to your app and sign in with your QuerySail account when it asks:

https://mcp.querysail.com/gsc/mcp
  1. Open Settings → Security and login and turn on Developer mode. Availability depends on your plan and workspace settings.
  2. Go to chatgpt.com/plugins and select the plus button.
  3. Name it QuerySail, paste the endpoint above as the connection URL and create it.
  4. Sign in with your QuerySail account when asked, then add QuerySail from the tools menu in a new chat.

Optional, for coding agents such as Claude Code, Codex, Cursor and OpenCode: the Google Search Console skill tells the agent which QuerySail tool to call for each question and how to report the numbers. Installing it needs Node.js:

npx skills add https://querysail.com --skill querysail-search-console

Security and permissions

What QuerySail asks Google for, where it keeps your credentials, and how to take access back. The privacy policy has the full detail.

The Google permission

QuerySail asks Google for one Search Console permission, the read-only scope https://www.googleapis.com/auth/webmasters.readonly. It also asks for your Google account's email address and ID (openid and email) so it can tell your connected accounts apart. Each Google product is a separate connection with its own consent, so connecting one never grants another.

What QuerySail can and cannot do

  • It can read the Search Console data that your Google account can read, when your assistant asks for it.
  • It cannot add or verify properties, submit or remove sitemaps, request indexing or change any setting. None of its tools write to Google.
  • It cannot read properties your Google account has no access to.
  • It keeps data in a 15-minute cache to avoid repeat calls. There is no long-term archive.

Where your credentials are stored

QuerySail encrypts your Google tokens with AES-256-GCM before it stores them, and the encryption key is not kept in the database. Your Google tokens never leave QuerySail's servers. Your AI app gets its own QuerySail token and never sees your Google credentials.

How to disconnect and revoke access

  • In Account → Connections, choose Disconnect. QuerySail deletes the stored tokens at once, asks Google to revoke them and removes cached data for that connection.
  • You can also remove QuerySail in your Google account at myaccount.google.com/permissions. QuerySail notices within about 15 minutes and stops serving that data.
  • To cut off an AI app but keep Google connected, revoke plugin access in Account → Settings.

Questions, answered

Something else? See support.

What is a Google Search Console MCP server?

MCP (Model Context Protocol) is the standard way AI assistants call external tools. A Google Search Console MCP server exposes your Search Console data as tools, so ChatGPT, Claude or Codex can fetch clicks, impressions, CTR and average position when you ask a question, instead of you exporting CSV files. It is often shortened to GSC MCP server.

Is there an official Google Search Console MCP server?

Not at the moment. We found no official Search Console MCP server from Google. Google's list of its official MCP servers had none for Search Console when we checked on October 19, 2026. The Search Console MCP servers available today, QuerySail included, are third-party products built on the public Search Console API.

Is QuerySail an SEO MCP server?

It covers the Search Console side of SEO. Your assistant gets clicks, impressions, CTR, average position, index status and sitemap reports from Google. It does not crawl your site, track rankings outside Search Console, or report backlinks or keyword search volumes.

Which apps work with QuerySail?

Any app that supports remote MCP servers over streamable HTTP with OAuth sign-in. Setup guides cover ChatGPT, Claude Desktop and claude.ai, Claude Code, Codex, Grok, Cursor, VS Code and OpenCode. Apps that only run local commands can connect through the mcp-remote bridge.

Do I need a Google Cloud project, service account or API key?

No. You approve read-only Search Console access with Google once, on the QuerySail website. Your AI app then signs in with your QuerySail account. There is nothing to install and no key to paste.

Can it change my site, submit sitemaps or request indexing?

No. QuerySail only asks Google for read-only Search Console access. It can report whether a page is indexed, but it cannot edit properties, submit sitemaps, request indexing or change any setting.

What data can my assistant get?

Clicks, impressions, CTR and average position, as totals or grouped by date, query, page, country, device and search appearance, with filters, for web, image, video, news, Discover and Google News results. Hourly data covers the last 10 days. Comparisons show what changed between two periods and which queries or pages gained or lost. URL inspection reports, for up to 20 pages at a time, whether each is on Google, why not, its last crawl and the canonical Google chose. Sitemaps show when Google last read them and any errors. Search Console keeps roughly the last 16 months, and Google returns only top rows for query and page breakdowns.

Does QuerySail store my Search Console data?

Data is fetched from Google when your assistant asks and kept in a short-lived cache of 15 minutes to avoid repeat calls. There is no long-term performance archive.

How much does it cost?

$8 per month with unlimited connected properties. The 7-day free trial needs no card and starts with your first successful performance query, not at sign-up.

Why use a hosted server instead of running one myself?

Open-source Search Console MCP servers are free to run, but you set up a Google Cloud project, an OAuth client or service account, and a machine to run the server. QuerySail is hosted: sign in, connect Google and add one URL to your app. If you would rather run your own, a self-hosted server is a fine choice.

Is QuerySail made by Google?

No. QuerySail is an independent product that uses the public Google Search Console API. It is not affiliated with or endorsed by Google, OpenAI or Anthropic.