Best for
- SEO professionals
- Content marketers
- Website owners
- Developers integrating Search Console data into their applications or workflows.
G
Google Search Console MCP Server
Community
Comprehensive access to Google Search Console via MCP, with advanced analytics and quick win detection.
GitHub source repository ↗
69FMRS · C
Based on the feature list in the README, the server appears feature-rich, but the source provides no user reviews or usage experience. As a third-party project, use with caution and ensure key security.
This is a Model Context Protocol (MCP) server that provides access to Google Search Console data. It offers enhanced analytics capabilities such as retrieving up to 25,000 rows of performance data, advanced filtering including regex patterns, quick wins detection, and rich dimensions like query, page, country, device, and search appearance.
Tools
search_analytics
Fetches search performance data from Google Search Console, supporting advanced filtering, dimension grouping, and quick wins detection.
Setup
- In Google Cloud Console, create a project and enable the Search Console API.
- Create a service account and generate a JSON key file.
- In Search Console, add the service account email as a property administrator.
- Install the npm package: npm install mcp-server-gsc
- Configure your client (e.g., Claude Desktop) to run the server with npx and set the environment variable GOOGLE_APPLICATION_CREDENTIALS to the JSON key file path.
claude_desktop_config.json
{
"mcpServers": {
"gsc": {
"command": "npx",
"args": [
"-y",
"mcp-server-gsc"
],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "/path/to/credentials.json"
}
}
}
}
Fit and risk
Not for
- Users without a Google Cloud project or Search Console access.
- Those needing real-time data (default is final data, but 'all' option exists).
- Non-technical users may find setup challenging due to required Google Cloud configuration.
Required permissions
- Requires a Google Cloud service account key with access to the Search Console API.
- The service account must be granted property administrator rights in Search Console.
- The server reads the key via environment variable, typically for external services.
Risks and side effects
- Credential leak risk: If the service account key is not stored securely, data may be exposed. Use secret management services.
- Data access scope: The service account can access all authorized Search Console properties, including sensitive performance data.
- This is a third-party project, not an official Google server, and may not have undergone security auditing. Evaluate trustworthiness before use.
- Potential Google Cloud API costs, though Search Console API is usually free within quotas.
Troubleshooting
- Ensure the service account is added to Search Console and has permissions.
- Check that the JSON key file path is correct and the service account is enabled.
- Make sure the Search Console API is enabled.
- Verify date format is YYYY-MM-DD.
- If you encounter permission errors, confirm the service account email is added as a property administrator.
Use cases
Analyze website search performance including clicks, impressions, CTR, and average position.
Segment data by query, page, country, device, and search appearance.
Identify optimization opportunities (quick wins) by setting thresholds for position, impressions, and CTR.
Apply advanced filters using regex, e.g., to include or exclude specific query patterns.
Supported clients
Claude DesktopFull support