Which integrations are available for this server?

Provides tools for search analytics, performance summaries, URL inspection, sitemap management, and property listing through the Google Search Console API. Supports service account and OAuth authentication, read-only by default with optional write scope for sitemap submission.

How do I use mcp-server-google-search-console?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-server-google-search-console show 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.

mcp-server-google-search-console

by thein-art

Overview Schema Related Servers Score Discussions

TypeScript

Remote

mcp-server-google-search-console

Community-built MCP server for the Google Search Console API. Provides search analytics, performance summaries, URL inspection, sitemap management, and property listing through the Model Context Protocol.

Features

9 tools covering search analytics, performance summaries, URL inspection, sitemap management, and property listing
3 prompts for guided multi-step SEO workflows
2 resources for automatic property and sitemap discovery
Service Account & OAuth — choose headless or interactive authentication
Read-only by default — write tools are only registered when write scope is configured
Safety gates — delete_sitemap requires explicit confirm: true
Minimal dependencies — only @modelcontextprotocol/sdk and zod

Quick Start

1. Set Up Credentials

Service Account (recommended for servers & CI):

Go to Google Cloud Console
Create or select a project
Enable the Google Search Console API
Create a Service Account and download the JSON key file
In Google Search Console, add the service account email as a user to your properties

OAuth (recommended for personal use):

In Google Cloud Console, create OAuth 2.0 Client ID (type: Desktop app)
Download the client credentials JSON
Set GSC_OAUTH_CLIENT_FILE — the server will open a browser for consent on first run
Tokens are cached at ~/.config/gsc-mcp/oauth-token.json (or GSC_OAUTH_TOKEN_FILE)

2. Configure Your Client

claude mcp add google-search-console \
  -e GSC_SERVICE_ACCOUNT_KEY_FILE=/path/to/service-account-key.json \
  -- npx -y mcp-server-google-search-console

Or add to .mcp.json manually:

{
  "mcpServers": {
    "google-search-console": {
      "command": "npx",
      "args": ["-y", "mcp-server-google-search-console"],
      "env": {
        "GSC_SERVICE_ACCOUNT_KEY_FILE": "/path/to/service-account-key.json"
      }
    }
  }
}

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "google-search-console": {
      "command": "npx",
      "args": ["-y", "mcp-server-google-search-console"],
      "env": {
        "GSC_SERVICE_ACCOUNT_KEY_FILE": "/path/to/service-account-key.json"
      }
    }
  }
}

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "google-search-console": {
      "command": "npx",
      "args": ["-y", "mcp-server-google-search-console"],
      "env": {
        "GSC_SERVICE_ACCOUNT_KEY_FILE": "/path/to/service-account-key.json"
      }
    }
  }
}

Add to .vscode/mcp.json:

{
  "servers": {
    "google-search-console": {
      "command": "npx",
      "args": ["-y", "mcp-server-google-search-console"],
      "env": {
        "GSC_SERVICE_ACCOUNT_KEY_FILE": "/path/to/service-account-key.json"
      }
    }
  }
}

docker build -t gsc-mcp .

{
  "mcpServers": {
    "google-search-console": {
      "command": "docker",
      "args": [
        "run", "--rm", "-i",
        "-e", "GSC_SERVICE_ACCOUNT_KEY_FILE=/key.json",
        "-v", "/path/to/service-account-key.json:/key.json:ro",
        "gsc-mcp"
      ]
    }
  }
}

Tools

Always available (read-only scope)

Tool	Description
`list_sites`	List all GSC properties accessible by the current credentials
`get_site`	Get details for a specific property (permission level, verification)
`get_search_analytics`	Query search performance data with dimensions, filters, date ranges, and comparison mode
`get_performance_summary`	Quick performance overview: current vs previous period metrics, deltas, and top 10 queries in a single call
`inspect_url`	Check a URL's indexing status, mobile usability, and rich results
`batch_inspect_urls`	Inspect multiple URLs concurrently (up to 20) with a single call
`list_sitemaps`	List all sitemaps for a property with aggregated health summary

Write scope required

These tools are only registered when GSC_SCOPES includes the full write scope. They do not appear in the tool list otherwise.

Tool	Description
`submit_sitemap`	Submit a sitemap to Google
`delete_sitemap`	Delete a sitemap (requires `confirm: true` safety gate)

Prompts

Guided multi-step SEO workflows that guide LLMs through structured analysis.

Prompt	Parameters	Description
`seo_performance_analysis`	`site_url`, `period` (7d/28d/90d)	5-step analysis: Top Queries → Top Pages → Device Split → Country Split → Trends. Produces a structured report with actionable insights.
`index_coverage_check`	`site_url`, `urls` (comma-separated)	Batch URL inspection with structured coverage report — flags indexing issues, canonical mismatches, and mobile problems.
`content_opportunity_analysis`	`site_url`	Full-funnel analysis: Low-Hanging Fruit (positions 5–20), Keyword Cannibalization detection, and Trending queries via comparison mode.

Resources

URI	Description
`sites://list`	Auto-discovery of all GSC properties accessible with current credentials. Enables LLMs to discover available sites without calling `list_sites` first.
`sitemaps://{site_url}`	Sitemaps for a specific property (e.g. `sitemaps://sc-domain:example.com`) with health summary, errors, warnings, and index rates.

Environment Variables

Variable	Required	Description
`GSC_SERVICE_ACCOUNT_KEY_FILE`	*	Path to service account JSON key file
`GSC_SERVICE_ACCOUNT_KEY`	*	Inline service account JSON (alternative to file)
`GSC_OAUTH_CLIENT_FILE`	*	Path to OAuth client credentials JSON (Desktop app type)
`GSC_OAUTH_TOKEN_FILE`	No	Custom path for cached OAuth tokens (default: `~/.config/gsc-mcp/oauth-token.json`)
`GSC_SCOPES`	No	OAuth scope. Default: `webmasters.readonly`. Set to `https://www.googleapis.com/auth/webmasters` for write access

* Auth priority: OAuth (GSC_OAUTH_CLIENT_FILE) > Service Account (GSC_SERVICE_ACCOUNT_KEY_FILE or GSC_SERVICE_ACCOUNT_KEY). At least one must be configured.

Development

npm install      # Install dependencies
npm run build    # Build
npm run dev      # Watch mode
npm test         # Run tests

License

MIT

Note: This is an unofficial community project. It is not affiliated with or endorsed by Google.

Built by Tobias Hein at artaxo — a digital marketing agency specializing in AI Search Optimization.

This server cannot be installed

license - permissive license

quality - not tested

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

0dRelease cycle

2Releases (12mo)

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

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/thein-art/mcp-server-google-search-console'

If you have feedback or need assistance with the MCP directory API, please join our Discord server