Google Search Console MCP Server
Provides tools for interacting with Google Search Console, enabling AI agents to manage properties, analyze search analytics, inspect URLs, manage sitemaps, and perform SEO diagnostics.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Google Search Console MCP Server show me my top queries from last month"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
This repository is a local fork of AminForou/mcp-gsc. It stays close to upstream and currently adds:
Local docs and notes
CI and Dependabot for the mirror
Python runtime compatibility of 3.10+ (Python 3.9 is not supported by the current MCP SDK)
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
isattyblock that prevented the browser login window from opening when running as an MCP subprocess on macOS. OAuth now works out of the box withuvx, no manual terminal run needed.get_capabilitiestool 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.
Related MCP server: Google Search Console MCP Server
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 |
| Lists all tools and shows auth status — call this first if unsure | Nothing |
| Shows all your GSC properties | Nothing |
| Details about a specific site | Site URL |
| Top queries and pages with clicks, impressions, CTR, position | Site URL, time period |
| Summary of site performance | Site URL, time period |
| Compare performance between two time periods | Site URL, two date ranges |
| Search terms driving traffic to a specific page | Site URL, page URL |
| Analytics with filters by country, device, query, page | Site URL |
| Read-only Search Analytics snapshot export with JSONL/CSV files and manifest | Site URL, date range |
| Read-only prioritized traffic-loss action queue for operator workflows | Site URL, current and previous date ranges |
| Read-only prioritized content-opportunity action queue for operator workflows | Site URL, date range |
| Read-only sampled cannibalization decision queue for manual review | Site URL, date range |
| Read-only weekly SEO ops report aggregator with performance snapshot, prioritized queues, and manual checklist guidance | Site URL, optional date ranges |
| Read-only checklist of Search Console UI-only/manual review tasks and evidence to collect | Optional site URL, focus |
| Detailed crawl/index status for a URL | Site URL, page URL |
| Inspect up to 10 URLs at once | Site URL, list of URLs |
| Read-only prioritized action queue from URL Inspection data | Site URL, list of URLs |
| Check multiple URLs for indexing problems | Site URL, list of URLs |
| Read-only JobPosting JSON-LD audit with Indexing API eligibility dry-run; never calls the Indexing API | Site URL, job URLs |
| Read-only JobPosting lifecycle action queue with dry-run Indexing API recommendations only | Site URL, job URLs |
| Auth-free sampled adjacent technical diagnostics with manual PageSpeed/Rich Results links; no PSI, CrUX, or GSC API calls | Site URL, page URLs |
| Lists all sitemaps for a site | Site URL |
| Detailed sitemap info including errors and warnings | Site URL |
| Safely fetches and parses a sitemap or sitemap index for read-only URL diagnostics | Site URL, sitemap URL |
| Submit or delete sitemaps | Site URL, action |
| Re-run the OAuth browser login (switch accounts) | Nothing |
Ask your AI assistant to "call get_capabilities" for the full registered tool catalog.
Search Analytics Data Behavior
Google Search Analytics API responses are best treated as official API data with clear coverage limits:
Search Analytics sorts rows by clicks by default, except when results are grouped by date.
Requested ranking such as
sort_byis applied by this server after rows are returned, so client-side sorting only reorders the retrieved rows.Returned rows are the top rows for the request, not a guaranteed complete export of everything visible in the Search Console UI.
gsc_export_search_analytics_snapshotwrites a read-only API snapshot underGSC_EXPORT_DIRwhen set, otherwise under the GSC config directory'sexports/folder. Relative export directories are normalized to absolute paths. Each snapshot includesmanifest.jsonwith request fingerprint, row/page counts, totals, artifact checksums, and limitations.gsc_build_traffic_drop_queuecompares current and previous Search Analytics periods using two officialquerycalls and returns stable JSON action items with heuristic likely causes, confidence, limitations, and manual-verification flags.gsc_build_content_action_queueuses one official Search Analyticsquerycall and returns stable JSON heuristic opportunities for high-impression/low-CTR rows, striking-distance rankings, and page/query refresh candidates. Items require manual verification before content changes.gsc_build_cannibalization_decision_queueuses one official Search Analyticsquerycall withquery,pagedimensions and returns a stable sampled diagnostic queue for likely competing pages. It is not proof of cannibalization and requires SERP, intent, canonical, internal-link, and business review before URL changes.gsc_run_weekly_seo_ops_reportcomposes a stable read-only JSON weekly operator report from two dimensionless Search Analytics performance calls, the traffic-drop/content/cannibalization queues, and the static manual checklist. It supports partial failures by returning section-level errors and warnings instead of collapsing the whole report when at least one section succeeds.gsc_get_manual_operator_checklistis a static read-only checklist for UI-only/manual Search Console surfaces such as Manual actions, Security issues, Removals, Crawl stats, Core Web Vitals, HTTPS, Links, Enhancements, and Settings access. It does not call Google APIs, require credentials, click UI buttons, submit requests, remove URLs, request indexing, validate fixes, or change permissions.gsc_audit_jobposting_schemais a read-only HTML fetch and JSON-LD parser for supplied property-scoped job URLs. It blocks off-property/private targets, does not follow redirects, does not call Search Console, does not call the Google Indexing API, does not publishURL_UPDATEDorURL_DELETED, does not request indexing, and does not write files. Itsindexing_api_dry_runrecommendation is advisory only.gsc_build_jobposting_lifecycle_queuecomposes the JobPosting audit with optional URL Inspection diagnostics when credentials are available. It is read-only, dry-run only, quota-conscious, supports partial per-URL failures, and never calls the Indexing API or mutates Search Console.gsc_run_adjacent_technical_diagnosticsis auth-free and read-only. It safely samples supplied property-scoped pages for basic adjacent technical signals such as robots meta noindex, canonical hints, JSON-LD type counts, robots.txt summary counts, and manual PageSpeed/Rich Results UI links. It is not Search Console parity and does not call PageSpeed Insights, CrUX, Rich Results, Search Console, or Indexing APIs.Snapshot exports paginate with Search Analytics
startRowandrowLimit, but the API remains bounded: exported rows may not equal a full UI export.Search Analytics requests support
data_state="all",data_state="final", anddata_state="hourly_all"(per call where available, or globally throughGSC_DATA_STATE). Usehourly_allonly withdimensions="hour"or a dimension list that includeshour, for exampledimensions="hour,query"; requests withouthourare rejected before invalid API calls or snapshot file writes.Official API surfaces: Search Analytics metrics, URL Inspection results for requested URLs, sitemap metadata, and property information.
Adjacent approximations: content opportunities, page prioritization, period comparisons, and other workflows that rank or filter the returned rows.
Sampled diagnostics: cannibalization checks and broad audits that look for patterns within available top rows.
Manual-only surfaces: full UI exports, UI-only reports, and any workflow that requires complete row coverage beyond the API response.
JobPosting Schema Audit & Indexing API Dry-Run
gsc_audit_jobposting_schema returns stable JSON with top-level schema_version: "jobposting_schema_audit.v1" plus summary counts, per-URL issues, summarized JobPosting objects, dry-run Indexing API recommendations, limitations, and source provenance.
gsc_build_jobposting_lifecycle_queue returns stable JSON with top-level schema_version: "jobposting_lifecycle_queue.v1" plus prioritized action items for active valid jobs, schema-blocked jobs, missing or stale validThrough, expired/noindex jobs, optional URL Inspection observations, and dry-run-only URL_UPDATED/URL_DELETED recommendations. Actual Indexing API publish/delete remains outside this MCP flow and should only happen later behind explicit approval, eligibility, and quota gates.
Encoded source constraints:
Google JobPosting docs: required properties checked include
datePosted,description,hiringOrganization,jobLocation, andtitle; the remote-work exception requiresjobLocationTypeplusapplicantLocationRequirements; JobPosting should be on the most specific single job page, not listing pages; expired jobs should be removed or use pastvalidThrough; content must match the page and users must be able to apply.Google Indexing API usage docs: Indexing API is only for pages with
JobPostingorBroadcastEventembedded inVideoObject;URL_UPDATEDandURL_DELETEDare publish actions;getMetadatais read-only status metadata and not indexing proof.Google Indexing API quota docs: default publish quota is 200 URLs/day/project, metadata quota is 180/min/project, and all endpoints share 380/min/project; production use requires approval and quota planning.
Limitations:
The audit parses only static JSON-LD in
<script type="application/ld+json">; it does not evaluate Microdata, RDFa, rendered JavaScript, or external feeds.The tool returns summaries only and does not echo full job descriptions.
The dry-run recommendation is not proof of rich result eligibility, indexing, crawl timing, quota approval, or API access.
Manual review is still required for apply-flow availability, page/content matching, whether the page is truly a single-job detail page, and business decisions about expired/noindex pages.
Getting Started
Quick Start Example
For a domain property, the most common format will be:
sc-domain:example.comRecommended first workflow in your MCP client:
Call
get_capabilitiesRun
get_search_analyticsforsc-domain:example.comRun
compare_search_periodsfor the last 28 days vs. previous 28 daysUse
batch_url_inspectionorcheck_indexing_issuesfor priority URLsReview
get_sitemapsormanage_sitemaps
For job pages, ask: "Run gsc_build_jobposting_lifecycle_queue for https://example.com/ on these vacancy URLs and prioritize lifecycle actions, including dry-run URL_UPDATED or URL_DELETED recommendations." The tool will not call the Indexing API; if you later want fast recrawl requests for eligible vacancy pages, use the Google Indexing API separately for valid JobPosting URLs only after approval/quota review.
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
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)
Go to Google Cloud Console and create or select a project
Go to Credentials → Create Credentials → Service Account
Go to the Keys tab → Add Key → Create new key → JSON → Download
Save the file somewhere permanent (e.g.
~/Documents/service_account.json)Add the service account email to your GSC property: Search Console → Settings → Users and permissions → Add user → Full access
🎥 Watch the step-by-step setup tutorial for this section
Updated 2026 — covers the full installation process using the new uvx method, from setting up your Google credentials to your first successful query.
Step 2 — Installation
Option A — uvx (Recommended)
No cloning, no Python installation, no virtual environments. uvx downloads and runs the server automatically and keeps it up to date.
Install uv — open Terminal and run all three commands in order:
# 1. Download and install
curl -LsSf https://astral.sh/uv/install.sh | sh
# 2. Activate in the current Terminal session
source $HOME/.local/bin/env
# 3. Make it permanent for all future sessions
echo 'source $HOME/.local/bin/env' >> ~/.zshrcVerify:
uv --versionWhy all three commands? The installer puts
uvin~/.local/bin, but your already-open Terminal session doesn't know about that folder yet. Step 2 activates it immediately. Step 3 ensures every future Terminal window has it automatically.
Now configure your AI client:
Claude Desktop
Config file: ~/Library/Application Support/Claude/claude_desktop_config.json
OAuth:
{
"mcpServers": {
"gscServer": {
"command": "/FULL/PATH/TO/uvx",
"args": ["mcp-search-console"],
"env": {
"GSC_OAUTH_CLIENT_SECRETS_FILE": "/full/path/to/client_secrets.json"
}
}
}
}Service Account:
{
"mcpServers": {
"gscServer": {
"command": "/FULL/PATH/TO/uvx",
"args": ["mcp-search-console"],
"env": {
"GSC_CREDENTIALS_PATH": "/full/path/to/service_account.json",
"GSC_SKIP_OAUTH": "true"
}
}
}
}Cursor
Config file: ~/.cursor/mcp.json
OAuth:
{
"mcpServers": {
"gscServer": {
"command": "/FULL/PATH/TO/uvx",
"args": ["mcp-search-console"],
"env": {
"GSC_OAUTH_CLIENT_SECRETS_FILE": "/full/path/to/client_secrets.json"
}
}
}
}Codex CLI
Config file: ~/.codex/config.toml
OAuth:
[mcp_servers.gscServer]
command = "/FULL/PATH/TO/uvx"
args = ["mcp-search-console"]
enabled = true
env = { GSC_OAUTH_CLIENT_SECRETS_FILE = "/full/path/to/client_secrets.json" }Service Account:
[mcp_servers.gscServer]
command = "/FULL/PATH/TO/uvx"
args = ["mcp-search-console"]
enabled = true
env = { GSC_CREDENTIALS_PATH = "/full/path/to/service_account.json", GSC_SKIP_OAUTH = "true" }Finding your uvx path: On macOS/Linux run
which uvxin Terminal after installing uv (typically/Users/YOUR_NAME/.local/bin/uvx). On Windows, runGet-Command uvx | Select-Object -ExpandProperty Sourcein PowerShell (orwhere uvxin cmd) — it's usuallyC:\Users\YOUR_NAME\.local\bin\uvx.exe. Replace/FULL/PATH/TO/uvxin the configs above with that path.Why the full path? GUI apps like Claude Desktop and Cursor launch without reading your shell config (
~/.zshrc), so they don't know about~/.local/bin. Using the full path guarantees it works regardless of how the app is launched. If you see aspawn uvx ENOENTerror, this is the fix.
After saving the config, fully quit the app (Cmd+Q) and reopen it.
For OAuth: on first use, a browser window will open automatically for login. After that, the token is cached and you won't be asked again.
Option B — Clone (Advanced)
Prefer a video walkthrough for this method? The tutorial below covers the clone install path step by step — virtual environment setup, dependencies, and config:
Use this if you want to modify the code or run a specific local version. This method uses the video tutorial above for the credential setup steps.
Requires Python 3.10+. Python 3.9 is not supported by the current MCP Python SDK, so this server will not start there. Check your version with
python --version. If it's below 3.10, install Python 3.10 or newer and recreate your virtual environment. Theuvxmethod (Option A) avoids this entirely by managing the Python version for you, so it's still the recommended path for most users.
Clone the repo:
git clone <your-fork-url>
cd google-search-console-mcpIf you want to compare changes with upstream or contribute a fix back, keep the original project as an upstream remote:
git remote add upstream https://github.com/AminForou/mcp-gsc.gitOr download the ZIP from the green Code button at the top of this page and unzip it.
Set up the environment:
uv venv .venv
uv pip install -r requirements.txtConfigure your AI client (Claude Desktop example):
OAuth:
{
"mcpServers": {
"gscServer": {
"command": "/full/path/to/google-search-console-mcp/.venv/bin/python",
"args": ["/full/path/to/google-search-console-mcp/gsc_server.py"],
"env": {
"GSC_OAUTH_CLIENT_SECRETS_FILE": "/full/path/to/client_secrets.json"
}
}
}
}Service Account:
{
"mcpServers": {
"gscServer": {
"command": "/full/path/to/google-search-console-mcp/.venv/bin/python",
"args": ["/full/path/to/google-search-console-mcp/gsc_server.py"],
"env": {
"GSC_CREDENTIALS_PATH": "/full/path/to/service_account.json",
"GSC_SKIP_OAUTH": "true"
}
}
}
}Mac path examples:
Python:
/Users/yourname/Documents/google-search-console-mcp/.venv/bin/pythonScript:
/Users/yourname/Documents/google-search-console-mcp/gsc_server.py
Step 3 — Test
Ask your AI assistant: "List my GSC properties"
If you see your properties — it's working. If not, ask: "Call get_capabilities" to see auth status and diagnose the issue.
Environment Variables Reference
Variable | Required | Default | Description |
| OAuth only | — | Absolute path to your OAuth client secrets JSON. Always required when using |
| Service account only | — | Absolute path to your service account JSON key. Always required when using |
| No |
| Set to |
| No |
|
|
| No |
| Directory for read-only Search Analytics snapshot exports. Relative values are expanded to absolute paths. Tool args cannot override this path. |
| No |
| Set to |
| No |
| Required to bind SSE/HTTP transport to a non-loopback host such as |
Cursor Marketplace
One-click install available — search for mcp-search-console in the Cursor Marketplace.
After installing, configure your credentials (see Step 1 above) then use the bundled skills directly in Cursor Agent chat:
Skill | How to invoke | What it does |
| "Run the SEO weekly report for example.com" | Weekly ops report with performance snapshot, prioritized queues, and manual checklist guidance |
| "Check for keyword cannibalization on example.com" | Builds a sampled manual-review decision queue for likely competing pages |
| "Audit indexing for my top pages" | Batch-inspects top 20 pages and returns a prioritized fix list |
| "Find content opportunities for example.com" | Surfaces low-CTR/high-impression, striking-distance, and query/page refresh candidates for manual verification |
Sample Prompts
Tool | Sample Prompt |
| "List all my GSC properties and tell me which ones have the most pages indexed." |
| "Show me the top 20 search queries for mywebsite.com in the last 30 days, highlight any with CTR below 2%, and suggest title improvements." |
| "Create a visual performance overview of mywebsite.com for the last 28 days, identify any unusual drops or spikes, and explain possible causes." |
| "Check these pages for indexing issues: mywebsite.com/product, mywebsite.com/services, mywebsite.com/about" |
| "Do a comprehensive inspection of mywebsite.com/landing-page and give me actionable recommendations." |
| "Compare my site's performance between January and February. What queries improved the most?" |
| "Analyze queries with high impressions but positions below 10, filtered to mobile traffic in the US only." |
| "Export a Search Analytics snapshot for June as both JSONL and CSV, then summarize the manifest totals and truncation warning." |
| "Run the weekly SEO ops report for example.com for the last 28 days, include prioritized manual follow-up actions, and call out any section-level errors." |
| "Build a content action queue for the last 28 days and prioritize high-impression low-CTR, striking-distance (default positions 4-20), and query/page refresh opportunities for manual verification." |
| "Build a cannibalization decision queue for the last 28 days, show likely competing pages by query, and explain which cases need manual SERP and intent review first." |
| "Give me the weekly manual Search Console operator checklist for example.com, including UI paths and evidence I should collect without taking actions in the UI." |
Troubleshooting
spawn uvx ENOENT or command not found: uvx
Your AI client can't find uvx. Use the full path instead of just uvx:
# Find your full path (macOS/Linux):
which uvx
# Typically: /Users/YOUR_NAME/.local/bin/uvx# Find your full path (Windows PowerShell):
Get-Command uvx | Select-Object -ExpandProperty Source
# Typically: C:\Users\YOUR_NAME\.local\bin\uvx.exeReplace "command": "uvx" with the full path (e.g. "command": "/Users/YOUR_NAME/.local/bin/uvx") in your config.
uv --version gives "command not found" right after installing
The installer updates ~/.local/bin but your current Terminal session doesn't see it yet. Run:
source $HOME/.local/bin/envThen add it permanently:
echo 'source $HOME/.local/bin/env' >> ~/.zshrcAuthentication failed / credentials file not found
Make sure you are using the absolute path to your credentials file — not a relative path, not ~/. Example:
/Users/yourname/Documents/client_secrets.json ✅
~/Documents/client_secrets.json ✅
client_secrets.json ❌MCP only works in Claude Desktop app, not the website
The MCP server runs locally on your machine. It only works in the Claude Desktop app (downloaded from claude.ai/download), not in the claude.ai browser interface.
AI Client Configuration Issues
Make sure all file paths in your config are correct absolute paths
Fully quit (
Cmd+Q) and reopen the app after any config change — just closing the window is not enoughAsk your AI assistant to "call get_capabilities" — it will report the exact auth status and error
Safety: Destructive Operations
By default, add_site, delete_site, submit_sitemap, and delete_sitemap are disabled because they mutate external Google Search Console state. To enable these external mutations:
"GSC_ALLOW_DESTRUCTIVE": "true"Remote Deployment & Docker (Advanced)
The standard setup runs the server locally. This section is only for users who want to run it on a remote server or in a container.
Remote SSE/HTTP mode has no built-in authentication. Treat it as a trusted-network-only mode and place it behind your own network controls, reverse proxy, or tunnel.
HTTP Transport
MCP_TRANSPORT=sse GSC_ALLOW_REMOTE_SSE=true MCP_HOST=0.0.0.0 MCP_PORT=3001 python gsc_server.pyVariable | Default | Description |
|
| Set to |
|
| Host to bind |
|
| Port to bind |
|
| Explicit safety switch required for non-loopback SSE/HTTP binding |
Docker
docker build -t mcp-gsc .
docker run \
-e MCP_TRANSPORT=sse \
-e GSC_ALLOW_REMOTE_SSE=true \
-e MCP_HOST=0.0.0.0 \
-e MCP_PORT=3001 \
-e GSC_CREDENTIALS_PATH=/app/credentials.json \
-v /path/to/credentials.json:/app/credentials.json \
-p 3001:3001 \
mcp-gscRelated Tools
Advanced GSC Visualizer — A Chrome extension (14,000+ users) with interactive charts, one-click export of up to 25,000 rows, keyword cannibalization detection, and an AI assistant — all directly inside Google Search Console. Built by the same author. Install from the Chrome Web Store →
Contributing
Found a bug or have an idea for improvement? Open an issue or submit a pull request on GitHub.
License
MIT License. See the LICENSE file for details.
Changelog
[0.3.2] — April 2026
OAuth browser flow fixed for uvx — removed
isattyblock that prevented the OAuth browser window from opening when running as an MCP subprocess on macOS. OAuth +uvxnow works out of the box.get_capabilitiestool — returns all available tools grouped by category plus live auth status in one call.Better auth error messages — all tools now explicitly tell you to call
reauthenticatewhen credentials are missing or expired.Improved
list_propertiesdescription — better semantic tool discovery in clients that use lazy tool loading.
[0.3.1] — April 2026
Fixed
list_propertiesmasking real auth errors; fail-fast on missing credentials.
[0.3.0] — April 2026
Cursor Marketplace plugin with 4 bundled SEO skills
Stable token storage in platform user config dir (survives
uvxupgrades)Structured JSON output for all data tools
39 unit tests
[0.2.2] — April 2026
Safety mode for destructive tools (disabled by default)
HTTP/SSE transport for remote deployments
Dockerfile
[0.2.1] — March 2026
reauthenticatetool for switching Google accountsFixed sitemap TypeError crash
Fixed domain property 404 errors
[0.2.0] — March 2026
dataState: "all"by default (matches GSC dashboard)Flexible
row_limitparameter (up to 500)Multi-dimension filtering for advanced analytics
[0.1.0] — Initial release
20+ tools covering property management, search analytics, URL inspection, sitemap management, and operator queues
OAuth and service account authentication
Available Tools
32 toolsadd_siteA
Add a site to your Search Console properties.
Args:
site_url: The URL of the site to add (must be exact match e.g. https://example.com, or https://www.example.com, or https://subdomain.example.com/path/, for domain properties use format: sc-domain:example.com)
Inputs: site_url (required). Returns: result
audit_sitemap_urlsA
Safely fetch and parse an XML sitemap or sitemap index for read-only diagnostics.
This tool does not submit/delete sitemaps and does not call URL Inspection. It
validates the sitemap URL against the supplied GSC property scope before any
network request, resolves DNS to block unsafe IP targets, disables redirects,
and caps response bytes.
Args:
site_url: Exact GSC property URL from list_properties, or sc-domain:example.com
sitemap_url: Full URL of the sitemap XML to fetch
max_urls: Maximum number of URL or child sitemap entries to include in samples
Inputs: site_url (required), sitemap_url (required), max_urls. Returns: result
batch_url_inspectionA
Inspect multiple URLs in batch (within API limits).
Args:
site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or
"sc-domain:example.com"). Domain properties cover all subdomains — use the
domain property as site_url and filter by page to analyze a specific subdomain.
urls: List of URLs to inspect, one per line
Inputs: urls (required), site_url (required). Returns: result
build_indexing_action_queueA
Build a read-only prioritized action queue from URL Inspection data.
This tool does not request indexing. It only inspects URL-level indexed state for up to 10 URLs and recommends manual next steps.
Inputs: urls (required), site_url (required). Returns: result
check_indexing_issuesA
Check for specific indexing issues across multiple URLs.
Args:
site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or
"sc-domain:example.com"). Domain properties cover all subdomains — use the
domain property as site_url and filter by page to analyze a specific subdomain.
urls: List of URLs to check, one per line
Inputs: urls (required), site_url (required). Returns: result
compare_search_periodsA
Compare search analytics data between two time periods.
Args:
site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or
"sc-domain:example.com"). Domain properties cover all subdomains — use the
domain property as site_url and filter by page to analyze a specific subdomain.
period1_start: Start date for period 1 (YYYY-MM-DD)
period1_end: End date for period 1 (YYYY-MM-DD)
period2_start: Start date for period 2 (YYYY-MM-DD)
period2_end: End date for period 2 (YYYY-MM-DD)
dimensions: Dimensions to group by (default: query)
limit: Number of top results to compare (default: 10)
Inputs: site_url (required), period1_end (required), period2_end (required), period1_start (required), +3 more. Returns: result
delete_siteA
Remove a site from your Search Console properties.
Args:
site_url: The URL of the site to remove (must be exact match e.g. https://example.com, or https://www.example.com, or https://subdomain.example.com/path/, for domain properties use format: sc-domain:example.com)
Inputs: site_url (required). Returns: result
delete_sitemapA
Delete (unsubmit) a sitemap from Google Search Console.
Args:
site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or
"sc-domain:example.com"). Domain properties cover all subdomains — use the
domain property as site_url and filter by page to analyze a specific subdomain.
sitemap_url: The full URL of the sitemap to delete
Inputs: site_url (required), sitemap_url (required). Returns: result
get_advanced_search_analyticsA
Get advanced search analytics data with sorting, filtering, and pagination.
Args:
site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or
"sc-domain:example.com"). Domain properties cover all subdomains — use the
domain property as site_url and filter by page to analyze a specific subdomain.
start_date: Start date in YYYY-MM-DD format (defaults to 28 days ago)
end_date: End date in YYYY-MM-DD format (defaults to today)
dimensions: Dimensions to group by, comma-separated (e.g., "query,page,device")
search_type: Type of search results (WEB, IMAGE, VIDEO, NEWS, DISCOVER)
row_limit: Maximum number of rows to return (max 25000)
start_row: Starting row for pagination
sort_by: Metric to sort by (clicks, impressions, ctr, position)
sort_direction: Sort direction (ascending or descending)
filter_dimension: Single filter dimension (query, page, country, device). Use 'filters' instead for multiple filters.
filter_operator: Single filter operator (contains, equals, notContains, notEquals)
filter_expression: Single filter expression value
filters: JSON array of filter objects for AND logic across multiple dimensions. Overrides
filter_dimension/filter_operator/filter_expression when provided. Each object must
have 'dimension', 'operator', and 'expression' keys. Valid dimensions: query, page,
country, device. Valid operators: contains, equals, notContains, notEquals.
Example: [{"dimension":"country","operator":"equals","expression":"usa"},
{"dimension":"device","operator":"equals","expression":"MOBILE"}]
data_state: Data freshness — "all" (default, matches GSC dashboard) or "final" (confirmed data only, 2-3 day lag)
Inputs: site_url (required), filters, sort_by, end_date, +10 more. Returns: result
get_capabilitiesA
Get a full list of all available tools, current auth status, and how to get started. ALWAYS call this first when asked what tools are available, what this server can do, or how to get started. Returns all tool names grouped by category in a single call — faster than searching individually. Also shows if authentication is needed.
Inputs: no named parameters. Returns: result
get_creator_infoA
Provides information about Amin Foroutan, the creator of the MCP-GSC tool.
Inputs: no named parameters. Returns: result
get_performance_overviewA
Get a performance overview for a specific property.
Args:
site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or
"sc-domain:example.com"). Domain properties cover all subdomains — use the
domain property as site_url and filter by page to analyze a specific subdomain.
days: Number of days to look back (default: 28)
Inputs: site_url (required), days. Returns: result
get_search_analyticsA
Get search analytics data for a specific property.
Args:
site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or
"sc-domain:example.com"). Domain properties cover all subdomains — use the
domain property as site_url and filter by page to analyze a specific subdomain.
days: Number of days to look back (default: 28)
dimensions: Dimensions to group by (default: query). Options: query, page, device, country, date
You can provide multiple dimensions separated by comma (e.g., "query,page")
row_limit: Number of rows to return (default: 20, max: 500). Use 5-20 for quick overviews,
50-200 for deeper analysis, up to 500 for comprehensive reports. For bulk exports
beyond 500 rows, use get_advanced_search_analytics which supports pagination.
Inputs: site_url (required), days, row_limit, dimensions. Returns: result
get_search_by_page_queryA
Get search analytics data for a specific page, broken down by query.
Args:
site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or
"sc-domain:example.com"). Domain properties cover all subdomains — use the
domain property as site_url and filter by page to analyze a specific subdomain.
page_url: The specific page URL to analyze
days: Number of days to look back (default: 28)
row_limit: Number of rows to return (default: 20, max: 500). Use 5-20 for quick overviews,
50-200 for deeper analysis, up to 500 for comprehensive reports. For bulk exports
beyond 500 rows, use get_advanced_search_analytics which supports pagination.
Inputs: page_url (required), site_url (required), days, row_limit. Returns: result
get_site_detailsA
Get detailed information about a specific Search Console property.
Args:
site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or
"sc-domain:example.com"). Domain properties cover all subdomains — use the
domain property as site_url and filter by page to analyze a specific subdomain.
Inputs: site_url (required). Returns: result
get_sitemap_detailsA
Get detailed information about a specific sitemap.
Args:
site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or
"sc-domain:example.com"). Domain properties cover all subdomains — use the
domain property as site_url and filter by page to analyze a specific subdomain.
sitemap_url: The full URL of the sitemap to inspect
Inputs: site_url (required), sitemap_url (required). Returns: result
get_sitemapsA
List all sitemaps for a specific Search Console property.
Args:
site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or
"sc-domain:example.com"). Domain properties cover all subdomains — use the
domain property as site_url and filter by page to analyze a specific subdomain.
Inputs: site_url (required). Returns: result
gsc_audit_jobposting_schemaA
Read-only JobPosting JSON-LD audit and Indexing API eligibility dry run.
This tool fetches only property-scoped URLs, blocks unsafe/private targets,
does not follow redirects, parses JSON-LD JobPosting objects from static HTML,
validates a minimal Google JobPosting checklist, and returns what Indexing API
action would be eligible in a dry run. It never calls the Indexing API, never
publishes URL_UPDATED or URL_DELETED, never writes files, and never mutates
Search Console.
Inputs: urls (required), site_url (required), max_urls. Returns: result
gsc_build_cannibalization_decision_queueB
Build a read-only sampled decision queue for likely keyword cannibalization.
Uses one official Search Analytics query call with dimensions query,page. A query is a candidate when two or more distinct returned page URLs compete for that query. This is a diagnostic queue, not proof of cannibalization.
Inputs: site_url (required), end_date, row_limit, data_state, +4 more. Returns: result
gsc_build_content_action_queueB
Build a read-only prioritized content-opportunity action queue.
Uses one official Search Analytics query call and returns heuristic action items for high-impression/low-CTR rows, striking-distance rankings, and page/query refresh opportunities. It does not mutate Search Console state.
Inputs: site_url (required), max_ctr, end_date, max_items, +8 more. Returns: result
gsc_build_jobposting_lifecycle_queueA
Build a read-only JobPosting lifecycle action queue.
This composes the safe JobPosting schema audit with optional URL Inspection
diagnostics. It never calls the Google Indexing API, never publishes
URL_UPDATED/URL_DELETED, never requests indexing, never writes files, and
never mutates Search Console.
Inputs: urls (required), site_url (required), max_urls. Returns: result
gsc_build_traffic_drop_queueC
Build a read-only prioritized action queue for Search Analytics traffic drops.
Uses two official Search Analytics query calls, compares current vs previous rows by dimension keys, and returns stable JSON for operator/agent workflows.
Inputs: site_url (required), current_end (required), previous_end (required), current_start (required), +7 more. Returns: result
gsc_export_search_analytics_snapshotC
Export a read-only Search Analytics snapshot to JSONL and/or CSV plus manifest.
Files are written only below GSC_EXPORT_DIR when set, otherwise below the GSC
config directory's exports/ folder. This uses Search Analytics query pagination
and does not mutate Search Console state.
Inputs: site_url (required), filters, end_date, max_pages, +7 more. Returns: result
gsc_get_manual_operator_checklistA
Return a stable read-only checklist for Search Console UI-only/manual surfaces. This tool never calls Google APIs, never requires credentials, and never mutates Search Console. It tells an operator what to review and what evidence to bring back.
Inputs: focus, site_url. Returns: result
gsc_run_adjacent_technical_diagnosticsA
Run auth-free, read-only sampled adjacent technical diagnostics for supplied URLs.
This tool performs safe property-scoped HTML and robots.txt fetches only. It never calls Search Console, the Indexing API, PageSpeed Insights, CrUX, or Rich Results Test APIs, never writes files, and never mutates external state.
Inputs: urls (required), site_url (required), max_urls. Returns: result
gsc_run_weekly_seo_ops_reportB
Compose a read-only weekly SEO ops report from official Search Analytics data, existing diagnostic queues, and an auth-free static manual checklist.
Inputs: site_url (required), row_limit, data_state, current_end, +5 more. Returns: result
inspect_url_enhancedA
Enhanced URL inspection to check indexing status and rich results in Google.
Args:
site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or
"sc-domain:example.com"). Domain properties cover all subdomains — use the
domain property as site_url and filter by page to analyze a specific subdomain.
page_url: The specific URL to inspect
language_code: Optional IETF BCP-47 language code to pass to the URL Inspection API
Inputs: page_url (required), site_url (required), language_code. Returns: result
list_propertiesA
List all Google Search Console (GSC) properties and sites the user has access to.
Use this to see all verified sites, domain properties, and URL-prefix properties
in the connected Google Search Console account. Always call this first to get the
exact site_url needed for other tools.
Inputs: no named parameters. Returns: result
list_sitemaps_enhancedA
List all sitemaps for a specific Search Console property with detailed information.
Args:
site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or
"sc-domain:example.com"). Domain properties cover all subdomains — use the
domain property as site_url and filter by page to analyze a specific subdomain.
sitemap_index: Optional sitemap index URL to list child sitemaps
Inputs: site_url (required), sitemap_index. Returns: result
manage_sitemapsA
All-in-one tool to manage sitemaps (list, get details, submit, delete).
Args:
site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or
"sc-domain:example.com"). Domain properties cover all subdomains — use the
domain property as site_url and filter by page to analyze a specific subdomain.
action: The action to perform (list, details, submit, delete)
sitemap_url: The full URL of the sitemap (required for details, submit, delete)
sitemap_index: Optional sitemap index URL for listing child sitemaps (only used with 'list' action)
Inputs: action (required), site_url (required), sitemap_url, sitemap_index. Returns: result
reauthenticateA
Perform a logout and new login sequence. Deletes the current OAuth token file and triggers the browser authentication flow. Useful when you need to switch to a different Google account.
Inputs: no named parameters. Returns: result
submit_sitemapA
Submit a new sitemap or resubmit an existing one to Google.
Args:
site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or
"sc-domain:example.com"). Domain properties cover all subdomains — use the
domain property as site_url and filter by page to analyze a specific subdomain.
sitemap_url: The full URL of the sitemap to submit
Inputs: site_url (required), sitemap_url (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 32 tools
Many tools have overlapping purposes (e.g., get_sitemaps, list_sitemaps_enhanced, manage_sitemaps all can list sitemaps; get_search_analytics vs get_advanced_search_analytics). Detailed descriptions help distinguish, but the redundancy creates ambiguity.
Naming is inconsistent: some use verb_noun (list_properties, get_site_details), others use gsc_ prefix for diagnostics, but verbs vary (list vs get, build vs gsc_build). No single pattern is followed across all tools.
32 tools is excessive for GSC's limited API surface. Many tools are near-duplicates or highly specialized diagnostics that could be combined, making the toolset feel bloated.
Covers properties, sitemaps, URL inspection, search analytics, performance overview, and advanced diagnostics. Minor gaps like crawl errors or detailed index coverage, but overall a thorough surface for GSC.
Related MCP Connectors
Search Console, Google Analytics and keyword data for your AI agent.
Google Search Console for AI assistants: traffic, rankings, indexing and page checks. Read-only.
AI SEO agent on your Google Search Console data: audits, quick wins, content, WordPress publishing.
Real SEO data for AI assistants: page audits, Keyword Planner volumes, Search Console history.
Related MCP Servers
- AlicenseAqualityDmaintenanceConnects AI assistants to Google Search Console data for SEO analysis, including search analytics, URL inspection, sitemaps, indexing, and opportunity detection.17MIT
- AlicenseNot gradedqualityDmaintenanceConnects Google Search Console to AI assistants, enabling SEO data analysis via natural language conversations.MIT
- AlicenseAqualityDmaintenanceConnects Google Search Console to AI assistants, enabling natural language queries for SEO data, indexing audits, sitemap management, and full site audits.20MIT
- AlicenseAqualityDmaintenanceConnects Google Search Console to AI assistants, enabling natural language analysis of SEO data. Provides read-only tools for properties, search analytics, URL inspection, and sitemaps.15MIT