Vosik Signals Google Search Console

io.github.Vosikkkv1.0.0Updated Oct 8, 2026

Read-only Google Search Console MCP server for AI assistants.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Lets an assistant read Google Search Console data — properties, search performance, query and page breakdowns, and URL indexing status.

What it does
A hosted, read-only Google Search Console integration for MCP-compatible assistants. It can list the Search Console properties a Google account can access, retrieve daily search performance, break results down by query and page, report clicks, impressions, click-through rate and average position, and inspect URL indexing status. It does not modify Search Console properties.
When to use it
Useful when you want to ask an assistant about organic search performance, top queries, or indexing status without opening the Search Console interface. Best for read-only reporting and quick lookups rather than configuration changes.
Requirements
A remote Streamable HTTP MCP endpoint; no local installation. The client must support remote MCP with OAuth. You complete Google OAuth authorization with an account that can access the Search Console property, using the read-only webmasters.readonly scope. ChatGPT is the primary tested client; other clients depend on their remote OAuth support.
Before you install
Authorization grants read access to your Google Search Console data through the webmasters.readonly scope, and the server is hosted by a third party, so property data is handled on their infrastructure. Results can be sampled, limited, delayed, or incomplete, and missing rows do not necessarily mean zero traffic. Do not share OAuth tokens or private reports publicly.

Installation

In SourceWeft

  1. Open Vosik Signals Google Search Console in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "google-search-console-mcp": {
      "type": "http",
      "url": "https://gsc.vosiksignals.win/mcp"
    }
  }
}

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:

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

Source: README.md at commit 67125dc

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestOct 8, 2026