searchconsole-ai
Google Search Console MCP server (GSC) for SEO analytics in Codex, Claude Code, Cursor, and ChatGPT.
Documentation
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.
npx -y searchconsole-ai@latest setupOr choose a client directly:
npx -y searchconsole-ai@latest setup codex
npx -y searchconsole-ai@latest setup claude
npx -y searchconsole-ai@latest setup cursorGoogle 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:
{
"mcpServers": {
"searchconsole-ai": {
"type": "http",
"url": "https://searchconsole.ai/mcp"
}
}
}Preview changes without applying them:
npx -y searchconsole-ai@latest setup cursor --dry-runConfigure a command-line client without opening OAuth immediately:
npx -y searchconsole-ai@latest setup codex --no-loginThis 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:
https://searchconsole.ai/mcpFull instructions: searchconsole.ai
Public source and release history: github.com/AndreyAzimov/searchconsole-ai
Privacy and support
License
MIT
Frequently asked questions
What is searchconsole-ai?
searchconsole-ai is Google Search Console MCP server (GSC) for SEO analytics in Codex, Claude Code, Cursor, and ChatGPT.
How do I install searchconsole-ai?
Open the GitHub repository and follow its README. Most MCP servers are added to your client's MCP config, then called by your agent.
Is searchconsole-ai open source?
Yes — it is hosted on GitHub at https://github.com/AndreyAzimov/searchconsole-ai.
Related MCP tools
Official remote MCP server for Atlassian. Securely connect Jira, Confluence, Jira Service Management, Bitbucket, and Compass to Claude, ChatGPT, Cursor, VS Code, and other AI tools using OAuth 2.1 or API tokens.
Cut AI token costs 95%+ on code exploration. The leading MCP server for precise, symbol-level GitHub code retrieval via tree-sitter AST. Works with Claude Code, Cursor & any MCP client. 313B+ tokens saved.
Open-source coding agent memory. Records issues, attempts, fixes and decisions, then warns your agent before it repeats an approach that already failed. Native MCP server for Claude Code, Cursor, Antigravity and Codex. 100% local, no cloud, no telemetry. MIT.
Open-source cross-agent memory layer for coding agents via MCP. Compatible with Claude Code, Codex, Cursor, Windsurf, Gemini CLI, Antigravity, OpenClaw, Hermes Agent, Oh-my-Pi, Pi, Copilot, Kiro, OpenCode, and Trae.
AI Skills, MCP Tools, and CLI for Unity Engine. Full AI develop and test loop. Use cli for quick setup. Efficient token usage, advanced tools. Any C# method may be turned into a tool by a single line. Works with Claude Code, Gemini, Copilot, Cursor and any other absolutely for free.
Give your AI agents persistent, collective memory — with deduplicating absorb, supersession lineage, semantic search, and a graph UI. Speaks MCP.
Run your own MCP server? See who uses it and what to fix.
Measure it with TrackMCP