Google Search Console MCP Server

What is Google Search Console MCP Server?

Google Search Console MCP Server is an MCP (Model Context Protocol) server that transforms raw Google Search Console signals into actionable marketing insights. It is designed for marketers who need to understand website performance in a search landscape increasingly defined by AI Overviews and conversational search, and is compatible with any MCP-compliant AI agent.

How to use Google Search Console MCP Server?

Install via pip install google-search-console-mcp. Configure your MCP-compliant AI agent by adding a JSON entry to its settings file with the command gsc-mcp and environment variables GOOGLE_APPLICATION_CREDENTIALS (path to your service account JSON key) and GSC_SITE_URL (e.g., sc-domain:example.com). Beforehand, you must set up a Google Cloud service account, enable the Search Console API, grant that account Full permissions in Google Search Console, and identify your property URL.

Key features of Google Search Console MCP Server

• Audits search appearance for cannibalization insights
• Segments traffic into "Searchers" and "Prompters"
• Recommends click triggers from high-visibility content
• Cross-checks pages with URL Inspection API for crawl errors
• Measures brand reference value vs. destination value
• Calculates intent efficiency for each search intent type

Use cases of Google Search Console MCP Server

• Detect when your site is used as a "Silent Reference" in SERP features with high visibility but no clicks
• Understand whether traffic comes from traditional keyword searchers or natural-language AI prompters
• Find content that satisfies user intent so well users don't click, and identify actionable click-triggers
• Audit technical health by checking high-visibility pages for disqualifying crawl errors
• Measure your brand's "Reference Value" versus its "Destination Value" in search

FAQ from Google Search Console MCP Server

What Google APIs does this server use?

It uses only official Google Search Console API signals. It also leverages the URL Inspection API for technical citation audits.

What are the runtime requirements?

Python (via PyPI), a Google Cloud service account with a JSON key, and a configured Google Search Console property with the service account granted Full permissions.

Where does the data live?

All processing happens server-side; the server aggregates data from Google Search Console before sending results to the AI agent, preventing context length issues.

Which AI agents are compatible?

Any MCP-compliant AI agent can use this server via the standard MCP settings configuration.

How do I specify my site in the config?

For domain properties use sc-domain:example.com; for URL-prefix properties use the full URL like https://example.com/.