Best Google Search Console MCP Server in 2026

Quick comparison: 7 Google Search Console MCP servers

A Search Console MCP server lets Claude, ChatGPT or Cursor query clicks, impressions, CTR and position from a chat. The servers differ in who hosts them, whether they can change anything in Search Console and what they cost. Facts come from each vendor's docs, README or pricing page, opened November 14, 2026.

Hosted servers take a Google sign-in. Self-hosted servers need a Google Cloud project or service account and a machine that runs them. Access describes what each server documents, not a test run.

What is the best Google Search Console MCP server?

For most marketing teams, Ryze AI is our first pick: a hosted server with 7 Search Console tools on the same connector URL as Google Analytics, Google Ads and Meta Ads. Disclosure: Ryze AI publishes this page and runs that server, so each reason comes with its limit.

Setup is a URL and a Google sign-in. No Google Cloud project, OAuth client or service account. The steps are on the Search Console MCP setup page. Limit: the tools need an active Ryze AI plan or free trial.

The query tool is complete. One tool runs Search Analytics by query, page, country, device, search appearance or date, for web, image, video, news or Discover results, up to 25,000 rows per request. Limit: results lag Google's data by 2 to 3 days.

Sitemaps and index checks are covered. Tools list sitemaps, summarize them, submit, resubmit or delete one, and inspect one URL. Limit: there is no tool to request indexing, and URL Inspection checks one URL at a time.

Free, and comfortable with Python and a Cloud project? AminForou/mcp-gsc, with 20 tools. Reporting across many sources on a small budget? Windsor.ai. Only need a hosted reader in several AI tools? Adzviser.

Side-by-side: access, setup and tool counts

Read means the server only pulls data. Write means it can submit or delete sitemaps, add or remove properties, or ask Google to crawl a URL. Tool counts are the ones each vendor or README publishes. None of these servers was connected for this page.

Only Ryze AI, mcp-gsc and search-console-mcp document sitemap writes against Search Console itself. mcp-gsc is the only one here that documents a request-indexing tool, and it keeps it, like its other writes, behind a flag. Windsor.ai, Adzviser and mcp-server-gsc only read.

The best Search Console MCP servers, ranked 1 to 4

1. Ryze AI

• What it does: hosted MCP server for Claude, ChatGPT and Cursor, with Search Console on the same connector as Google Analytics, Google Ads and Meta Ads.
• Search Console access: 7 tools: listSites, runRawSearchAnalytics, listSitemaps, getIndexationSummary, inspectUrl (read), submitSitemap (write) and deleteSitemap (delete). Deleting a sitemap removes it from Search Console only, not the file on your site.
• Setup: a connector URL and a Google sign-in, then confirm the Site. The Ryze AI help center lists every step. Several Google logins can be connected to one workspace.
• Price: needs an active plan or trial. SEO Starter is $129 a month with a 3-day free trial; Paid Ads is $89 a month with a 7-day free trial; annual billing saves 30% the first year (pricing).
• Fits: marketers who want a hosted server. Limit: no request-indexing tool, and no way to add or verify a property.

2. AminForou/mcp-gsc

• What it does: the most-starred open-source Search Console server we found: 2,201 GitHub stars, MIT license, last push November 6, 2026, version 0.4.2.
• Search Console access: 20 tools across property management, search analytics, URL inspection and indexing, and sitemaps, including compare_search_periods, batch_url_inspection and request_indexing. add_site, delete_site, manage_sitemaps and request_indexing are off until you set GSC_ALLOW_DESTRUCTIVE=true; the default scope is webmasters.readonly.
• Setup: uvx (recommended) or a clone with Python 3.11 or later; OAuth with your Google account, or a service account. Documented for Claude Desktop, Cursor, Codex CLI, Gemini CLI and Antigravity.
• Price: free.
• Fits: SEOs who want the widest tool list and batch inspection. Limit: you run it on your own machine and set up Google credentials.

3. Windsor.ai

• What it does: hosted MCP on Windsor's data platform. Its Search Console MCP page states that Google publishes no Search Console MCP server as of November 4, 2026.
• Search Console access: read-only search analytics, with extra fields such as branded queries and path levels. No tool count published.
• Setup: sign in to Windsor.ai, pick the property, then add the Windsor connector. Works in Claude, ChatGPT, Gemini and Copilot, per that page.
• Price: Free plan; Basic $23 a month ($19 billed annually); MCP is included on every plan (pricing).
• Fits: cross-channel reporting on a small budget. Limit: no sitemap or inspection tools listed.

4. Adzviser

• What it does: hosted remote MCP server; its Search Console page lists the URL https://mcp.adzviser.com/http.
• Search Console access: read-only: clicks, impressions, CTR and position, with 25 breakdowns such as queries, landing pages, devices, countries and search appearances. No tool count published.
• Setup: create a workspace, authorize Search Console, then connect through Claude's connector directory or the ChatGPT plugin. Also lists Gemini CLI, Perplexity and n8n.
• Price: Starter $48.99 a month for 3 data sources, Growth $148.99 for 7, with a 14-day trial (pricing).
• Fits: teams that only report and want the lightest install. Limit: price grows with the number of sources.

Ranked 5 to 7: open-source options for developers

