add_site
Add a site to the authenticated account. Requires write scope and verification still happens in Search Console.
LABSCO SUMMARY
The analysis layer that usually lives in a spreadsheet is on the server side of the call.
Most Search Console clients hand back rows and leave the interpretation to you; here traffic_drop_diagnosis attributes a loss to ranking, CTR or demand, ctr_opportunities compares against an expected-CTR curve, and search_intent_breakdown sorts queries into informational, commercial, transactional, navigational and local buckets. verify_claim is the unusual one: it re-queries the property to test a number you are about to present, against a tolerance percent you set. delete_site and delete_sitemap are both marked destructive in their own descriptions, and the URL Inspection and Indexing calls run sequentially, so batches are quota-bound by design.
What it is
A Search Console front end with 40 tools, covering the Search Analytics, URL Inspection, Sitemaps and Indexing APIs for the properties one authenticated account or service account can reach.
What you get
- Raw pulls when you know what you want: search_analytics for custom dimensions and filters, advanced_filter_query for up to 50,000 rows, top_queries and top_pages with cross-filtering, and dimension_breakdown for a single dimension.
- Period framing done for you: performance_overview returns a snapshot against the previous period with daily trend, devices and search appearances, compare_periods sets current against previous by page, query, country, device or appearance.
- Diagnoses rather than tables: traffic_drop_diagnosis separates ranking loss from CTR loss, demand decline or a mixed signal; content_decay looks across several equal periods instead of one noisy comparison; anomaly_alerts watches the latest period against the one before it.
- Opportunity finders with thresholds you set: quick_wins for positions 4-15, ctr_opportunities against an expected-CTR curve, cannibalization_check, device_country_opportunities, long_tail_questions and internal_link_opportunities.
- Content briefs backed by the property's own data: page_query_matrix maps pages to the queries driving them, query_page_fit reads one URL's query mix and intent, title_meta_brief builds a refresh brief from high-impression low-CTR queries.
- Index-side work: inspect_url, batch_inspect_urls and index_coverage_summary; list_sitemaps, get_sitemap, submit_sitemap and delete_sitemap; indexing_publish_url, indexing_batch_publish and indexing_get_metadata.
- Reporting and self-checks: multi_site_dashboard compares configured properties, generate_markdown_report writes a report to GSC_REPORT_DIR, and verify_claim re-queries the API to test a numeric claim against a tolerance you give it.
Requirements
A Search Console property and an account or service account with access to it, plus GSC_AUTH_MODE, GSC_KEY_FILE and GSC_SITE_URL in the environment. add_site, submit_sitemap and delete_sitemap need write scope, and generate_markdown_report writes into GSC_REPORT_DIR.
Setup effort
One command plus credentials — npx -y gsc-seo-mcp, then supply credentials
USE CASES
01
Explaining a traffic drop to someone who wants a cause, not a chart
Separate a ranking loss from a CTR loss or falling demand, then confirm whether the decline is a trend across periods or one noisy comparison.
02
Choosing which pages are worth rewriting this quarter
Start from queries already close to the first page and pages losing clicks, then turn the chosen page into a title and meta brief backed by its own query data.
03
Sorting out two pages fighting over the same query
Identify the queries where several URLs split impressions, see which page each query really belongs to, and get the internal links that would settle it.
04
Checking whether Google has actually picked up the pages you shipped
Inspect the URLs for indexed status and canonical, summarise coverage across the batch, and push the sitemap or an Indexing API notification for the ones that qualify.
05
Making sure a number in the client deck survives being checked
Re-query the property for the exact claim and tolerance before it is presented, pull the underlying rows if it fails, and hand over a report rather than a screenshot.
40 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
advanced_filter_query
Pull up to 50,000 Search Analytics rows with advanced filters for deeper audits.
anomaly_alerts
Detect recent page/query anomalies using the latest period versus the immediately previous period.
batch_inspect_urls
Inspect multiple URLs sequentially. Keep batches small to respect URL Inspection API quotas.
brand_nonbrand_split
Split performance into brand and non-brand search demand using configured or supplied brand terms.
cannibalization_check
Find queries where multiple pages compete and split impressions or clicks.
compare_periods
Compare current vs previous period by page, query, country, device, or search appearance.
content_decay
Detect pages declining across multiple equal periods, not just one noisy comparison.
ctr_opportunities
Find queries and pages where CTR is below an expected CTR curve for the current average position.
delete_site
Remove a site from the authenticated account. Destructive: use only when explicitly requested.
delete_sitemap
Delete a submitted sitemap from Search Console. Destructive: use only when explicitly requested.
device_country_opportunities
Find device and country segments with high impressions but weak CTR or ranking.
dimension_breakdown
Break performance down by a single dimension such as country, device, date, or search appearance.
generate_markdown_report
Generate a Markdown SEO performance report and save it to GSC_REPORT_DIR.
get_site
Get permission details for a specific Search Console property.
get_sitemap
Get details for one sitemap URL.
index_coverage_summary
Summarize indexed/not-indexed/canonical coverage for a supplied list of URLs.
indexing_batch_publish
Publish multiple Indexing API URL notifications sequentially. Use only for eligible pages and respect quota.
indexing_get_metadata
Check the latest Indexing API update/remove notification metadata for a URL.
indexing_publish_url
Notify Google that an eligible URL was updated or removed through the Indexing API.
inspect_url
Inspect a URL's indexed status, canonical, crawl, robots, and coverage signals.
internal_link_opportunities
Suggest internal linking opportunities from stronger pages to weaker pages sharing valuable queries.
list_properties
List Search Console properties available to the authenticated user or service account.
list_sitemaps
List submitted sitemaps with status, errors, warnings, and indexed URL counts.
long_tail_questions
Surface question and long-tail queries that can become FAQ sections, support docs, or content expansions.
multi_site_dashboard
Compare configured Search Console properties in one health dashboard.
page_query_matrix
Map pages to the queries that drive them. Great for content briefs and cannibalization review.
page_refresh_priorities
Prioritize pages to update using lost clicks, declining impressions, CTR gaps, and position changes.
performance_overview
Return a site-level snapshot with previous-period comparison, daily trend, devices, and search appearances.
query_page_fit
Analyze one URL's query mix, intent fit, and content angles based on the queries it already ranks for.
quick_wins
Find keywords ranking around positions 4-15 where better content, internal links, or snippets can win traffic.
search_analytics
Run a flexible Search Analytics query. Use this for exact data pulls with custom dimensions and filters.
search_intent_breakdown
Classify queries into informational, commercial, transactional, navigational, and local intent buckets.
server_health
Show server configuration, enabled defaults, and tool count without exposing secrets.
submit_sitemap
Submit or refresh a sitemap in Search Console. Requires write scope.
title_meta_brief
Create a data-backed title/meta refresh brief from high-impression, low-CTR queries for one page.
top_pages
Find top pages with optional query filtering, useful for landing page and folder audits.
top_queries
Find top queries with optional page filtering, useful for keyword and content research.
traffic_drop_diagnosis
Explain page or query traffic losses as ranking loss, CTR loss, demand decline, or mixed signal.
verify_claim
Re-query GSC to verify a numeric SEO claim before presenting it to a client or stakeholder.
BEFORE YOU INSTALL
What to know first
Tools you get
40 tools when we connected. The three indexing_ tools need the Indexing API enabled and only work for JobPosting and BroadcastEvent pages; brand_nonbrand_split needs GSC_BRAND_TERMS and multi_site_dashboard needs GSC_SITE_URLS.
Requires
- npx on PATH
- Node.js 20+
- GSC_SITE_URL in your environment
- GSC_KEY_FILE (service account) or GSC_OAUTH_SECRETS_FILE (browser sign-in) in your environment
Where it runs
All 5 documented clients run the server on your machine.
CONTEXT COST
Moderate Standing cost
Rated by the size of the 40 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y gsc-seo-mcpMCP Clients
Cursor
CURSOR · JSON
{
"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:<YOUR_DOMAIN>",
"GSC_BRAND_TERMS": "mybrand,mybrand.com"
}
}
}
}.cursor/mcp.json
Claude Desktop
CLAUDE DESKTOP · JSON
{
"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:<YOUR_DOMAIN>"
}
}
}
}Claude Code
CLAUDE CODE · JSON
{
"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:<YOUR_DOMAIN>"
}
}
}
}.mcp.json
Gemini CLI
GEMINI CLI · JSON
{
"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:<YOUR_DOMAIN>"
},
"timeout": 120000,
"trust": false
}
}
}~/.gemini/settings.json
Any MCP client — OAuth
ANY MCP CLIENT — OAUTH · JSON
{
"mcpServers": {
"gsc-seo": {
"command": "npx",
"args": [
"-y",
"gsc-seo-mcp"
],
"env": {
"GSC_AUTH_MODE": "oauth",
"GSC_OAUTH_SECRETS_FILE": "<YOUR_GSC_OAUTH_SECRETS_FILE>",
"GSC_TOKEN_FILE": "<YOUR_GSC_TOKEN_FILE>",
"GSC_SITE_URL": "sc-domain:<YOUR_DOMAIN>"
}
}
}
}
