modelbrain-search-console
OfficialRelated Servers
Alternatives to modelbrain-search-console
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceGoogle Search Console for Claude, Cursor & any MCP client — one sign-in, 30 seconds, no Google Cloud project. Six read-only tools (search analytics incl. Google Discover, period comparison with computed deltas, batch URL inspection, sitemaps) plus five built-in SEO analyses as slash-commands. Tokens stay on your machine. MIT.6370 npm8MIT
- AlicenseAqualityBmaintenanceGoogle Search Console for Claude and other MCP clients. Sign in with Google in one click, then ask about clicks, queries, rankings and indexing, export every GSC report as CSV (beyond the 1,000-row UI limit), inspect URLs, submit sitemaps and verify sites. Includes a local SEO dashboard. Free, open source, runs on your computer.18100 npm2MIT
- AlicenseBqualityDmaintenanceProfessional Google Search Console MCP server providing 40+ SEO tools for performance analysis, content decay, CTR opportunities, and more, enabling real search data in clients like Cursor and Claude.4021 npm6MIT
- AlicenseBqualityCmaintenanceA production-oriented, read-only Google Search Console MCP server and TypeScript SDK for Claude, Cursor, VS Code, and other MCP clients. Query real Search Console data, inspect indexed URLs, review sitemaps, compare periods, and surface transparent SEO opportunities without handing private data to a third-party SaaS.20MIT
- AlicenseNot gradedqualityCmaintenanceSelf-hosted Google Search Console MCP server that lets ChatGPT, Claude, or other MCP clients query GSC data in natural language. It exposes tools to list sites, query Search Analytics, inspect URLs, and list sitemaps.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceConnects AI assistants to Google Search Console through MCP so users can query search performance, inspect URLs and indexing status, compare periods, and manage sitemaps from Claude, Cursor, or other MCP clients. Runs as a remote Cloudflare Worker with API-key authentication and optional write tools.MIT
TDQS
Scored across 5 tools
Each tool targets a clearly distinct resource or operation: property enumeration (list_sites), per-URL status (inspect_url), sitemap listing (list_sitemaps), raw performance querying (search_performance), and period-over-period comparison (compare_periods). The only mild adjacency is search_performance vs compare_periods, but one is a granular grouped query and the other a fixed two-period diff with gain/loss highlights, so boundaries are clear.
All five names follow a consistent snake_case verb_noun convention (inspect_url, list_sitemaps, list_sites, search_performance, compare_periods). Verbs are distinct and meaningfully matched to each action.
Five tools is well-scoped for a focused Search Console surface, covering properties, sitemaps, URL inspection, analytics, and comparison without redundancy. Each tool earns its place.
Core read workflows (properties, sitemaps, URL inspection, search analytics, period comparison) are well covered. However, the surface is entirely read-only: there is no way to submit or delete a sitemap or request reindexing, which are natural Search Console operations and could cause dead ends.