Back to Browse

Search Console MCP Server

Developer ToolsUse Caution4.8MCP RegistryLocal
Free

Server data from the Official MCP Registry

Multi-account Google Search Console MCP: analytics, URL inspection, sitemaps across named accounts.

About

Multi-account Google Search Console MCP: analytics, URL inspection, sitemaps across named accounts.

Security Report

4.8
Use Caution4.8High Risk

This is a well-structured MCP server for Google Search Console with proper authentication, appropriate permission scoping, and solid error handling. OAuth and service account credentials are handled securely using Google's official libraries, tokens are stored in user-controlled locations (not hardcoded), and destructive operations are protected by an environment flag. Minor code quality observations noted, but no security vulnerabilities detected. Supply chain analysis found 5 known vulnerabilities in dependencies (1 critical, 3 high severity). Package verification found 1 issue.

7 files analyzed · 11 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

File System Write

Writes or modifies files on your machine. Check that this is expected for the tool.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

Path to accounts.json config file with GSC credentials. Defaults to ~/.config/mcp-search-console/accounts.jsonOptional

Environment variable: GSC_ACCOUNTS_CONFIG

Set to 'true' to enable sitemap submit/delete operationsOptional

Environment variable: GSC_ALLOW_DESTRUCTIVE

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-ayo-fam-mcp-search-console": {
      "env": {
        "GSC_ACCOUNTS_CONFIG": "your-gsc-accounts-config-here",
        "GSC_ALLOW_DESTRUCTIVE": "your-gsc-allow-destructive-here"
      },
      "args": [
        "mcp-search-console-multi"
      ],
      "command": "uvx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

mcp-search-console

Multi-account Google Search Console MCP server for operators who need one MCP surface across multiple sites or clients without restarting the server.

Release posture: beta package, version 0.1.3 from pyproject.toml.

Choose your path

You are...Start hereThen
Connecting the server to Claude/Codex/Cursordocs/start-here.mdQuick start below
Auditing account routing or destructive guardsdocs/architecture.mdgsc/server.py
Reviewing packaging or registry metadatapyproject.tomlserver.json

Architecture

flowchart TD
  U[AI operator] --> C[MCP client]
  C --> S[FastMCP server]
  S --> M[Account manager]
  M --> F[Accounts config]
  M --> A[OAuth or service-account auth]
  S --> R[Retry wrapper]
  R --> G[Google Search Console API]
  G --> R --> S

Request flow

flowchart TD
  P[Operator asks for analytics or indexing data] --> T[Selected MCP tool]
  T --> A[Resolve named or default account]
  A --> B[Build authenticated GSC client]
  B --> C[Call Search Console endpoint]
  C --> D{API call succeeds?}
  D -- yes --> E[Return normalized JSON]
  D -- retryable --> F[Backoff and retry]
  F --> D
  D -- no --> G[Return error payload]

Quick start

  1. Install the package.
python -m pip install mcp-search-console-multi
  1. Create the accounts config.
mkdir -p ~/.config/mcp-search-console
cp accounts.example.json ~/.config/mcp-search-console/accounts.json
  1. Register it in your MCP client.
{
  "mcpServers": {
    "search-console": {
      "command": "uvx",
      "args": ["mcp-search-console-multi"],
      "env": {
        "GSC_ACCOUNTS_CONFIG": "/Users/you/.config/mcp-search-console/accounts.json"
      }
    }
  }
}

Available tools

Tool groupToolsPurpose
Account routinglist_accounts, set_default_account, reauthenticateInspect accounts, switch defaults, refresh auth
Property inventorylist_properties, get_site_detailsDiscover accessible properties and permissions
Search analyticsget_search_analytics, get_performance_overview, compare_periods, get_advanced_search_analytics, get_search_by_pageQuery search-performance data
Inspection and sitemapsinspect_url, batch_inspect_urls, check_indexing_issues, list_sitemaps, get_sitemap, submit_sitemap, delete_sitemapInspect indexing and manage sitemap submissions

submit_sitemap and delete_sitemap stay behind the destructive flag documented in docs/start-here.md.

Runtime proof

ClaimProof
Package entry point is stablemcp-search-console-multi = "gsc.server:main" in pyproject.toml
Multi-account routing is first-classAccountManager() and _get_manager() in gsc/server.py
Search Console calls are retriedwith_retry() in gsc/server.py and gsc/retry.py
Auth is file-driven per accountaccounts.example.json and gsc/accounts.py

Repo map

PathPurpose
gsc/server.pyFastMCP tool surface and response normalization
gsc/accounts.pyAccount config, auth loading, client construction
gsc/auth/OAuth and service-account auth implementations
gsc/retry.pyRetry behavior for transient API failures
docs/start-here.mdSetup, env, validation, common failures
docs/architecture.mdComponent map and runtime lifecycle

Validation

CheckCommand
Import compilespython -m compileall gsc
Package buildspython -m build
README/docs links stay localrg '\\]\\(([^)]+\\.md)\\)' README.md docs/

License

MIT

Reviews

No reviews yet

Be the first to review this server!

Search Console MCP Server - Multi-account Google Search Console MCP: analytics, URL | MCP Marketplace