Git vs MCP Search Console
A side-by-side look at the Git 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 Git for other tools and integrations work as a local process; choose MCP Search Console for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Git when
- You need dedicated capabilities in the Other Tools and Integrations 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 MCP Search Console when
- You need dedicated capabilities in the Developer Tools 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Other Tools and Integrations | Developer Tools |
| Quality signal | 89/100 · Excellent | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | GSC_ACCOUNTS_CONFIG |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,289 | 0 |
| Directory activity | 39 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 9 | 17 |
| Full listing | View Git | View MCP Search Console |
Tools & capabilities
Git 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
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
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.
Git
{
"mcpServers": {
"git": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}
}
MCP Search Console
{
"mcpServers": {
"mcp-search-console": {
"command": "uvx",
"args": [
"mcp-search-console-multi"
],
"env": {
"GSC_ACCOUNTS_CONFIG": "YOUR_GSC_ACCOUNTS_CONFIG_HERE"
}
}
}
}
Frequently asked questions
Git is categorized under Other Tools and Integrations and uses a local stdio subprocess. MCP Search Console belongs to Developer Tools and uses a local stdio subprocess. Pick Git for other tools and integrations work and MCP Search Console for developer tools.
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.
Git is listed as free. Auth: no auth required. MCP Search Console has no declared pricing — check the project's own site. 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 git and mcp-search-console as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Git has a quality signal of 89/100 (Excellent) with 39 views, 0 installs and 91,289 GitHub stars. MCP Search Console has 59/100 (Good) with 2 views, 0 installs and 0 GitHub stars.