MCP Server Docker vs Google Search Console | AllMCPs
Side-by-Side Model Context Protocol Comparison
MCP Server Docker vs Google Search Console
In-depth architectural comparison of the MCP Server Docker and Google Search Console MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MCP Server Docker
Developer Tools · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Google Search Console
Developer Tools · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose MCP Server Docker if you need specialized Developer Tools tools running via a local process. Choose Google Search Console if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Server Docker when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
MCP Server Docker is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Google Search Console belongs to Developer Tools using local stdio subprocess. Select MCP Server Docker when you need capabilities focused on developer tools and Google Search Console when you require tools for developer tools.
List every tool this server exposes and report local Google credential state. `connected` means a stored refresh credential is present; the response also exposes `auth_status_basis` and `provider_auth_live_verified: false` because this discovery call does not probe Google. A later Google tool call…
sites.list
List the Search Console properties the connected Google account can access (`siteUrl`, `permissionLevel`).
sites.get
Retrieve one exact Search Console property and the connected account's permission level for it.
analytics.query
Impressions, clicks, CTR, and average position over a date range, with dimensions, filters, safe pagination, and selectable search type. Pass `dimensions: []` for true site totals; Google's aggregate row may omit `keys`. Search Analytics does not guarantee every data row and can return only top row…
urls.inspect
Google's URL Inspection report for the version of one page currently known in Google's index. It is not a live URL test; mobile-usability output is deprecated.
urls.inspect_many
Inspect Google's indexed versions of up to 10 URLs with bounded concurrency of 3 in one call while preserving input-order results. Each URL still consumes one Google URL Inspection request and one unit of the server's shared inspection safety budget; this does not run live URL tests.
reports.weekly_digest
Generate a plain-language seven-day performance report with movers, top pages, and one recommended action. Query movers compare only rows returned in both weekly Search Analytics result sets; a query missing from one bounded response is not treated as zero because Google does not guarantee every da…
indexing.status
Read Google's latest successful Indexing API `URL_UPDATED` / `URL_DELETED` notification receipts for a previously submitted URL. This is notification metadata only, not index coverage, crawl status, indexing completion, or removal completion. It requires `GSC_ACCESS_MODE=readwrite` because Google's…
indexing.request
Requests indexing through Google's Indexing API. Google currently restricts this API to pages containing `JobPosting` structured data or livestream pages containing `BroadcastEvent` inside `VideoObject`. It is not available for general webpage submission. Google's default 200 publish requests/day/p…