Google Searchconsole… vs MCP Icp Fit Scorer | AllMCPs
Side-by-Side Model Context Protocol Comparison
Google Searchconsole MCP vs MCP Icp Fit Scorer
In-depth architectural comparison of the Google Searchconsole MCP and MCP Icp Fit Scorer 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 Searchconsole MCP
Customer Data Platforms · Local stdio
Quality: 63/100 (Good) | Auth: OAuth 2.0
MCP Icp Fit Scorer
Customer Data Platforms · Local stdio
Quality: 59/100 (Good) | Auth: API Key required
Verdict Summary: Choose Google Searchconsole MCP if you need specialized Customer Data Platforms tools running via a local process. Choose MCP Icp Fit Scorer if your workspace requires Customer Data Platforms 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 Searchconsole MCP when:
You need dedicated capabilities in the Customer Data Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
Google Search Console MCP server with 13 SEO tools — search analytics, URL inspection, sitemap management, keyword opportunities, brand analysis, and performance comparison.
Scores a company against a weighted ideal customer profile, returning a 0-100 score, A/B/C tier, and per-signal breakdown.
Category & Scope
Tools & Capabilities Breakdown
Google Searchconsole MCP Tools (13)
list_accounts
List all authenticated Google accounts and their associated GSC sites.
list_sites
List all sites you have access to in Google Search Console. When multiple accounts exist and no account is specified, shows all accounts' sites grouped by account.
query_search_analytics
Query Google Search Console search analytics data. Returns search queries, clicks, impressions, CTR, and average position.
inspect_url
Inspect a URL to check its indexing status, mobile usability, and rich results. Shows if Google can crawl and index the page.
list_sitemaps
List all sitemaps submitted for a site in Google Search Console.
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 Searchconsole MCP is categorized under Customer Data Platforms and uses a local stdio subprocess. In contrast, MCP Icp Fit Scorer belongs to Customer Data Platforms using local stdio subprocess. Select Google Searchconsole MCP when you need capabilities focused on customer data platforms and MCP Icp Fit Scorer when you require tools for customer data platforms.
Find keyword optimization opportunities - queries with high impressions but low CTR that could be improved.
get_top_pages
Get top performing pages sorted by clicks, impressions, CTR, or position.
compare_performance
Compare search performance between two time periods. Shows which queries/pages gained or lost traffic.
analyze_brand_queries
Analyze branded vs non-branded search queries. Shows what percentage of traffic comes from brand searches.
get_keyword_trend
Get the performance trend of a specific keyword over time. Shows daily clicks, impressions, and position changes.
export_analytics
Export search analytics data as CSV or JSON format for external analysis or reporting.
query_by_search_appearance
Query analytics filtered by search appearance type (AMP, Rich Results, Video, FAQ, etc.).
+1 more tools listed on main page
MCP Icp Fit Scorer Tools (1)
score_icp_fit
Score a company against your ideal customer profile (ICP) using weighted signals. Returns a 0 to 100 icp_score, an A to D icp_tier, and a per-signal breakdown as a flat, Clay-ready JSON row. Define your ICP with a prebuilt template, a JSON scoring_config, or a plain-English icp_description (which requires llm_api_key). Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.