Fetch vs Google Search Console
A side-by-side look at the Fetch and Google Search Console MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Fetch for search & data extraction work as a local process; choose Google Search Console 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 Fetch when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
create_entities, create_relations, add_observations.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 90/100 · Excellent | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,308 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 9 | 20 |
| Full listing | View Fetch | View Google Search Console |
Tools & capabilities
Fetch tools 9
create_entitiesCreate multiple new entities in the knowledge graphcreate_relationsCreate multiple new relations between entities in the knowledge graph. Relations should be in active voiceadd_observationsAdd new observations to existing entities in the knowledge graphdelete_entitiesDelete multiple entities and their associated relations from the knowledge graphdelete_observationsDelete specific observations from entities in the knowledge graphdelete_relationsDelete multiple relations from the knowledge graphread_graphRead the entire knowledge graphsearch_nodesSearch for nodes in the knowledge graph based on a queryopen_nodesOpen specific nodes in the knowledge graph by their names
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
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.
Fetch
{
"mcpServers": {
"fetch": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}
}
Google Search Console
{
"mcpServers": {
"google-search-console-7": {
"command": "npx",
"args": [
"-y",
"@getmcpads/google-search-console-mcp-server"
]
}
}
}
Frequently asked questions
Fetch is categorized under Search & Data Extraction and uses a local stdio subprocess. Google Search Console belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Fetch for search & data extraction work and Google Search Console 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.
Fetch is listed as free. Auth: no auth required. Google Search Console 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 fetch and google-search-console-7 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Fetch has a quality signal of 90/100 (Excellent) with 4 views, 0 installs and 91,308 GitHub stars. Google Search Console has 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.