mcp-gsc and search-console-mcp
These are competitors offering overlapping SEO data integration—both expose Google Search Console data to Claude/AI agents, though B extends further with Bing Webmaster Tools and GA4 support while A focuses exclusively on GSC insights.
About mcp-gsc
AminForou/mcp-gsc
Google Search Console Insights with Claude AI for SEOs
Implements the Model Context Protocol (MCP) standard to expose Google Search Console data as tools callable by AI assistants, supporting OAuth and service account authentication for flexible credential management. Provides 19 specialized tools covering property management, search analytics with configurable row limits up to 500, URL inspection, and sitemap operations—all accessible through natural language queries in Claude, Cursor, Gemini CLI, and other MCP-compatible clients. Generates data visualizations and multi-dimension filtering capabilities to help SEO professionals analyze trends and identify indexing issues programmatically.
About search-console-mcp
saurabhsharma2u/search-console-mcp
Search & analytics data as infrastructure — MCP server for Google Search Console, Bing Webmaster Tools, and GA4, designed for AI agents and automation.
Provides deterministic SEO intelligence through built-in analysis tools (cannibalization detection, Z-score anomalies, opportunity scoring) that transform raw analytics into actionable insights for AI agents, eliminating the need for manual data correlation across platforms. Implements multi-layered security with OS-native keychain storage, AES-256-GCM hardware-bound encryption, and automatic token refresh, while supporting both interactive OAuth and service account authentication for flexible deployment scenarios. Exposes cross-platform data through a unified MCP interface with automatic multi-account credential resolution, enabling agents to query unified GSC + Bing + GA4 context without manual site-to-account mapping.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work