Google Search Console Connector
Related Servers
Alternatives to Google Search Console Connector
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceGoogle 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.662 npm7MIT
- FlicenseNot gradedqualityCmaintenanceEnables users to query Google Search Console data interactively from Claude Desktop and via CLI, providing search analytics, period comparisons, branded split, indexing status, sitemaps, and full CSV exports.-
- AlicenseNot gradedqualityCmaintenanceEnables Claude, Cursor, VS Code, ChatGPT and other MCP clients to analyze Google Search Console, Google Ads and AdSense data through 57 read-only tools covering search performance, indexing, wasted ad spend, quality scores, earnings and combined paid-vs-organic insights. Runs as a thin local client against a hosted backend, so no Google Cloud project, OAuth client or developer token is needed.129 npmMIT
- 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
- 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 deployable to Cloudflare Workers, allowing natural language queries of GSC data via ChatGPT, Claude, or any MCP-capable client.MIT
TDQS
Scored across 18 tools
Most tools target distinct Search Console setup, verification, reporting, or sitemap tasks, but gsc_search_analytics and gsc_performance_summary partially overlap, and gsc_connect/gsc_link_project both relate to selecting a property. Descriptions largely mitigate the confusion, so boundaries are mostly clear.
All 18 tools use a consistent gsc_ snake_case prefix with predictable verb_noun or noun forms, such as gsc_list_sites, gsc_submit_sitemap, and gsc_get_verification_token. There are no mixed conventions or vague names.
18 tools is on the high side for a connector, but the set is grouped into setup/auth, analytics, verification, sitemaps, and reporting. Each tool maps to a specific operation, making it feature-rich rather than bloated.
The surface covers connection/status, property add/list/link/verify, analytics summary and querying, URL inspection, sitemaps list/submit/delete, report export, annotations, and brand terms. The main gap is property deletion/removal, but core workflows are otherwise covered.