QuerySail
Sign inStart free trial
QuerySail for Google Search Console

Google Search Console MCP server for ChatGPT, Claude and Codex

A hosted, read-only MCP server for your Search Console data. Ask about clicks, impressions, queries and pages across every property you can see, in the AI app you already use.

Start 7-day free trialSetup guides →

What you can ask

Plain questions. Your assistant picks the dates, dimensions and filters, and every answer says what it covers.

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, query, page, country and device.
  • 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.

Two read-only MCP tools

Small on purpose, so your assistant picks the right call. Both 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, dimensions (date, query, page, country, device), filters, finalized or fresh data, and 20 to 100 rows per call with paging.

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.

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.

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, 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 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 and device, with filters. 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.