Yandex Metrika MCP vs Yandex Metrika MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
Yandex Metrika MCP vs Yandex Metrika MCP
In-depth architectural comparison of the Yandex Metrika MCP and Yandex Metrika MCP 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
Yandex Metrika MCP
Marketing · Remote HTTP/SSE
Quality: 47/100 (Fair) | Auth: No auth required
Yandex Metrika MCP
Marketing · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Yandex Metrika MCP if you need specialized Marketing tools running via a hosted cloud SSE transport. Choose Yandex Metrika MCP if your workspace requires Marketing integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Yandex Metrika MCP when:
You need dedicated capabilities in the Marketing domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: YANDEX_METRIKA_TOKEN.
Yandex Metrika MCP is categorized under Marketing and uses a remote streaming HTTP/SSE transport. In contrast, Yandex Metrika MCP belongs to Marketing using local stdio subprocess. Select Yandex Metrika MCP when you need capabilities focused on marketing and Yandex Metrika MCP when you require tools for marketing.