5. saurabhsharma2u/search-console-mcp

• What it does: TypeScript server, MIT, 322 GitHub stars, last push October 21, 2026. Besides Search Console it covers Bing Webmaster Tools, GA4 and AdSense.
• Search Console access: the README lists 7 core tools plus 3 AdSense tools, including analytics_query, analytics_compare, inspection_inspect and sitemaps_list. Tools are read-only by default; sitemap submit and delete and site management need OAuth re-authorization with the write scope.
• Setup: npx search-console-mcp setup, or a .mcpb bundle for Claude Desktop. Mentions Claude Desktop, Cursor and Antigravity.
• Price: free.
• Fits: developers who also use Bing Webmaster Tools. Limit: a wide scope, so check the tool list before connecting.

6. iannuttall/seo (SEO skill)

• What it does: open-source SEO tool for agents, Apache-2.0, 626 GitHub stars, last push November 14, 2026. Every command is also an MCP tool, hosted at https://seoskill.dev/mcp or run locally through the npm CLI.
• Search Console access: commands for a Search Console report, page checks, before and after comparisons, indexing reasons and raw rows, plus keyword research and a crawl (crawl is CLI only). The submit command uses IndexNow or Index My Site, not Search Console.
• Setup: sign in with the Google account that can see Search Console. Lists Claude Code, Codex, Cursor, Claude Desktop and VS Code.
• Price: its README says it is free and open source.
• Fits: teams that want SEO workflows around Search Console data. Limit: it is broader than Search Console, and no sitemap tools are listed.

7. ahonn/mcp-server-gsc

• What it does: small npm server, 286 GitHub stars, last push September 4, 2026, MIT per its README.
• Search Console access: one read tool, search_analytics, with up to 25,000 rows, regex filters and dimensions such as query, page, country, device and search appearance.
• Setup: npx with a service account JSON file, and the service account email added to the property in Search Console. The README shows a Claude Desktop configuration.
• Price: free.
• Fits: a single, auditable query tool. Limit: no sitemap or URL inspection tools.

Google's own options: the API, quotas and no official server

Google's Search Console API pages that we opened mention no MCP server, and Windsor.ai states Google publishes none for Search Console as of November 4, 2026. Every server above wraps the same Search Console API, so its quotas apply to all of them.

Per Google's quota page, Search Analytics also has load-based quotas, and a load violation means waiting 15 minutes. The 2,000 URL Inspection calls per site per day cap any batch inspection run by an MCP server.

Data limits sit on top of quotas. Search Console data arrives 2 to 3 days late and goes back up to 16 months, one request returns at most 25,000 rows, and Google withholds some queries for privacy, so query-level rows add up to less than total clicks.

How to choose a Search Console MCP server

Three questions settle it: can you run Python or Node and set up Google credentials, does anything need to write to Search Console, and do you need more than Search Console data?

Marketer, no terminal

Ryze AI if you want sitemap tools as well as reports. Windsor.ai or Adzviser if you only report. Setup for Ryze AI is in how to connect Claude to Google Search Console and how to connect ChatGPT to Google Search Console.

SEO who works in Claude Code, Cursor or a terminal

AminForou/mcp-gsc for the widest tool list, iannuttall/seo for SEO workflows around the data, search-console-mcp if you also use Bing Webmaster Tools.

Auditable and minimal

ahonn/mcp-server-gsc: one query tool and a service account you control. See also the best MCP for Google Analytics if traffic data is the next question.

Prompts to test a Search Console MCP server

Run the same prompts on every server you shortlist. Replace the brackets with your own property and dates; the numbers that come back will be your own.

Returns properties and permission levels (listSites on Ryze AI, list_properties on mcp-gsc).

Returns one row per page with both periods. Search Console data is 2 to 3 days late, so end the range before today.

Returns a table of queries close to page one. It tests filters and the row limit.

Returns sitemap status and one URL's index state. Inspection works one URL at a time.

Safety checklist before you connect one

Search Console holds a site's query data and controls its sitemaps, so connect with the least access that does the job.

• Start read-only. mcp-gsc and search-console-mcp default to read scopes; Windsor.ai, Adzviser and mcp-server-gsc only read.
• Check the write tools. Ryze AI's submitSitemap and deleteSitemap change Search Console. In Claude, set write and delete tools to Needs approval under Customize, Connectors, Ryze AI, Tool permissions. In the Ryze AI chat, the Tool approvals setting can be switched to Approve write and delete.
• Pick the right property type. A URL-prefix property excludes traffic outside that prefix; a Domain property covers all subdomains and protocols.
• Read the code of self-hosted servers. They run on your machine with your Google credentials. Prefer a service account with Restricted access where it fits.
• Know what leaves your account. Hosted servers receive your Search Console query data; check each vendor's privacy terms.

How we compared them

Sources

The verdict

Google has no Search Console MCP server, so you pick a hosted connector or a server you run. Hosted ones take a sign-in; mcp-gsc has the longest tool list and keeps its writes behind a flag; the smaller open-source servers suit developers who want to read the code.

For a hosted setup with report, sitemap and inspection tools, Ryze AI is our pick. It has no request-indexing tool, so that job stays in Search Console itself or in mcp-gsc.