Skip to main content
Glama

QuerySail: Google Search Console

Server Details

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

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
querysail/querysail-gsc
GitHub Stars
0
Server Listing
QuerySail: Google Search Console
ChatGPT
–
Claude
–

TDQS

A4.4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a clearly distinct task: single-period performance, period comparison, URL inspection, property listing, or sitemap listing. The compare/get performance pair is the closest overlap, but the names and descriptions make the boundary explicit.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: compare_performance, get_performance, inspect_urls, list_properties, list_sitemaps. The verbs accurately reflect the operations.

Tool Count5/5

Five tools is well-scoped for a read-only Google Search Console server, and each tool covers a distinct core workflow. There is no obvious filler or redundant tool.

Completeness4/5

The set covers core read-only workflows: performance retrieval, period comparison, URL inspection, properties, and sitemaps. Minor gaps remain around sitemap submission, indexing requests, and live URL tests, but these appear to be intentional read-only limitations.

Publisher details

Operator
QuerySail (operated by Gidian Bateman, South Africa) · Publisher source
Operator website
https://querysail.com
Vendor relationship
Independent
Trust center
Not available
Restrictions
Requires a QuerySail account with Google Search Console connected. 7-day free trial without a card, then a paid plan ($8/month). · Publisher source

Available Tools

5 tools
compare_performanceCompare Search Console performanceA
Read-onlyIdempotent
Inspect

Use this when the user asks what changed between two periods, why traffic went up or down, or which pages, queries, countries or devices gained or lost. Compares clicks, impressions, CTR and average position for one property between a current period and the previous period (default), the same weekdays a year earlier, or explicit dates. Returns both totals with absolute and percent changes, the click change split into an impressions part and a CTR part, and, with a dimension, the top gainers and losers ranked by change in clicks or impressions. Dates are Pacific Time; with no dates the current period is the last 28 finalized days. Filters and search type apply to both periods. Changes are observed differences and do not identify causes. Read-only; does not change anything in Search Console.

Inputs: property_id (required), movers, filters, rank_by, +9 more. Returns: notes, units, losers, totals, +5 more

get_performanceGet Search Console performanceA
Read-onlyIdempotent
Inspect

Use this to retrieve Google Search Console search performance (clicks, impressions, CTR, average position) for one property. With no dimensions it returns property totals. Add dimensions to break results down by date, hour, query, page, country, device or searchAppearance, and filters to narrow to specific queries, pages, countries, devices or search appearances (for example mobile traffic to pages containing '/blog/'). search_type selects web (default), image, video, news, discover or googleNews results; discover and googleNews have no queries. For what happened in the last hours or days, group by hour (data_state 'hourly', last 10 days only, preliminary). Dates are Pacific Time. If no dates are given it uses the last 28 finalized days (or yesterday and today for hourly) and reports the exact dates it used. Covers one period at a time. Rows are bounded (default 20, max 100); page through with the returned cursor. Google returns only top rows for query/page breakdowns, so results are not guaranteed to be complete, and a missing row does not mean zero. Figures are observed values and do not identify causes. Read-only; cannot request indexing or change anything in Search Console.

Inputs: property_id (required), cursor, filters, end_date, +7 more. Returns: rows, units, totals, request, +3 more

inspect_urlsInspect URLs in Search ConsoleA
Read-onlyIdempotent
Inspect

Use this when the user asks whether specific pages are indexed by Google, why a page is not on Google, or which canonical Google chose. Runs Search Console URL Inspection for 1 to 20 full URLs of one property and returns, per URL: whether it is on Google, the coverage state (for example 'Crawled - currently not indexed'), robots.txt and noindex blocking, the page fetch result, last crawl time and crawler, the canonical Google chose versus the one the page declares, sitemaps and referring pages that list it, and detected rich results with their issues. Results describe the version Google last indexed, not a live test. Each URL must belong to the property, given by its exact property_id. Read-only; cannot request indexing, a recrawl or change anything in Search Console.

Inputs: urls (required), property_id (required), connection_id. Returns: notes, results, summary, property, +1 more

list_propertiesList Search Console propertiesA
Read-onlyIdempotent
Inspect

Use this when the user asks which Google Search Console sites or properties they can access, or to find the exact property_id for a site. Returns exact property IDs (Domain properties look like 'sc-domain:example.com', URL-prefix properties like 'https://example.com/'), the permission level, and connection status. The same site is listed once even if several connected Google accounts can see it. A site name can match more than one property, for example a Domain property and a URL-prefix property. Read-only. Does not change anything in Google Search Console.

Inputs: cursor, connection_id. Returns: notes, coverage, properties, connections

list_sitemapsList Search Console sitemapsA
Read-onlyIdempotent
Inspect

Use this when the user asks which sitemaps a site has in Search Console, whether Google read them, or whether they have errors or warnings. Lists the sitemaps submitted for one property with type, whether it is an index, pending status, last submitted and last read times, error and warning counts, and how many URLs each lists by content type. Pass sitemap_index to list the sitemaps inside a sitemap index. URL counts are listed URLs, not indexed URLs. Read-only; cannot submit, resubmit or delete sitemaps.

Inputs: property_id (required), connection_id, sitemap_index. Returns: notes, summary, property, sitemaps, +2 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to query Google Search Console search performance, inspect indexing, analyze sitemaps, and run SEO analyses such as cannibalisation detection, query clustering, and wins/losses, all with read-only access.
      20
      397 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server for Google Search Console data, enabling search analytics, URL inspection, indexing diagnostics, and sitemap management through MCP clients.
      19 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables local, read-only access to Google Search Console data, allowing users to query site performance, identify ranking opportunities, inspect URL indexing, and review sitemap status through MCP clients.
      8
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.