In-depth architectural comparison of the Яндекс.Директ and Google Tag Manager MCP Server 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
Яндекс.Директ
Marketing · Local stdio
Quality: 44/100 (Fair) | Auth: No auth required
Google Tag Manager MCP Server
Marketing · Local stdio
Quality: 60/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose Яндекс.Директ if you need specialized Marketing tools running via a local process. Choose Google Tag Manager MCP Server 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 Яндекс.Директ when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Яндекс.Директ is categorized under Marketing and uses a local stdio subprocess. In contrast, Google Tag Manager MCP Server belongs to Marketing using local stdio subprocess. Select Яндекс.Директ when you need capabilities focused on marketing and Google Tag Manager MCP Server when you require tools for marketing.