B2b Enrichment MCP vs Google Searchconsole… | AllMCPs
Side-by-Side Model Context Protocol Comparison
B2b Enrichment MCP vs Google Searchconsole MCP
In-depth architectural comparison of the B2b Enrichment MCP and Google Searchconsole 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
B2b Enrichment MCP
Customer Data Platforms · Local stdio
Quality: 48/100 (Fair) | Auth: API Key required
Google Searchconsole MCP
Customer Data Platforms · Local stdio
Quality: 63/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose B2b Enrichment MCP if you need specialized Customer Data Platforms tools running via a local process. Choose Google Searchconsole MCP 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 B2b Enrichment MCP when:
You need dedicated capabilities in the Customer Data Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: HUNTER_API_KEY, APOLLO_API_KEY.
B2B lead enrichment server integrating Hunter.io and Apollo APIs. 9 tools for email discovery, domain search, company data, and contact verification.
Google Search Console MCP server with 13 SEO tools — search analytics, URL inspection, sitemap management, keyword opportunities, brand analysis, and performance comparison.
Category & Scope
Tools & Capabilities Breakdown
B2b Enrichment MCP Tools (9)
hunter_find_emails_by_domain
hunter_find_email
hunter_verify_email
hunter_count_emails
hunter_check_account
enrich_company
enrich_person_by_email
bulk_enrich_people
enrich_person
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).
B2b Enrichment MCP is categorized under Customer Data Platforms and uses a local stdio subprocess. In contrast, Google Searchconsole MCP belongs to Customer Data Platforms using local stdio subprocess. Select B2b Enrichment MCP when you need capabilities focused on customer data platforms and Google Searchconsole MCP when you require tools for customer data platforms.
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.
find_keyword_opportunities
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.).