flin-google-search-console-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_CLIENT_ID | Yes | Your OAuth client ID for Google Search Console API. | |
| GOOGLE_CLIENT_SECRET | Yes | Your OAuth client secret for Google Search Console API. | |
| GOOGLE_SEARCH_CONSOLE_SITE_URL | No | Optional default site URL to avoid passing site_url every time. | |
| GOOGLE_SEARCH_CONSOLE_TOKEN_PATH | No | Optional custom path for storing the OAuth token file. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Read-only MCP server for Google Search Console performance analysis and URL inspection. No write operations are exposed.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkB | Check local configuration and saved sign-in status without opening a browser or calling Google. |
| list_sitesA | List properties available to the selected Google account before choosing a site to analyse. Opens Google sign-in in the browser if needed and saves or refreshes the local token. Does not modify Search Console properties. |
| get_site_summaryC | Get aggregate performance metrics for a property over a date range. |
| query_performanceC | Query Search Analytics performance data with explicit dimensions and filters. |
| get_top_queriesC | Get top query rows for a property over a date range. |
| get_top_pagesC | Get top page rows for a property over a date range. |
| get_dimension_breakdownD | Get a single-dimension Search Analytics breakdown. |
| inspect_urlB | Read Google's indexed status for a URL within an accessible property; does not request indexing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools are clearly distinct, but query_performance overlaps heavily with get_top_queries, get_top_pages, and get_dimension_breakdown, which are convenience wrappers around the same Search Analytics data. An agent may struggle to choose between the generic query tool and the specialized top-N tools.
Nearly all tools follow a consistent snake_case verb_noun pattern (list_sites, get_site_summary, query_performance, inspect_url). health_check is a minor deviation as a noun phrase, but overall naming remains predictable.
Eight tools are well-scoped for a Google Search Console analytics server. Each tool covers a distinct operation, and the count avoids both thinness and bloat.
The surface covers authentication status, site listing, aggregate metrics, flexible queries, top-N reports, dimension breakdowns, and URL inspection status. Minor gaps exist around sitemap management and requesting indexing, but core read-oriented workflows are complete.