Seo Stack MCP vs Google Search Console MCP
A side-by-side look at the Seo Stack MCP 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 Seo Stack MCP 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 Seo Stack MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GOOGLE_APPLICATION_CREDENTIALS, SEO_STACK_OAUTH_CLIENT, GA4_PROPERTY_ID, GSC_SITE_URL, BING_WEBMASTER_API_KEY, BING_SITE_URL, CLARITY_API_TOKEN, ADSENSE_ACCOUNT_ID. - You want tools like
gsc_bulk_inspect_urls, gsc_bulk_request_indexing, gsc_cannibalization_check.
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 | 48/100 · Fair | 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 | GOOGLE_APPLICATION_CREDENTIALSSEO_STACK_OAUTH_CLIENTGA4_PROPERTY_IDGSC_SITE_URLBING_WEBMASTER_API_KEYBING_SITE_URLCLARITY_API_TOKENADSENSE_ACCOUNT_ID | GSC_SITE_URLGOOGLE_APPLICATION_CREDENTIALS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 40 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 80 | Not listed |
| Full listing | View Seo Stack MCP | View Google Search Console MCP |
Tools & capabilities
Seo Stack MCP tools 80
gsc_bulk_inspect_urlsInspect multiple URLs in batch via the URL Inspection API. Max 50 URLs per call.gsc_bulk_request_indexingRequest indexing for multiple URLs via the Google Indexing API. Max 50 URLs.gsc_cannibalization_checkFind queries where multiple pages compete (keyword cannibalization). Shows queries with 2+ ranking pages.gsc_compare_periodsCompare two periods: shows deltas of clicks, impressions, CTR and position per item.gsc_content_gap_analysisContent gap analysis: queries where the competitor ranks but you don't (or you are far behind).gsc_country_performancePerformance by country: clicks, impressions, CTR and average position. Default: last 28 days.gsc_daily_statsAggregated daily site statistics: clicks, impressions, CTR and average position per day.gsc_declining_queriesQueries losing clicks/positions: compares last N days vs the equivalent previous period.gsc_delete_sitemapRemove a sitemap from Google Search Console. Requires write scope on the credentials.gsc_device_performanceCompare performance across MOBILE vs DESKTOP vs TABLET. Default: last 28 days.gsc_indexing_status_summaryIndexing status summary for multiple URLs: how many indexed, not indexed, and errored.gsc_inspect_urlInspect a URL via the Google Search Console URL Inspection API.- +68 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.
Seo Stack MCP
{
"mcpServers": {
"seo-stack-mcp": {
"command": "uvx",
"args": [
"--with",
"google-ads",
"seo-stack-mcp"
],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "YOUR_GOOGLE_APPLICATION_CREDENTIALS_HERE",
"SEO_STACK_OAUTH_CLIENT": "YOUR_SEO_STACK_OAUTH_CLIENT_HERE",
"GA4_PROPERTY_ID": "YOUR_GA4_PROPERTY_ID_HERE",
"GSC_SITE_URL": "YOUR_GSC_SITE_URL_HERE",
"BING_WEBMASTER_API_KEY": "YOUR_BING_WEBMASTER_API_KEY_HERE",
"BING_SITE_URL": "YOUR_BING_SITE_URL_HERE",
"CLARITY_API_TOKEN": "YOUR_CLARITY_API_TOKEN_HERE",
"ADSENSE_ACCOUNT_ID": "YOUR_ADSENSE_ACCOUNT_ID_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
Seo Stack MCP is categorized under Marketing and uses a local stdio subprocess. Google Search Console MCP belongs to Marketing and uses a local stdio subprocess. Pick Seo Stack MCP 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.
Seo Stack MCP 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 seo-stack-mcp 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, Seo Stack MCP has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. Google Search Console MCP has 55/100 (Good) with 0 views, 0 installs and 40 GitHub stars.