mcp-gsc
Provides tools to query search analytics, inspect URLs, manage sitemaps, and more via Google Search Console API.
Click on "Install 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., "@mcp-gscshow search analytics for last 30 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.
Quick Start
1. Get Credentials
You need OAuth client credentials from Google Cloud Console.
Go to Google Cloud Console
Create a project (or select existing)
Enable the Google Search Console API:
APIs & Services → Library → search "Google Search Console API" → Enable
Configure OAuth consent screen (if not done):
APIs & Services → OAuth consent screen → External
Fill in app name + your email, add scope
https://www.googleapis.com/auth/webmasters
Create credentials:
APIs & Services → Credentials → Create Credentials → OAuth client ID
Application type: Desktop app (allows localhost redirects automatically)
Download the JSON file
Set the credentials path:
export GOOGLE_GSC_CREDENTIALS_PATH=/path/to/credentials.jsonRun setup to authorize:
npx mcp-gsc setupThis opens your browser for OAuth consent, saves a refresh token, verifies access to your GSC properties, and prints config snippets for your MCP client.
2. Add to Claude Code
claude mcp add gsc --scope user --transport stdio \
-e GOOGLE_GSC_CREDENTIALS_PATH=/path/to/credentials.json \
-- npx -y mcp-gsc@latestThat's it. Restart Claude Code and the tools are available.
Also works with
bunx mcp-gsc@latestif you have Bun. Requires Node 18+ when running vianpx.
Claude Desktop / Cursor
Add to your claude_desktop_config.json:
{
"mcpServers": {
"gsc": {
"command": "npx",
"args": ["-y", "mcp-gsc@latest"],
"env": {
"GOOGLE_GSC_CREDENTIALS_PATH": "/path/to/credentials.json"
}
}
}
}Codex CLI
Add to ~/.codex/config.toml (TOML, not JSON):
[mcp_servers.gsc]
command = "npx"
args = ["-y", "mcp-gsc@latest"]
startup_timeout_sec = 30
env = { GOOGLE_GSC_CREDENTIALS_PATH = "/path/to/credentials.json" }Codex defaults to a 10s startup timeout, which is often too short for a cold
npxfetch. Bumpstartup_timeout_sec(30 is safe) or install the package globally (npm i -g mcp-gsc) and usecommand = "mcp-gsc"instead.
Service Account (alternative)
For server-to-server auth without browser-based OAuth:
Create a service account in Google Cloud Console
Download the JSON key file
In Google Search Console, add the service account email as a user for each property
Point
GOOGLE_GSC_CREDENTIALS_PATHto the key file — auth type is auto-detected
Related MCP server: gsc-mcp
Tools (25)
Core Tools (always available)
Sites
Tool | Description |
| List all GSC properties with permission levels |
| Verification info, ownership, permissions for a property |
Search Analytics
Tool | Description |
| Query search performance (clicks, impressions, CTR, position) with dimensions, filters, and brand segmentation |
Dimensions: query, page, country, device, date, searchAppearance, hour
Types: web, image, video, news, discover, googleNews
Note: searchAppearance cannot combine with query or page. hour requires data_state="hourly_all" (last 10 days only). Country codes are ISO 3166-1 alpha-3 (usa, gbr, deu).
Sitemaps
Tool | Description |
| List sitemaps with status, type, indexed counts, errors |
| Detailed sitemap info with content breakdown |
URL Inspection
Tool | Description |
| URL indexing status, crawl info, rich results, canonicals |
| Inspect up to 10 URLs at once with categorized results |
Rate limits: 600/minute + 2,000/day per site (tracked automatically).
Export
Tool | Description |
| Export full search analytics to CSV file (auto-paginates, up to 25K rows) |
Extended Tools (disabled by default)
Enable with GOOGLE_GSC_ENABLE_EXTENDED_TOOLS=true:
Reporting Suite
Tool | Description |
| Aggregate metrics + daily trend breakdown |
| Compare two date ranges with delta calculations |
| Biggest gains and drops between periods |
| Performance by device and/or country |
SEO Suite
Tool | Description |
| High-impression, low-CTR queries in striking distance (position 4-20) |
| Multiple pages competing for the same query |
| Emerging queries, growing impressions with low CTR, declining performers |
| Position changes over time for specific queries/pages |
| Queries with abnormal CTR relative to position |
| Pages/queries with impressions dropping >50% from historical peak |
| All-in-one report: overview + quick wins + top movers |
Technical SEO Suite
Tool | Description |
| Batch URL inspection with categorized indexing status |
| Sitemap error patterns, freshness, indexed vs submitted ratio |
Write Tools (disabled by default)
Enable with GOOGLE_GSC_ENABLE_WRITES=true:
Tool | Description |
| Add a new site to GSC |
| Remove a site from GSC |
| Submit a new sitemap |
| Remove/unsubmit a sitemap |
Configuration
Variable | Required | Default | Description |
| Yes | — | Path to OAuth client JSON or service account key |
| No | Derived | Path to cached OAuth token (default: |
| No | — | Default property URL (e.g., |
| No |
| Enable write tools |
| No |
| Enable extended analytics tools (13 extra) |
| No |
| Path to .env file |
| No | — | Enable debug logging |
Property resolution: You can pass bare domains like example.com — the server auto-resolves to sc-domain:example.com or https://example.com/ by matching against your verified properties.
Examples
Ask your AI assistant:
"Show me my top 10 queries this month"
"Find quick wins for example.com"
"Which pages have declining traffic over the last 3 months?"
"Check if these URLs are indexed: url1, url2, url3"
"Compare this week's performance to last week"
"Export all search analytics data to CSV for the last 28 days"
"Run a weekly SEO report for my site"
"Find keyword cannibalization issues"
Future Tool Ideas
Content gap analysis (requires competitor data integration)
Core Web Vitals integration (via PageSpeed Insights API)
Multi-property comparison
Search appearance deep analysis
Integration with Google Analytics for conversion data
Automated reporting schedules
Updates
Using npx @latest (recommended): You always get the latest version.
Using a binary: The server checks for new releases on startup and logs to stderr if outdated.
mcp-gsc --versionDevelopment
Requires Bun.
git clone https://github.com/pijusz/mcp-gsc.git
cd mcp-gsc
bun install
bun test # tests
bun run build # standalone binary
bun run inspect # MCP Inspector
bun run check # biome format + lintLicense
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/pijusz/mcp-gsc'
If you have feedback or need assistance with the MCP directory API, please join our Discord server