mcpField
V
Vosik Signals Google Search Console

Vosik Signals Google Search Console

Remote
vosiksignals.winBusiness & Marketing0Updated 3w ago
RepositoryVisit website

About Vosik Signals Google Search Console

Vosik Signals Google Search Console is a hosted, read-only MCP integration for AI assistants exploring Search Console data. It retrieves search performance and URL indexing details; the hosted server implementation is not published.

Key features

  1. 01Discover accessible Search Console properties
  2. 02Retrieve daily performance and query or page breakdowns
  3. 03Review clicks, impressions, CTR, and average position
  4. 04Inspect URL indexing status

Use cases

  1. 01Compare daily clicks and impressions
  2. 02Find queries leading to a page
  3. 03Check a URL's indexing status

MCP support

Exposes Search Console property discovery, performance data, and URL indexing status to MCP clients through a hosted remote endpoint. It uses Streamable HTTP and Google OAuth with read-only access.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gsc.vosiksignals.win/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

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

  1. In an AI client supporting remote Streamable HTTP MCP and OAuth, add a custom MCP server.

  2. Enter:

    https://gsc.vosiksignals.win/mcp

  3. Complete Google OAuth authorization with an account that can access your Search Console property.

  4. 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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.