In-depth architectural comparison of the Appmetrica MCP and MCP 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
Appmetrica MCP
Developer Tools · Local stdio
Quality: 59/100 (Good) | Auth: OAuth 2.0
MCP Search Console
Developer Tools · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose Appmetrica MCP if you need specialized Developer Tools tools running via a local process. Choose MCP 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?
A
Choose Appmetrica MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
Appmetrica MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, MCP Search Console belongs to Developer Tools using local stdio subprocess. Select Appmetrica MCP when you need capabilities focused on developer tools and MCP Search Console when you require tools for developer tools.
The same as a time series (`group`: day / week / month / hour / all). One namespace prefix per call
get_drilldown
Drill down into a dimension value for detailed breakdown
list_metrics
Metric/dimension catalogue (197 metrics, 188 dimensions): compact overview, or `search` / `namespace` / `kind` / `limit` for entries
audit_events
Event instrumentation audit for a period: registered vs active vs zero-volume events, optional `expected_events`, plain-language findings (read-only)
list_segments
List saved segments (id, name, expression)
get_segment
Get one segment with all fields
+33 more tools listed on main page
MCP Search Console Tools (17)
list_accounts
List all configured GSC accounts and which is the current default.
set_default_account
Set the default account used when no account is specified in other tools.
reauthenticate
Force 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_properties
List all Google Search Console properties for the specified account.
get_site_details
Get verification and permission details for a specific GSC property.
get_search_analytics
Fetch search analytics data (clicks, impressions, CTR, position).
get_performance_overview
Get a high-level performance summary: total clicks, impressions, CTR, average position.
No dimension breakdown — use get_search_analytics for that.
compare_periods
Compare search performance between two date ranges.
Returns rows for both periods side-by-side with delta calculations.