Google Search Console MCP vs Seocrawl MCP
A side-by-side look at the Google Search Console MCP and Seocrawl 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 Google Search Console MCP for marketing work as a local process; choose Seocrawl MCP for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose Seocrawl MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Google Search Console MCP | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 55/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | other | OAuth 2.0 |
| Pricing | Not declared | Paid service |
| Required env vars | GSC_SITE_URLGOOGLE_APPLICATION_CREDENTIALS | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 40 | 2 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Google Search Console MCP | View Seocrawl MCP |
Tools & capabilities
Google Search Console MCP tools
No tool names declared yet. Check the project README from the listing page.
Seocrawl 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.
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"
}
}
}
}
Seocrawl MCP
{
"mcpServers": {
"seocrawl-seocrawl-mcp": {
"url": "https://mcp.seocrawl.ai"
}
}
}
Frequently asked questions
Google Search Console MCP is categorized under Marketing and uses a local stdio subprocess. Seocrawl MCP belongs to Marketing and uses a remote HTTP/SSE transport. Pick Google Search Console MCP for marketing work and Seocrawl 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.
Google Search Console MCP has no declared pricing — check the project's own site. Auth: other. Seocrawl MCP is listed as a paid service. 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 surendranb-google-search-console-mcp and seocrawl-seocrawl-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Search Console MCP has a quality signal of 55/100 (Good) with 1 views, 0 installs and 40 GitHub stars. Seocrawl MCP has 49/100 (Fair) with 4 views, 0 installs and 2 GitHub stars.