Google Search Console… vs Seo Performance Mcp | AllMCPs
Side-by-Side Model Context Protocol Comparison
Google Search Console Mcp vs Seo Performance Mcp
In-depth architectural comparison of the Google Search Console Mcp and Seo Performance Mcp MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Google Search Console Mcp
Marketing · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
Seo Performance Mcp
Marketing · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Google Search Console Mcp if you need specialized Marketing tools running via a local process. Choose Seo Performance Mcp if your workspace requires Marketing integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Google Search Console Mcp when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Read-only OAuth access with webmasters.readonly scope, Eight tools covering sites, performance, indexing, URL inspection, and sitemaps, One-call HTML SEO audit report generator with branding customization.
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Aggregates data from Google Search Console, Matomo/GA4, Microsoft Clarity, and AI citation sources, Emits per-URL verdicts with reason codes and confidence scores, Supports multiple content discovery methods including sitemap, Ghost API, and HTML extraction.
Google Search Console MCP server: query performance data, inspect URLs, check indexing, and generate brandable HTML SEO audit reports with a 30/60/90-day roadmap. Read-only OAuth scope, installable via uvx mcp-google-search-console.
Post-publish SEO performance MCP that unifies Google Search Console, Matomo, GA4, Clarity, and AI-citation signals per URL and emits a verdict (refresh / expand / merge / kill / doubledown / hold) per post with reason codes.
Category & Scope
Tools & Capabilities Breakdown
Google Search Console Mcp Tools (6)
Read-only OAuth access with webmasters.readonly scope
Eight tools covering sites, performance, indexing, URL inspection, and sitemaps
One-call HTML SEO audit report generator with branding customization
Stateless credential management via environment variables or config files
Zero setup with uvx or pipx for easy installation and execution
Compatible with any MCP client including Claude Code, Cursor, and others
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Google Search Console Mcp is categorized under Marketing and uses a local stdio subprocess. In contrast, Seo Performance Mcp belongs to Marketing using local stdio subprocess. Select Google Search Console Mcp when you need capabilities focused on marketing and Seo Performance Mcp when you require tools for marketing.