GSC Wizard MCP

Most SEO and analytics MCP servers hand the raw rows back to the model: thousands of query/page records streamed into the context window for the LLM to crunch. Language models are not built for arithmetic over large tables. They are slow at it, they burn tokens doing it, and they make mistakes (dropped rows, miscounted sums, hallucinated totals) that are hard to catch.

GSC Wizard does the opposite. Every analysis (CTR curves, decay detection, cannibalization, opportunity scoring, path breakdowns, ranking changes, full SEO reports) is computed inserver-side Python and SQL, against the data warehouse, before anything reaches the model. The tool returns the finished result, not the raw input.

- Far fewer tokens.A single tool call returns a compact, finished answer instead of tens of thousands of rows the model has to read, hold in context, and pay for.
- Much faster.Aggregations run on the warehouse in milliseconds. The model spends its time reasoning about the result, not grinding through a spreadsheet one token at a time.
- Not prone to errors.The math is deterministic. Numbers come from real queries, so there is no risk of the model miscounting or inventing totals.
- Bigger datasets in scope.Because the heavy lifting never enters the context window, the server can analyze months of data and millions of rows that would never fit in a prompt.

The model still does what it is good at: interpreting the findings, spotting the story, and recommending what to do next. The crunching just happens where it belongs.

Two ways to authenticate, both tied to your GSC Wizard account:

- API key(header): sendAuthorization: Bearer gscw_live_.... Best for config-file clients (Claude Code, Cursor, VS Code, Windsurf).
- OAuth 2.1(sign-in): clients that support remote OAuth (ChatGPT, the Claude web/app Connectors UI, the native Claude Desktop connector) discover it automatically and walk you through a Google sign-in and consent screen. No key to copy or store.

In clients that render rich tool output (such as ChatGPT), summary tools likeget_site_summary,query_top_queries,query_top_pages,get_ranking_changes,list_sites, andgenerate_seo_reportdisplay an interactive, theme-aware card/table view. Other clients receive the same data as JSON.

The server speaks Streamable HTTP, so any client that supports remote MCP servers can connect. The config-file clients below (Claude Code, Cursor, VS Code, Windsurf) authenticate with an API-key header: replacegscw_live_...with your key. Clients that support remote OAuth (ChatGPT, the Claude web/app Connectors UI, the native Claude Desktop connector) instead just need the URL and will sign you in: see the OAuth note in each section.

claude mcp add --transport http gsc-wizard \ https://mcp.gscwizard.com/mcp \ --header "Authorization: Bearer gscw_live_..."

Easiest (OAuth, no Node):Settings → Connectors →Add custom connector, enterhttps://mcp.gscwizard.com/mcpas the URL, and leave the OAuth fields blank. Claude registers itself automatically, opens a Google sign-in and consent screen, and connects. Nothing to copy or store.

Add custom connector: paste the URL, leave the OAuth fields blank.

Tool calls are rate limited per account to protect your Search Console quota and keep the service responsive. Two windows apply at once, and a call must fit within both:

The limit is shared across every key and session on your account, so opening more sessions does not raise it. Only tool invocations (tools/call) count: protocol handshakes such asinitializeandtools/listare free, and a batched request that invokes several tools counts as one call per tool.

When you exceed a window the server returnsHTTP 429with aRetry-Afterheader giving the seconds until the window resets, and a JSON-RPC error body:{ "error": { "code": -32000, "message": "Rate limit exceeded (minute window). Retry after 42s." } }. Pause forRetry-Afterseconds and retry. Most clients surface this as a transient error you can simply re-run.

These limits are separate from Google's own quotas. URL Inspection tools (inspect_url,bulk_inspect_urls,check_tracked_url_now) also draw on the daily ~2,000-inspection-per-property quota you share with the GSC Wizard UI.

The server exposes 106 tools. You normally just ask your assistant in natural language ("show my top queries last month for example.com") and it picks the right tool and fills the arguments. The JSON under each tool below shows the argument shape, so you can see what each one accepts. Dates useYYYY-MM-DDand are optional on every tool that takes a date range: omitstartDate/endDateand the server uses the most recent settled window automatically (never passnullor the string"null").siteUrlis a value returned bylist_sites(a URL prefix likehttps://example.com/or a domain property likesc-domain:example.com).

Date ranges are optional.Every tool that takes a date range treatsstartDateandendDateas optional: omit them and the server analyzes the last 28 days Search Console has settled (its data lags ~2-3 days). Pass one end or both to narrow the window; the comparison tools (get_ranking_changes,find_decaying_content) default the baseline to the same-length period immediately before the current one. You never need to know today's date, and you should never sendnullor the string"null"for a date.

Where the numbers come from.The search-analytics tools (query_search_analytics,query_top_queries,query_top_pages,query_countries,query_devices,get_site_summary,get_query_performance,get_page_performance) and the analysis-report tools (get_ranking_changes,find_decaying_content,get_decay_overview,analyze_cannibalization,analyze_ctr_curve,find_page_poaching_opportunities,score_opportunities,breakdown_by_path,analyze_sampling_impact,get_sitemap_performance,get_cross_site_summary,get_tag_group_view) read from the GSC Wizard data warehouse when it has your property: that gives you longer history and no Search Console sampling. Otherwise they fall back to the live Search Console API automatically. Every response includes adataSourcefield set toclickhouseorapiso you always know which one answered. Warehouse responses also include asettledThroughdate and a freshness note: warehouse data settles ~2 days behind real-time, so for the most recent day or two the live API is the better source. Requests that need thesearchAppearancedimension, thegoogleNewstype, three or more distinct dimensions, or pagination always use the live API.

Metric units.Everyctrfield returned by any tool is apercentage from 0 to 100(a 2.34% click-through rate is2.34, not0.0234) — the same on the warehouse path, the live Search Console path, and the Bing tools. Differences between two CTRs (ctrPoints,ctrDelta, thedeltasmap onanalyze_ctr_curve) are in percentage points.positionis an impressions-weighted average where lower is better. GA4 rate metrics are the exception and keep the Data API's own units:bounceRateandengagementRateare 0-1 fractions.

Bing Webmaster Tools.Thelist_bing_sitesandget_bing_*tools read the Bing side of organic search (Bing, Yahoo, DuckDuckGo) live from the Bing Webmaster API. They use the Bing Webmaster API key stored on the property's connected Google account in GSC Wizard, so they need no separate connection here: if no key is set up, the tool returnsnotConfigured: truewith a hint instead of an error. Bing exposes roughly the last 6 months per endpoint, so omitting the date range returns everything Bing has (not a settled-window default like the Search Console tools).

List Search Console properties connected to the account.

No arguments. Start here to get the siteUrl values the other tools expect.

Profile, connected Google accounts, and subscription state.

Runs the whole analysis suite for a property in one call and returns a complete, self-contained HTML report (overview, top queries/pages, countries & devices, CTR curve, opportunities, ranking changes, decay, cannibalization, sections, coverage, sitemaps). Much faster than calling each tool separately.

{ "siteUrl": "sc-domain:example.com", "days": 28, "format": "html" }

days defaults to 28 (7-180). format: "html" (default, ready-to-open report) or "json" (raw data bundle). includeSitemap defaults to true.

Ad-hoc searchAnalytics.query against a property. The most flexible read tool.