Google Search Console… vs Recao — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Google Search Console MCP vs Recao
In-depth architectural comparison of the Google Search Console MCP and Recao 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: 61/100 (Good) | Auth: OAuth 2.0
Recao
Marketing · Remote HTTP/SSE
Quality: 48/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 Recao if your workspace requires Marketing integration with remote web transport. 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: OAuth 2.0 (Free / Open Source).
You have access to required keys: GSC_CLIENT_ID, GSC_CLIENT_SECRET, GSC_REFRESH_TOKEN.
Google Search Console MCP is categorized under Marketing and uses a local stdio subprocess. In contrast, Recao belongs to Marketing using remote streaming HTTP/SSE transport. Select Google Search Console MCP when you need capabilities focused on marketing and Recao when you require tools for marketing.
Queries where several pages compete against each other
gsc_traffic_drops
Pages that lost clicks, with a likely cause for each
gsc_content_decay
Pages sliding down month after month
gsc_alerts
What moved sharply enough to be worth a message today
gsc_portfolio
Every property at a glance, worst first
+5 more tools listed on main page
Recao Tools (4)
search_app_advertiser
Find an app or developer in Apple's Ad Repository by name. Returns the ids the other tools take. Start here.
get_competitor_ads
Pull every App Store ad an advertiser ran in the EU (up to 1 year back), sorted by how long each has been live. An ad the advertiser keeps paying for is the closest public signal that it converts.
get_ad_details
Full detail for one ad: every locale variant, creative asset URLs, icon variations, placements, and date range. Shows how a competitor localizes a winning ad.
get_playbook
An Apple Search Ads playbook for indie apps, wired to the data tools. Call with no argument to list the available playbooks.
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.
Rank a competitor's EU App Store ads by longevity. From Apple's official Ad Repository.