Fetch vs Gsc MCP
A side-by-side look at the Fetch and Gsc MCP 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 Gsc MCP 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 Gsc MCP 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:
GSC_CLIENT_ID, GSC_CLIENT_SECRET, GSC_REFRESH_TOKEN, GSC_SERVICE_ACCOUNT_KEY_PATH. - You want tools like
sites_list, sites_get, sites_add.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 86/100 · Excellent | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | OAuth 2.0 |
| Pricing | Free | Free |
| Required env vars | None listed | GSC_CLIENT_IDGSC_CLIENT_SECRETGSC_REFRESH_TOKEN |
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
Gsc MCP tools 13
sites_listList all sites (properties) you have access to in Google Search Console.sites_getRetrieve information about a specific site (property) in Google Search Console.sites_addAdd a site (property) to Google Search Console. Verification may still be required.sites_deleteRemove a site (property) from Google Search Console.sitemaps_listList all sitemaps submitted for a site in Google Search Console.sitemaps_getRetrieve information about a specific sitemap.
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"
]
}
}
}
Gsc MCP
{
"mcpServers": {
"mikusnuz-gsc-mcp": {
"command": "npx",
"args": [
"-y",
"@mikusnuz/gsc-mcp"
],
"env": {
"GSC_CLIENT_ID": "YOUR_GSC_CLIENT_ID_HERE",
"GSC_CLIENT_SECRET": "YOUR_GSC_CLIENT_SECRET_HERE",
"GSC_REFRESH_TOKEN": "YOUR_GSC_REFRESH_TOKEN_HERE",
"GSC_SERVICE_ACCOUNT_KEY_PATH": "YOUR_GSC_SERVICE_ACCOUNT_KEY_PATH_HERE"
}
}
}
}
Frequently asked questions
Fetch is categorized under Search & Data Extraction and uses a local stdio subprocess. Gsc MCP belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Fetch for search & data extraction work and Gsc MCP 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. Gsc MCP is listed as free. 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 fetch and mikusnuz-gsc-mcp 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 86/100 (Excellent) with 4 views, 0 installs and 91,147 GitHub stars. Gsc MCP has 63/100 (Good) with 1 views, 0 installs and 7 GitHub stars.