Back to Browse

Querysail Gsc MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Hosted, read-only Google Search Console MCP: performance, comparisons, URL inspection, sitemaps.

About

Hosted, read-only Google Search Console MCP: performance, comparisons, URL inspection, sitemaps.

Remote endpoints: streamable-http: https://mcp.querysail.com/gsc/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "com-querysail-gsc": {
      "url": "https://mcp.querysail.com/gsc/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

QuerySail: Google Search Console MCP server

QuerySail is a hosted MCP server for Google Search Console. Connect it to ChatGPT, Claude, Codex, Cursor or VS Code, sign in, connect your Google account once, and ask about your search traffic in plain language. There is nothing to install and no API key to paste.

This repository holds the public listing files (MCP Registry server.json, a Claude Code plugin, client configs). The service itself is hosted at querysail.com; its source is not published here.

Tools

All tools are read-only. QuerySail cannot submit sitemaps, request indexing or change any Search Console setting.

ToolWhat it does
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.

Example prompts

  • Which of my pages got the most clicks from Google in the last 28 days?
  • What changed in my search traffic compared with the previous 28 days?
  • Is my homepage indexed on Google, and which canonical did Google choose?
  • Which queries rank on page two for my blog, sorted by impressions?

Setup

You need a QuerySail account with Google Search Console connected: sign up at https://querysail.com. Each client below opens a browser window to sign in the first time.

Claude Code

claude mcp add --transport http --scope user querysail-gsc https://mcp.querysail.com/gsc/mcp

Then run /mcp, choose querysail-gsc and sign in. Or install it as a plugin, which also adds a Search Console analysis skill:

/plugin marketplace add querysail/querysail-gsc
/plugin install querysail-gsc@querysail

Claude Desktop and claude.ai

Open Customize → Connectors, select + Add → Add custom connector, name it QuerySail and paste https://mcp.querysail.com/gsc/mcp as the server URL.

ChatGPT

Turn on Developer mode under Settings → Security and login, go to chatgpt.com/plugins, select the plus button and paste the endpoint as the connection URL.

Grok

Go to grok.com/connectors, select New Connector → Custom, paste https://mcp.querysail.com/gsc/mcp as the MCP server URL and sign in. On Grok Business and Enterprise plans a team admin first adds it at console.x.ai under Grok Business → Connectors.

Codex

codex mcp add querysail-gsc --url https://mcp.querysail.com/gsc/mcp
codex mcp login querysail-gsc

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "querysail-gsc": { "url": "https://mcp.querysail.com/gsc/mcp" }
  }
}

VS Code

Run MCP: Add Server, choose HTTP and paste the endpoint, or add to mcp.json:

{
  "servers": {
    "querysail-gsc": { "type": "http", "url": "https://mcp.querysail.com/gsc/mcp" }
  }
}

Cline

Open MCP Servers → Remote Servers, name it querysail-gsc, paste the endpoint, choose Streamable HTTP and click Add Server. Or add to cline_mcp_settings.json:

{
  "mcpServers": {
    "querysail-gsc": { "type": "streamableHttp", "url": "https://mcp.querysail.com/gsc/mcp" }
  }
}

Sign in with your QuerySail account when Cline asks.

Clients that only run local commands

Use the mcp-remote bridge (needs Node.js):

{
  "mcpServers": {
    "querysail-gsc": { "command": "npx", "args": ["mcp-remote", "https://mcp.querysail.com/gsc/mcp"] }
  }
}

Agent skill

The querysail-search-console skill tells coding agents such as Claude Code, Codex, Cursor and OpenCode which QuerySail tool to call for each question and how to report the numbers. Install it with the skills CLI (needs Node.js):

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

Data and limits

License

The files in this repository are MIT licensed. The QuerySail service is subject to its terms.

Reviews

No reviews yet

Be the first to review this server!