A side-by-side look at the Google Webtools MCP and MCP 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 Google Webtools MCP for developer tools work; choose MCP Search Console for developer tools as a local process. You can also run both side by side in one mcpServers block.
GOOGLE_APPLICATION_CREDENTIALS.list_properties, get_property_details, add_property.GSC_ACCOUNTS_CONFIG.list_accounts, set_default_account, reauthenticate.Rows where the two servers differ are marked.
| Spec | G Google Webtools MCP | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 51/100 · Good | 56/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | GOOGLE_APPLICATION_CREDENTIALS | GSC_ACCOUNTS_CONFIG |
| Verified owner | Community listing | Community listing |
| GitHub stars | 7 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 39 | 17 |
| Full listing | View Google Webtools MCP | View MCP Search Console |
list_propertiesStarting point — see every GSC property you can access and your permission level on each.get_property_detailsCheck the type and permission level of one specific property.add_propertyRegister a new site in Search Console (verification is a separate step).delete_propertyDrop a property from the authenticated account's Search Console site list. Historical data is not destroyed — the property can be added back.list_sitemapsSee which sitemaps are submitted and whether Google reports errors or warnings.get_sitemap_detailsDrill into one sitemap: URL counts by content type, last download time, error and warning counts.submit_sitemapSubmit a new sitemap after publishing or moving one.delete_sitemapWithdraw a sitemap that is stale, duplicated, or returning errors.get_search_analyticsThe raw query — full control over dimensions, filters, search type, row limit, data state, aggregation. Use when the shaped tools below don't fit.get_performance_summary"How are we doing?" — clicks, impressions, CTR, position with period-over-period comparison. Trend advice is withheld when the previous period returned no data at all.compare_periodsCompare two explicit date ranges side by side (before/after a release, seasonal comparison).get_top_queriesTop queries by clicks, each scored against the CTR benchmark for its position.list_accountsList all configured GSC accounts and which is the current default.set_default_accountSet the default account used when no account is specified in other tools.reauthenticateForce re-authentication for an account. Clears the cached token and re-runs
the OAuth flow (or reloads service account credentials). Useful when a token
has been revoked or you need to switch Google accounts.list_propertiesList all Google Search Console properties for the specified account.get_site_detailsGet verification and permission details for a specific GSC property.get_search_analyticsFetch search analytics data (clicks, impressions, CTR, position).get_performance_overviewGet a high-level performance summary: total clicks, impressions, CTR, average position.
No dimension breakdown — use get_search_analytics for that.compare_periodsCompare search performance between two date ranges.
Returns rows for both periods side-by-side with delta calculations.get_advanced_search_analyticsAdvanced search analytics with dimension filters.
filters format: [{"dimension": "country", "operator": "equals", "expression": "usa"}]
operators: equals, notEquals, contains, notContains, includingRegex, excludingRegexget_search_by_pageGet search queries driving traffic to a specific page URL.inspect_urlInspect a URL's indexing status, last crawl date, mobile usability,
and rich result eligibility.batch_inspect_urlsInspect multiple URLs at once. Returns one result per URL.
Maximum 10 URLs per call (GSC API limit).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.
No confirmed install command for Google Webtools MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"mcp-search-console": {
"command": "uvx",
"args": [
"mcp-search-console-multi"
],
"env": {
"GSC_ACCOUNTS_CONFIG": "YOUR_GSC_ACCOUNTS_CONFIG_HERE"
}
}
}
}