Google Searchconsole MCP vs NexaLink — Digital Business Card & Personal CRM
A side-by-side look at the Google Searchconsole MCP and NexaLink — Digital Business Card & Personal CRM MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
N
NexaLink — Digital Business Card & Personal CRMCustomer Data Platforms · Remote HTTP/SSENexaLink digital business card & personal CRM — edit your card and capture contacts via MCP.37FairAuth: not declaredVerdict: choose Google Searchconsole MCP for customer data platforms work as a local process; choose NexaLink — Digital Business Card & Personal CRM for customer data platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Google Searchconsole MCP when
- You need dedicated capabilities in the Customer Data Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
list_accounts, list_sites, query_search_analytics.
NChoose NexaLink — Digital Business Card & Personal CRM when
- You need dedicated capabilities in the Customer Data Platforms domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | N NexaLink — Digital Business Card & Personal CRM | |
|---|---|---|
| Category | Customer Data Platforms | Customer Data Platforms |
| Quality signal | 61/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 7 | — |
| Directory activity | 5 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 13 | Not listed |
| Full listing | View Google Searchconsole MCP | View NexaLink — Digital Business Card & Personal CRM |
Tools & capabilities
Google Searchconsole MCP tools 13
list_accountsList all authenticated Google accounts and their associated GSC sites.list_sitesList 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_analyticsQuery Google Search Console search analytics data. Returns search queries, clicks, impressions, CTR, and average position.inspect_urlInspect a URL to check its indexing status, mobile usability, and rich results. Shows if Google can crawl and index the page.list_sitemapsList all sitemaps submitted for a site in Google Search Console.find_keyword_opportunitiesFind keyword optimization opportunities - queries with high impressions but low CTR that could be improved.get_top_pagesGet top performing pages sorted by clicks, impressions, CTR, or position.compare_performanceCompare search performance between two time periods. Shows which queries/pages gained or lost traffic.analyze_brand_queriesAnalyze branded vs non-branded search queries. Shows what percentage of traffic comes from brand searches.get_keyword_trendGet the performance trend of a specific keyword over time. Shows daily clicks, impressions, and position changes.export_analyticsExport search analytics data as CSV or JSON format for external analysis or reporting.query_by_search_appearanceQuery analytics filtered by search appearance type (AMP, Rich Results, Video, FAQ, etc.).- +1 more on the listing page
NexaLink — Digital Business Card & Personal CRM tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Google Searchconsole MCP
{
"mcpServers": {
"lionkiii-google-searchconsole-mcp": {
"command": "npx",
"args": [
"-y",
"google-searchconsole-mcp"
]
}
}
}
NexaLink — Digital Business Card & Personal CRM
{
"mcpServers": {
"nexalink-digital-business-card-personal-crm": {
"url": "https://nexalink.co/mcp"
}
}
}
Frequently asked questions
Google Searchconsole MCP is categorized under Customer Data Platforms and uses a local stdio subprocess. NexaLink — Digital Business Card & Personal CRM belongs to Customer Data Platforms and uses a remote HTTP/SSE transport. Pick Google Searchconsole MCP for customer data platforms work and NexaLink — Digital Business Card & Personal CRM for customer data platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Google Searchconsole MCP is listed as free. Auth: oauth 2.0. NexaLink — Digital Business Card & Personal CRM has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add lionkiii-google-searchconsole-mcp and nexalink-digital-business-card-personal-crm as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Searchconsole MCP has a quality signal of 61/100 (Good) with 5 views, 0 installs and 7 GitHub stars. NexaLink — Digital Business Card & Personal CRM has 37/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.