GSC MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SSL_CERT_FILE | No | Path to a CA bundle file to trust for TLS/SSL connections. Optional, used on Windows or managed networks with a custom CA. | |
| REQUESTS_CA_BUNDLE | No | Path to a CA bundle file to trust for HTTP requests. Optional, used on Windows or managed networks with a custom CA. | |
| GOOGLE_APPLICATION_CREDENTIALS | No | Path to a service account key file for Application Default Credentials, used when authenticating as a service account. | |
| GRPC_DEFAULT_SSL_ROOTS_FILE_PATH | No | Path to a CA bundle file to trust for gRPC connections. Optional, used when a custom CA is required. |
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
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 |
|---|---|
| list_sitesA | Read-only. List every Google Search Console property available to the current ADC identity, preserving each exact property identifier and permission level. |
| query_search_analyticsA | Read-only. Query first-party Google Search Console performance data and return named dimensions with clicks, impressions, raw CTR fraction, and Search Console average position. Results are top rows, not a complete query universe. |
| inspect_urlA | Read-only. Return Google URL Inspection information for the version currently in Google's index. This is not a live URL test and never requests 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 3 tools
Each tool targets a distinct concern: site discovery, performance querying, and URL inspection. There is no overlap between listing properties, pulling analytics, or checking indexed URL status.
All tool names follow a consistent snake_case verb_noun pattern: list_sites, query_search_analytics, inspect_url. The naming clearly communicates the action and resource.
Three tools is lean but reasonable for a read-only Search Console server focused on core workflows. The count is not excessive, though adding a couple more relevant operations could make the set feel fuller.
The core Search Console needs are covered: site selection, performance data, and URL inspection status. Missing operations like sitemap submission or site management are notable but not critical for a read-only analytics-oriented server.