MCP Search Console vs Google Search Console MCP
A side-by-side look at the MCP Search Console and Google Search Console MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Google Search Console MCPMarketing · Local subprocess (stdio)Model Context Protocol (MCP) server for Google Search Console (GSC) inspection, search performance, and sitemaps via NPX. Spawns the Python package through uvx with full stdio passthrough.55GoodAuth: otherVerdict: choose MCP Search Console for marketing work as a local process; choose Google Search Console MCP for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Search Console when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GSC_ACCOUNTS_CONFIG. - You want tools like
list_accounts, set_default_account, reauthenticate.
Choose Google Search Console MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
GSC_SITE_URL, GOOGLE_APPLICATION_CREDENTIALS.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Google Search Console MCP | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 59/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Not declared |
| Required env vars | GSC_ACCOUNTS_CONFIG | GSC_SITE_URLGOOGLE_APPLICATION_CREDENTIALS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 40 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 17 | Not listed |
| Full listing | View MCP Search Console | View Google Search Console MCP |
Tools & capabilities
MCP Search Console tools 17
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).- +5 more on the listing page
Google Search Console MCP 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.
MCP Search Console
{
"mcpServers": {
"mcp-search-console": {
"command": "uvx",
"args": [
"mcp-search-console-multi"
],
"env": {
"GSC_ACCOUNTS_CONFIG": "YOUR_GSC_ACCOUNTS_CONFIG_HERE"
}
}
}
}
Google Search Console MCP
{
"mcpServers": {
"surendranb-google-search-console-mcp": {
"command": "uvx",
"args": [
"google-search-console-mcp"
],
"env": {
"GSC_SITE_URL": "YOUR_GSC_SITE_URL_HERE",
"GOOGLE_APPLICATION_CREDENTIALS": "YOUR_GOOGLE_APPLICATION_CREDENTIALS_HERE"
}
}
}
}
Frequently asked questions
MCP Search Console is categorized under Marketing and uses a local stdio subprocess. Google Search Console MCP belongs to Marketing and uses a local stdio subprocess. Pick MCP Search Console for marketing work and Google Search Console MCP for marketing.
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.
MCP Search Console has no declared pricing — check the project's own site. Google Search Console MCP has no declared pricing — check the project's own site. Auth: other. 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 mcp-search-console and surendranb-google-search-console-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Search Console has a quality signal of 59/100 (Good) with 3 views, 0 installs and 0 GitHub stars. Google Search Console MCP has 55/100 (Good) with 0 views, 0 installs and 40 GitHub stars.