Google Search Console MCP Server for SEOs
A Model Context Protocol (MCP) server that connects Google Search Console (GSC) to AI assistants, allowing you to analyze your SEO data through natural language conversations. Works with Claude Desktop, Cursor, Codex CLI, Gemini CLI, Antigravity, and any other MCP-compatible client.
Skip setup, get more. A more advanced hosted version — one-click sign-in, added GA4 tools. Works with Claude Desktop, Claude Code, Claude.ai, Codex, Cursor, and any MCP client. Only 100 seats.
→ Advanced GSC MCP (hosted)
What's New
[0.3.2] — April 2026
- OAuth browser flow fixed for uvx — removed the
isatty block that prevented the browser login window from opening when running as an MCP subprocess on macOS. OAuth now works out of the box with uvx, no manual terminal run needed.
get_capabilities tool added — call this to get a full list of available tools and current auth status in one shot. Useful when your AI assistant isn't sure what tools are available.- Better auth error messages — all tools now tell you exactly what to do when credentials are missing or expired.
What Can This Do?
Property Management
- See all your GSC properties in one place
- Get verification details and ownership information
- Add or remove properties from your account
Search Analytics & Reporting
- Discover which queries bring visitors to your site
- Track impressions, clicks, and click-through rates
- Analyze performance trends and compare time periods
- Visualize data with charts created by your AI assistant
URL Inspection & Indexing
- Check if specific pages have indexing problems
- See when Google last crawled your pages
- Inspect multiple URLs at once to identify patterns
Sitemap Management
- View all sitemaps and their status
- Submit new sitemaps
- Check for errors or warnings
Available Tools
| Tool | What It Does | What You Need to Provide |
|---|
get_capabilities | Lists all tools and shows auth status — call this first if unsure | Nothing |
list_properties | Shows all your GSC properties | Nothing |
get_site_details | Details about a specific site | Site URL |
get_search_analytics | Top queries and pages with clicks, impressions, CTR, position | Site URL, time period |
get_performance_overview | Summary of site performance | Site URL, time period |
compare_search_periods | Compare performance between two time periods | Site URL, two date ranges |
get_search_by_page_query | Search terms driving traffic to a specific page | Site URL, page URL |
get_advanced_search_analytics | Analytics with filters by country, device, query, page | Site URL |
inspect_url_enhanced | Detailed crawl/index status for a URL | Site URL, page URL |
batch_url_inspection | Inspect up to 10 URLs at once | Site URL, list of URLs |
check_indexing_issues | Check multiple URLs for indexing problems | Site URL, list of URLs |
get_sitemaps | Lists all sitemaps for a site | Site URL |
list_sitemaps_enhanced | Detailed sitemap info including errors and warnings | Site URL |
manage_sitemaps | Submit or delete sitemaps | Site URL, action |
reauthenticate | Re-run the OAuth browser login (switch accounts) | Nothing |
Ask your AI assistant to "call get_capabilities" for the full list of all 20 tools.
Getting Started
Step 1 — Set Up Google API Credentials
You need credentials before configuring any client. Pick one method:
Option A — OAuth (Recommended — uses your own Google account)
- Go to Google Cloud Console and create or select a project
- Enable the Search Console API
- Go to Credentials → Create Credentials → OAuth client ID
- Configure the OAuth consent screen, select Desktop app, click Create
- Download the JSON file — save it somewhere permanent (e.g.
~/Documents/client_secrets.json)
On first use, a browser window will open asking you to sign in to your Google account. After that, the token is saved and no browser interaction is needed again.
Option B — Service Account (For automation or team use)
