SearchConsole.ai

ai.searchconsolePublished by searchconsole.aiOfficial publisherv1.0.1Updated Oct 24, 2026

Read-only Search Console analytics, URL inspection, indexing diagnostics, and sitemaps.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Lets an assistant read Google Search Console search analytics, inspect URLs, check indexing diagnostics and review sitemaps for your properties.

What you can do
A hosted, read-only Google Search Console MCP server (R2). It provides GSC search analytics, period comparisons, URL inspection, indexing diagnostics and sitemaps (R9), so an assistant can compare clicks, impressions, CTR and average position across periods, find high-impression low-CTR queries, inspect a page's indexing status, and list sitemaps with reported errors or warnings (R27-R32). It reads Search Console data only and does not edit the website, submit sitemaps or request indexing (R34).
When to use it
Use it for SEO reporting and diagnostics when you want an assistant to answer questions about your own Search Console properties without building a Google Cloud project or handling OAuth credentials yourself (R3, R6). It suits period-over-period performance comparisons, query and page opportunity analysis, indexing checks and sitemap review (R27-R32).
Requirements
A remote Streamable HTTP MCP endpoint at (R7, R20); no local server runs (R16). An OAuth-capable MCP client such as Codex, Claude Code, Cursor or ChatGPT (R10), and a Google account with access to the Search Console properties you want to query (R24). The optional setup CLI runs via npx (R3). No Google Cloud project or downloaded OAuth credentials are needed (R6).
Before you install
Read-only: it does not edit the site, submit sitemaps or request indexing (R34). Access is granted through Google OAuth with read-only Search Console scope (R8); the setup package itself never asks for, receives or stores Google credentials (R17), and authentication is handled by the MCP client and the hosted OAuth service (R18). The Cursor setup writes to ~/.cursor/mcp.json, creating a backup first (R13); a dry-run preview is available (R14). Search Console data is sent to the hosted service…

Installation

In SourceWeft

  1. Open SearchConsole.ai in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.searchconsole%2Fsearchconsole-ai/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "searchconsole-ai": {
      "type": "http",
      "url": "https://searchconsole.ai/mcp"
    }
  }
}

README

Google Search Console MCP (GSC) — SearchConsole.ai

SearchConsole.ai is a hosted, read-only Google Search Console MCP server for GSC search analytics, SEO performance, URL inspection, indexing diagnostics, and sitemaps. Use the Google Search Console API as an SEO MCP integration in Codex, Claude Code, Cursor, ChatGPT, or another OAuth-capable MCP client without creating a Google Cloud project.

bash
npx -y searchconsole-ai@latest setup

Or choose a client directly:

bash
npx -y searchconsole-ai@latest setup codexnpx -y searchconsole-ai@latest setup claudenpx -y searchconsole-ai@latest setup cursor

Google Search Console MCP features

  • No Google Cloud project or downloaded OAuth credentials
  • Hosted Streamable HTTP MCP endpoint
  • Google OAuth with read-only Google Search Console access
  • GSC search analytics, period comparisons, URL inspection, indexing diagnostics, and sitemaps
  • Works with Codex, Claude Code, Cursor, ChatGPT, and other OAuth-capable MCP clients

What the setup command does

For Codex and Claude Code, the CLI invokes the client's supported mcp add command and starts its MCP OAuth flow. For Cursor, it safely adds this entry to ~/.cursor/mcp.json, preserving existing configuration and creating a backup before changing an existing file:

json
{  "mcpServers": {    "searchconsole-ai": {      "type": "http",      "url": "https://searchconsole.ai/mcp"    }  }}

Preview changes without applying them:

bash
npx -y searchconsole-ai@latest setup cursor --dry-run

Configure a command-line client without opening OAuth immediately:

bash
npx -y searchconsole-ai@latest setup codex --no-login

This package does not contain or run a local Search Console server. It never asks for, receives, or stores Google credentials. Authentication is handled by the MCP client and the hosted SearchConsole.ai OAuth service.

Manual configuration

Add a remote Streamable HTTP MCP server named searchconsole-ai with this URL:

text
https://searchconsole.ai/mcp

Full instructions: searchconsole.ai

Public source and release history: github.com/AndreyAzimov/searchconsole-ai

How to use it

After configuring the server, complete the client's OAuth sign-in with a Google account that has access to your Search Console properties. Then ask your AI assistant to use SearchConsole.ai, specifying the property and date range you want to analyze.

Example prompts:

  • "For example.com, compare clicks, impressions, CTR, and average position for the last 28 complete days with the preceding 28 days. Which pages lost the most clicks?"
  • "Find queries for example.com with high impressions and low CTR over the last 28 complete days. Suggest improvements based on the Search Console data."
  • "Inspect https://example.com/my-page and explain the indexing status reported by Google Search Console."
  • "List the sitemaps for example.com and summarize any reported errors or warnings."

Replace the example domain and URL with your own. SearchConsole.ai reads Search Console data; it does not edit your website, submit sitemaps, or request indexing.

Privacy and support

License

MIT

Source: README.md at commit a0fc016

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestSep 23, 2026
  2. v1.0.0Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts