@lomi./gsc-mcp
This MCP server lets you read and analyze Google Search Console data (and optionally write sitemaps/properties) through typed tools.
Portfolio & property discovery: list accessible properties, get permission details, and check server capabilities/auth.
Search analytics: query clicks, impressions, CTR, and position with dimensions, filters, pagination, freshness, and search types.
Performance analysis: overview of recent performance, period-over-period comparison, and quick-win opportunity detection.
URL inspection: inspect a single URL or batch up to 20 URLs for indexing status, and summarize non-indexable issues.
Sitemaps: list and get details for submitted sitemaps.
Read-only by default; mutations require explicit write scope and
GSC_ENABLE_WRITES=true.Flexible auth: supports Google Application Default Credentials, desktop OAuth with PKCE, or service account JSON.
Local stdio and self-hosted HTTP transports for Cursor, Claude Desktop, or team servers.
Provides tools for querying Google Search Console search analytics, comparing performance across periods, inspecting URL indexing status, and identifying quick-win opportunities for a site property.
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., "@@lomi./gsc-mcp show me the top search queries for last 28 days"
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.
@lomi./gsc-mcp
Public Model Context Protocol server for Google Search Console.
Repository: github.com/lomiafrica/gsc-mcp — standalone project. In the lomi. monorepo it is checked out as a submodule at apps/tools/gsc-mcp.
Features
Portfolio health across every accessible property (or
GSC_PORTFOLIO_SITES)Typed Search Analytics with dimensions, filters, pagination, and freshness controls
Performance overview, period comparison, and quick-win opportunity detection
URL inspection with bounded batch support
Sitemap and property discovery
Read-only by default; mutation tools require explicit write scope and
GSC_ENABLE_WRITES=trueLocal stdio for Cursor and Claude Desktop
Secure self-hosted Streamable HTTP for teams
Related MCP server: GSC MCP Server
Monorepo checkout
Inside the lomi. monorepo:
git submodule update --init apps/tools/gsc-mcp
cd apps/tools/gsc-mcp
pnpm install
pnpm run buildQuick start
Preferred: Application Default Credentials plus a quota project that has the Search Console API enabled.
gcloud auth application-default login \
--scopes=https://www.googleapis.com/auth/cloud-platform,https://www.googleapis.com/auth/webmasters.readonlyThen add to Cursor:
{
"mcpServers": {
"google-search-console": {
"command": "npx",
"args": ["-y", "@lomi./gsc-mcp"],
"env": {
"GOOGLE_CLOUD_QUOTA_PROJECT": "your-gcp-project-id",
"GSC_PORTFOLIO_SITES": "sc-domain:example.com"
}
}
}
}Cursor Connect only reconnects this local server. It does not sign in to Google.
Authentication
Choose one:
Application Default Credentials (
gcloud auth application-default login) plusGOOGLE_CLOUD_QUOTA_PROJECTDesktop OAuth with PKCE: put a Google Desktop client JSON at
~/.config/lomi-gsc-mcp/oauth_credentials.json, thennpx -y @lomi./gsc-mcp authService account JSON via
GSC_SERVICE_ACCOUNT_KEY_FILE
Default OAuth scope is read-only. Set GSC_OAUTH_SCOPE=write and GSC_ENABLE_WRITES=true only when you need sitemap or property mutations.
Start with gsc_portfolio_health. Sitemap contents.indexed is often 0 even when pages are indexed; use homepage inspection.
Self-hosted HTTP
GSC_MCP_TRANSPORT=http \
GSC_MCP_CLIENT_BEARER_TOKEN=replace-me \
GSC_MCP_ALLOWED_HOSTS=localhost \
GSC_MCP_ALLOWED_ORIGINS=http://localhost:3000 \
npx -y @lomi./gsc-mcp-httpNon-loopback HTTP requires GSC_MCP_CLIENT_BEARER_TOKEN.
Docs
See https://docs.lomi.africa/build/mcp.
License
MIT
Available Tools
5 toolsgsc_capabilitiesSearch Console capabilitiesARead-onlyIdempotent
Return active auth mode, scopes, limits, and disclosure notes for this server.
Inputs: no named parameters.
gsc_compare_periodsCompare search periodsARead-onlyIdempotent
Compare top rows between two date ranges for the same dimensions.
Inputs: site_url (required), period1_end (required), period2_end (required), period1_start (required), +4 more.
gsc_inspect_urlInspect URLBRead-onlyIdempotent
Inspect one URL indexing status in Google Search Console.
Inputs: site_url (required), inspection_url (required), language_code.
gsc_quick_winsFind quick-win queriesBRead-onlyIdempotent
Identify queries with meaningful impressions, low CTR, and positions in a target range.
Inputs: end_date (required), site_url (required), start_date (required), max_ctr, +4 more.
gsc_search_analyticsSearch analytics queryCRead-onlyIdempotent
Query clicks, impressions, CTR, and position with dimensions, filters, pagination, and data freshness controls.
Inputs: end_date (required), site_url (required), start_date (required), filters, +6 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a distinct purpose: capabilities (metadata), search analytics (raw data), quick wins (heuristic analysis), compare periods (comparative analysis), inspect URL (individual URL status). No overlap.
All tools start with 'gsc_' and follow a verb_noun or noun phrase pattern. Most are nouns or adjective-noun (e.g., quick_wins), while compare_periods and inspect_url use verbs. Consistent prefix but minor variation in verb usage.
5 tools is appropriate for a focused GSC server covering analytics, insights, and URL inspection. Not overly many nor too few, though additional tools could be justified.
Covers core search analytics and URL inspection, but missing tools for sitemap management, index coverage, site listing, or mobile usability. Notable gaps for a full GSC integration.
Maintenance
Related MCP Connectors
Hosted, read-only Google Search Console MCP: performance, comparisons, URL inspection, sitemaps.
Read-only Google Search Console MCP server for AI assistants.
Hosted Google Search Console MCP server, with each action switched on or off per account.
Free Google Search Console MCP + Bing Webmaster Tools: queries, URL inspection, sitemaps.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Google Search Console via MCP, offering search analytics, performance summaries, URL inspection, sitemap management, and property listing for SEO workflows.262 npm1MIT
- AlicenseAqualityCmaintenanceConnects MCP clients to the Google Search Console API, enabling search analytics queries, URL inspection, sitemap management, and performance comparison across time periods.2066 PyPIMIT
- AlicenseAqualityFmaintenanceEnables natural language interaction with Google Search Console data, including property management, search analytics, URL inspection, and sitemap management via MCP.21MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to query Google Search Console search performance, inspect indexing, analyze sitemaps, and run SEO analyses such as cannibalisation detection, query clustering, and wins/losses, all with read-only access.20119 npmApache 2.0