Google Search Console vs Crw
A side-by-side look at the Google Search Console and Crw MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Google Search Console for search & data extraction work as a local process; choose Crw for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Google Search Console when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- You want tools like
gsc_list_sites, gsc_get_site, gsc_health_check.
Choose Crw when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
CRW_API_KEY. - You want tools like
crw_scrape, crw_crawl, crw_check_crawl_status.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 49/100 · Fair | 72/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | CRW_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1,134 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 20 | 8 |
| Full listing | View Google Search Console | View Crw |
Tools & capabilities
Google Search Console tools 20
gsc_list_sitesList all Google Search Console properties accessible with the current credentials.gsc_get_siteGet one Search Console property and its exact permission level (read-only sites.get).gsc_health_checkVerify Google Search Console read-only authentication, visible properties, configured default site, and permission levels without exposing tokens.gsc_query_search_analyticsQuery Google Search Console Search Analytics.gsc_inspect_urlInspect a URL for Google indexing status, crawl info, mobile usability, AMP, and rich results.gsc_bulk_inspect_urlsInspect multiple URLs with a conservative sequential limit and normalized URL Inspection results.gsc_list_sitemapsList sitemaps submitted for a Search Console property, including processing status and submitted/indexed counts.gsc_get_sitemapGet one submitted sitemap by full feed path, including type, fetch state, warnings/errors, and submitted/indexed content totals.gsc_get_sitemap_healthReturn an enriched read-only sitemap health summary with status totals, submitted/indexed content counts, warnings, and errors.gsc_compare_search_typesCompare performance across Search Console search types: web, image, video, news, discover, and Google News.gsc_get_data_freshnessDetect the most recent date with Search Analytics data by querying recent daily rows.gsc_monitor_indexation_freshnessRead-only monitoring snapshot for Search Analytics freshness, sitemap indexation totals, and an optional small URL Inspection sample.- +8 more on the listing page
Crw tools 8
crw_scrapeScrape one URL to markdown, HTML, or links.crw_crawlStart an async site crawl; returns a job id to poll with crw_check_crawl_status.crw_check_crawl_statusPoll an async crawl job and retrieve its pages.crw_mapDiscover URLs on a site via sitemap and/or a short crawl. Returns a URL list only, no page content.crw_extractExtract structured JSON from URLs via a prompt and/or JSON schema. Async job — poll crw_check_extract_status with the returned id. Needs an LLM.crw_check_extract_statusPoll an extract job; returns status and, when complete, a per-URL results array.crw_cancel_extractRequest cancellation of an extract job. Returns the canonical status; cancelling remains non-terminal until the claimed URL settles.crw_parse_fileParse a local PDF (base64 in contentBase64) to markdown. No OCR: scanned PDFs return empty markdown with a warning.
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 Search Console
{
"mcpServers": {
"google-search-console-7": {
"command": "npx",
"args": [
"-y",
"@getmcpads/google-search-console-mcp-server"
]
}
}
}
Crw
{
"mcpServers": {
"us-crw": {
"command": "npx",
"args": [
"-y",
"crw-mcp@latest"
],
"env": {
"CRW_API_KEY": "YOUR_CRW_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Google Search Console is categorized under Search & Data Extraction and uses a local stdio subprocess. Crw belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Google Search Console for search & data extraction work and Crw for search & data extraction.
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 Search Console has no declared pricing — check the project's own site. Crw is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. 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 google-search-console-7 and us-crw as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Search Console has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Crw has 72/100 (Great) with 4 views, 0 installs and 1,134 GitHub stars.