Google Tag Manager MCP Server vs Yandex Direct MCP
A side-by-side look at the Google Tag Manager MCP Server and Yandex Direct MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Google Tag Manager MCP Server for marketing work as a local process; choose Yandex Direct MCP for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Google Tag Manager MCP Server when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
GOOGLE_SERVICE_ACCOUNT_KEY.
Choose Yandex Direct MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
YANDEX_DIRECT_TOKEN, YANDEX_DIRECT_SANDBOX, YANDEX_DIRECT_LOGIN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 61/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Free | Not declared |
| Required env vars | GOOGLE_SERVICE_ACCOUNT_KEY | YANDEX_DIRECT_TOKENYANDEX_DIRECT_SANDBOXYANDEX_DIRECT_LOGIN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 227 | 5 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Google Tag Manager MCP Server | View Yandex Direct MCP |
Tools & capabilities
Google Tag Manager MCP Server tools
No tool names declared yet. Check the project README from the listing page.
Yandex Direct MCP tools
No tool names declared yet. Check the project README from 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.
Google Tag Manager MCP Server
{
"mcpServers": {
"stape-io-google-tag-manager-mcp-server": {
"command": "npx",
"args": [
"-y",
"google-tag-manager-mcp-server"
],
"env": {
"GOOGLE_SERVICE_ACCOUNT_KEY": "YOUR_GOOGLE_SERVICE_ACCOUNT_KEY_HERE"
}
}
}
}
Yandex Direct MCP
{
"mcpServers": {
"yandex-direct-mcp-2": {
"command": "npx",
"args": [
"-y",
"@theyahia/yandex-direct-mcp"
],
"env": {
"YANDEX_DIRECT_TOKEN": "YOUR_YANDEX_DIRECT_TOKEN_HERE",
"YANDEX_DIRECT_SANDBOX": "YOUR_YANDEX_DIRECT_SANDBOX_HERE",
"YANDEX_DIRECT_LOGIN": "YOUR_YANDEX_DIRECT_LOGIN_HERE"
}
}
}
}
Frequently asked questions
Google Tag Manager MCP Server is categorized under Marketing and uses a local stdio subprocess. Yandex Direct MCP belongs to Marketing and uses a local stdio subprocess. Pick Google Tag Manager MCP Server for marketing work and Yandex Direct MCP for marketing.
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.
Google Tag Manager MCP Server is listed as free. Auth: oauth 2.0. Yandex Direct MCP 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 stape-io-google-tag-manager-mcp-server and yandex-direct-mcp-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Tag Manager MCP Server has a quality signal of 61/100 (Good) with 4 views, 0 installs and 227 GitHub stars. Yandex Direct MCP has 43/100 (Fair) with 0 views, 0 installs and 5 GitHub stars.