Google Search Console MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GSC_CREDENTIALS_PATH | Yes | Path to your Google service account credentials JSON file |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
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 20 tools
Most tools have distinct purposes, but there is notable overlap that could cause confusion. For example, 'get_sitemaps' and 'list_sitemaps_enhanced' both list sitemaps, and 'get_search_analytics' and 'get_advanced_search_analytics' serve similar functions with different feature sets. The descriptions help differentiate them, but an agent might struggle to choose between overlapping tools without careful reading.
The naming follows a consistent verb_noun pattern throughout, such as 'add_site', 'delete_sitemap', and 'get_performance_overview'. There are minor deviations like 'batch_url_inspection' (verb_adjective_noun) and 'reauthenticate' (single verb), but overall the pattern is predictable and readable.
With 20 tools, the count is borderline heavy for a Search Console server, as it might overwhelm agents. While the domain is broad, some tools like 'get_creator_info' and 'reauthenticate' seem peripheral, and overlaps (e.g., multiple sitemap tools) could have been consolidated, making the set feel slightly bloated.
The toolset covers core Search Console operations well, including site management, sitemap handling, URL inspection, and search analytics. However, there are minor gaps, such as no explicit tool for updating site details or handling security issues, and some redundancy (e.g., multiple sitemap tools) that doesn't add missing functionality. Overall, agents can perform most workflows effectively.