Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://searchconsole.ai/mcpThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http ai.searchconsole-searchconsole-ai https://searchconsole.ai/mcpRun in a terminal.
{ "mcpServers": { "ai.searchconsole-searchconsole-ai": { "command": "npx", "args": [ "-y", "mcp-remote", "https://searchconsole.ai/mcp" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
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.
npx -y searchconsole-ai@latest setup
Read-only Search Console analytics, URL inspection, indexing diagnostics, and sitemaps.
Or choose a client directly:
npx -y searchconsole-ai@latest setup codex
npx -y searchconsole-ai@latest setup claude
npx -y searchconsole-ai@latest setup cursor
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:
{
"mcpServers": {
"searchconsole-ai": {
"type": "http",
"url": "https://searchconsole.ai/mcp"
}
}
}
Preview changes without applying them:
npx -y searchconsole-ai@latest setup cursor --dry-run
Configure a command-line client without opening OAuth immediately:
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.
Add a remote Streamable HTTP MCP server named searchconsole-ai with this URL:
https://searchconsole.ai/mcp
Full instructions: searchconsole.ai
Public source and release history: github.com/AndreyAzimov/searchconsole-ai
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:
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.
MIT
© 2026 MCP Directory.
Read-only Search Console analytics, URL inspection, indexing diagnostics, and sitemaps.
{ "mcpServers": { "ai.searchconsole-searchconsole-ai": { "url": "https://searchconsole.ai/mcp", "headers": {} } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
SearchConsole.ai is reached over HTTP.
Last checked 2026-11-07. Read-only Search Console analytics, URL inspection, indexing diagnostics, and sitemaps.