Skip to main content
Glama
@mgcrea/mcp-google-search-console

@mgcrea/mcp-google-search-console

by mgcrea

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GSC_DEBUGNoSet to 1 to log requests to stderr.
GSC_CONFIGNoConfig file path.
GSC_CLIENT_IDYesDesktop-app OAuth client id (….apps.googleusercontent.com).
GSC_TIMEOUT_MSNoPer-request timeout in milliseconds.30000
GSC_TOKEN_FILENoWhere the login is stored.~/.config/google-search-console/tokens.json
GSC_MAX_RETRIESNoRetry budget for 429 / 5xx.3
GSC_ALLOW_WRITESNoSet to 1 to register the sitemap write tools and ask for the webmasters scope.
GSC_CLIENT_SECRETYesThe OAuth client secret. Google requires it even with PKCE.
GSC_REFRESH_TOKENNoUse this refresh token (memory only) instead of the token file.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
gsc_auth_statusA

Whether the server is configured and signed in, which Google account the token belongs to (the account decides which properties exist at all), how many properties it can read, the granted scopes, whether the write tools are registered, and the quota model. When unconfigured, returns the exact setup steps. Call this first when a tool you expected is missing, a property is not found, or a setting seems to have no effect (config_issues lists values that were clamped or ignored).

gsc_auth_loginA

Sign in with Google: opens the consent screen in the browser and waits for it to finish, then stores a refresh token (mode 600) and reports the signed-in account. Pick the Google account that has access to the Search Console properties you want — the account, not any argument, decides which properties are readable. The app is unverified, so Google shows a warning first: Advanced → Go to (app). If no browser can be opened, or the wait runs out, returns the authorize URL instead and keeps listening for 5 minutes; call gsc_auth_status afterwards. Logging in again replaces the stored login.

gsc_auth_logoutA

Revoke the stored refresh token at Google and delete it locally. Recoverable by calling gsc_auth_login again.

gsc_list_sitesA

The Search Console properties the signed-in account can see, each with its exact site_url (pass it as site to the other tools), kind and permission_level. A domain property (sc-domain:example.com) covers every protocol and subdomain; a URL-prefix property (https://www.example.com/) covers exactly that scheme, host and path, so http, https and www are separate properties with separate data. siteUnverifiedUser means listed but unreadable. Always fetches fresh; costs one request.

gsc_query_search_analyticsA

Search performance for a property: clicks, impressions, CTR and average position, grouped by the dimensions you pick (date, hour, query, page, country, device, searchAppearance, brandedClassification). Rows come back with named fields ({query, page, clicks, impressions, ctr, position}), sorted by clicks (by date when grouped by date), plus returned_totals: the sum of the RETURNED rows only, not the property total (rows past row_limit are not counted, and query-grouped rows omit anonymized queries); and next_start_row when there may be more. Dates are Pacific-time calendar days; data lags 2-3 days and is kept 16 months; the default range is the 28 days ending 3 days ago. QUOTA: grouping or filtering by page or query, and long ranges, are the expensive part of the 10-minute and daily load quotas — ask for the dimensions you need, not all of them. The hour dimension needs data_state hourly_all (set for you) and covers only about the last 10 days, which is then the default range. To find what changed between two periods use gsc_compare_periods instead of two queries.

gsc_compare_periodsA

What changed between two periods, by one dimension: the top gainers and losers present in both, keys that are new or lost, and each period's returned_totals. This is the tool for "what dropped?" or "which pages grew?" — prefer it over two gsc_query_search_analytics calls and diffing them by eye. Defaults: current = the 28 days ending 3 days ago (Pacific), previous = the same-length window just before it. Runs two queries of depth rows each (1,000 by default); by query or page that is the expensive kind of load quota, so do not loop it. returned_totals sum the fetched rows only, not the property: rows past depth are not counted, and by query anonymized queries are missing. When a period fills depth, truncated is set and some new/lost keys may only have crossed the cut.

gsc_inspect_urlA

Google's index status for one URL, as Search Console's URL Inspection reports it: verdict (PASS / NEUTRAL / FAIL), coverage state (e.g. "Crawled - currently not indexed"), robots.txt and noindex state, last crawl and fetch result, the canonical Google chose versus the one the page declares (canonical_mismatch is true when they differ), sitemaps and referring URLs it knows, and a rich-results summary. This is Google's indexed view, not a live test. QUOTA: 2,000 inspections per day and 600 per minute per property; for several URLs use gsc_inspect_urls.

gsc_inspect_urlsA

Inspect up to 20 URLs of one property, 3 at a time, with the same per-URL fields as gsc_inspect_url plus a summary (verdicts, canonical mismatches). Prefer this over calling gsc_inspect_url repeatedly — but each URL still costs one of the property's 2,000 daily inspections; quota_used estimates how many were spent. A URL that fails comes back with its own error and remedy instead of failing the call; on a quota, permission or sign-in error the remaining URLs are skipped rather than burned.

gsc_list_sitemapsA

The sitemaps submitted for a property (or, with sitemap_index, the child sitemaps listed in that index): path, type, last submitted and last downloaded times, whether processing is pending, warning and error counts, and submitted URL counts per content type. Google no longer reports an indexed count here — use gsc_inspect_url for a page's index status.

gsc_get_sitemapA

One submitted sitemap's processing status: last submitted and downloaded, pending, whether it is an index, warning and error counts, and submitted URL counts per content type. A 404 means it was never submitted for this property (gsc_list_sitemaps lists those that were).

gsc_requestA

Escape hatch: call a Search Console API endpoint that has no dedicated tool. The path must be under /webmasters/v3/ (sites, sitemaps, searchAnalytics) or /v1/urlInspection/, with the property URL-encoded as one segment, e.g. GET /webmasters/v3/sites/sc-domain%3Aexample.com. Returns the raw response, unshaped — prefer the dedicated tools, which resolve the property and name the fields. Writes are DISABLED: only GET is permitted, so the POST-only search analytics and URL inspection endpoints are reachable only through their dedicated tools. Set GSC_ALLOW_WRITES=1 to allow other methods.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 11 tools

Disambiguation5/5

Each tool targets a clearly distinct resource and action: auth status/login/logout, site listing, analytics querying, period comparison, single/batch URL inspection, and sitemap listing/retrieval. The only near-overlaps (gsc_inspect_url vs gsc_inspect_urls, gsc_query_search_analytics vs gsc_compare_periods) are explicitly disambiguated by their descriptions, and gsc_request clearly labels itself as a fallback to be avoided when dedicated tools exist.

Naming Consistency5/5

All tools use a consistent gsc_ prefix followed by snake_case verb_noun names, e.g. gsc_list_sites, gsc_list_sitemaps, gsc_get_sitemap, gsc_inspect_url. The batch variant gsc_inspect_urls and the auth_* group follow the same predictable convention throughout.

Tool Count5/5

11 tools is well within the typical 3-15 range and each tool maps to a distinct Search Console operation. The auth trio, analytics pair, inspection pair, and sitemaps pair are all justified and no tool feels redundant.

Completeness4/5

The read-only surface covers authentication, property discovery, search analytics, period comparison, URL inspection, and sitemaps, and gsc_request fills any remaining endpoint gaps. Write operations such as submitting/deleting sitemaps or managing properties are absent, though the server explicitly disables writes by default, making this a minor gap for the intended scope.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues