Vosik Signals Google Search Console
Read-only Google Search Console MCP server for AI assistants.
What can you do with Vosik Signals Google Search Console?
- Discover Search Console properties available to your Google account.
- Retrieve daily search performance and query/page breakdowns.
- Explore clicks, impressions, click-through rate, and average position.
- Inspect URL indexing status.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http vosik-signals-google-search-console 'https://gsc.vosiksignals.win/mcp'
{
"mcpServers": {
"vosik-signals-google-search-console": {
"type": "http",
"url": "https://gsc.vosiksignals.win/mcp"
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
Vosik Signals — Google Search Console MCP
Hosted, read-only Google Search Console integration for MCP-compatible AI assistants.
Remote MCP endpoint: https://gsc.vosiksignals.win/mcp
This repository contains documentation and Registry metadata, not the production server source code. The server is hosted by Vosik Signals; no local installation is required.
Part of Vosik Signals, alongside the Google Analytics 4 MCP.
What it does
Explore Search Console data using an AI assistant:
- Discover Search Console properties available to your Google account.
- Retrieve daily search performance and query/page breakdowns.
- Explore clicks, impressions, click-through rate, and average position.
- Inspect URL indexing status.
Google API results can be sampled, limited, delayed, or incomplete. Missing rows do not necessarily mean zero traffic.
Connect
- In an AI client supporting remote Streamable HTTP MCP and OAuth, add a custom MCP server.
- Enter:
https://gsc.vosiksignals.win/mcp - Complete Google OAuth authorization with an account that can access your Search Console property.
- Ask: “List the Google Search Console properties I can access.”
ChatGPT is the primary integration used during development. Compatibility with other MCP clients depends on their remote OAuth support and should be tested.
Example prompts
- List my Search Console properties.
- Show clicks and impressions by day for the last 28 days.
- Which queries lead to a particular page?
- Inspect the indexing status of a URL.
Privacy and security
The server uses Google OAuth with the read-only https://www.googleapis.com/auth/webmasters.readonly scope. The connector does not modify Search Console properties.
See the Privacy Policy for details on data handling, credential protection, retention, and deletion.
Never share OAuth tokens, sensitive property data, or private reports in public GitHub issues.
Support
Report bugs and client compatibility results via GitHub Issues, with sensitive information redacted.
This documentation repository is not an open-source release of the hosted server implementation.
Frequently asked questions
What is Vosik Signals Google Search Console?
Read-only Google Search Console MCP server for AI assistants.
How do I install Vosik Signals Google Search Console?
It runs as a remote server. In Claude Code: claude mcp add --transport http vosik-signals-google-search-console 'https://gsc.vosiksignals.win/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Vosik Signals Google Search Console need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Vosik Signals Google Search Console open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains Vosik Signals Google Search Console?
It is published by Vosikkk. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.