Connect Google Search Console to Cursor, Claude, or Gemini. Ask questions in plain English and get real SEO data back.
gsc-seo-mcp is an MCP project maintained in the samalyxx/gsc-seo-mcp repository. The maintainer describes its purpose as “Connect Google Search Console to Cursor, Claude, or Gemini. Ask questions in plain English and get real SEO data back”. Read the project documentation for the complete scope.
The documented npm package is gsc-seo-mcp. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.
The example declares GSC_AUTH_MODE, GSC_KEY_FILE, GSC_SITE_URL. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.
Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| server_health | Shows config status, auth mode, and tool count |
| list_properties | Lists all Search Console properties you have access to |
| get_site | Gets permission details for one property |
| add_site | Adds a site to your account |
| delete_site | Removes a site from your account |
| search_analytics | Full query with dimensions, filters, search type, and data state |
| advanced_filter_query | Pulls up to 50,000 rows for deeper audits |
| top_queries | Top queries, optionally filtered by page |
| top_pages | Top pages, optionally filtered by query |
| performance_overview | Site snapshot with period comparison, daily trend, devices |
| compare_periods | Current vs previous period by page, query, country, or device |
| dimension_breakdown | Performance by one dimension |
| page_query_matrix | Maps pages to the queries driving them |
| quick_wins | Which keywords are close enough to improve fast? |
| ctr_opportunities | Which snippets underperform for their ranking position? |
| content_decay | Which pages are declining across multiple periods? |
| traffic_drop_diagnosis | Was the drop rankings, CTR, demand, coverage, or mixed? |
| cannibalization_check | Which queries are split across competing pages? |
| brand_nonbrand_split | How much traffic is brand vs non-brand? |
| search_intent_breakdown | How do queries split across informational, commercial, transactional, navigational, local? |
| device_country_opportunities | Which device/country/page segments have weak CTR or ranking? |
| long_tail_questions | Which question queries deserve content expansion? |
| page_refresh_priorities | Which pages should be updated first? |
| internal_link_opportunities | Which strong pages can support weaker pages? |
| query_page_fit | What does one page rank for, and does the content match? |
| title_meta_brief | Which queries should inform title/meta refreshes? |
| anomaly_alerts | Which pages had abnormal losses recently? |
| inspect_url | Checks one URL for index status, canonical, crawl, coverage |
| batch_inspect_urls | Inspects multiple URLs |
| index_coverage_summary | Summarizes inspection results across a URL list |
| list_sitemaps | Lists submitted sitemaps with errors and indexed counts |
| get_sitemap | Details for one sitemap |
| submit_sitemap | Submits or refreshes a sitemap |
| delete_sitemap | Deletes a submitted sitemap |
| indexing_publish_url | Sends an Indexing API notification for an eligible URL |
| indexing_batch_publish | Sends multiple Indexing API notifications |
| indexing_get_metadata | Checks latest Indexing API notification status for a URL |
| multi_site_dashboard | Compares multiple properties in one view |
| generate_markdown_report | Saves a Markdown SEO report to disk |
| verify_claim | Re-queries GSC to check a number before you report it to a client |
{
"mcpServers": {
"gsc-seo": {
"command": "npx",
"args": [
"-y",
"gsc-seo-mcp"
],
"env": {
"GSC_AUTH_MODE": "service_account",
"GSC_KEY_FILE": "YOUR_GSC_KEY_FILE",
"GSC_SITE_URL": "sc-domain:example.com"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| GSC_AUTH_MODE | Declared in the maintainer’s client configuration. | Optional |
| GSC_KEY_FILE | Declared in the maintainer’s client configuration. | Check documentation |
| GSC_SITE_URL | Declared in the maintainer’s client configuration. | Optional |
Retrieve public web pages as readable Markdown with the reference Fetch MCP server, including pagination for longer responses.
Use Firecrawl MCP to retrieve website content and extract information for research through Firecrawl’s API-backed web tools.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Automates browsers and APIs, enabling Large Language Models (LLMs) to interact with web pages for tasks like screenshot capture and JavaScript
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.