Side-by-Side Model Context Protocol Comparison
PlainRouter vs Yandex Direct MCP
In-depth architectural comparison of the PlainRouter and Yandex Direct 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
PlainRouter
Marketing · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Yandex Direct MCP
Marketing · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Verdict Summary: Choose PlainRouter if you need specialized Marketing tools running via a local process. Choose Yandex Direct 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?
P
Choose PlainRouter 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).
- You have access to required keys:
PLAINROUTER_WORKSPACE_TOKEN. - Primary tools included: get_account_state, get_account_inventory, get_inventory_metrics.
Choose Yandex Direct MCP 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).
- You have access to required keys:
YANDEX_DIRECT_TOKEN, YANDEX_DIRECT_SANDBOX, YANDEX_DIRECT_LOGIN. - Primary tools included: 20 Yandex.Direct management tools, Campaign and ad group lifecycle controls, Keyword, bid, and negative phrase management.
Feature & Specification Comparison
Tools & Capabilities Breakdown
PlainRouter Tools (34)
get_account_state
Return the authorized advertising account, workspace, connection, Signal destination, and currently available account capabilities.
get_account_inventory
Read the authorized workspace account inventory from the Meta mirror, with optional level, status, parent, and ID cursor filters.
get_inventory_metrics
Read daily Meta metrics beside counted Plainrouter arrivals for mirrored campaigns, ad sets and ads.
get_performance
Compare Meta-reported conversions with the conversions Plainrouter accepted and verified for the selected account.
get_arrivals_comparison
Return counted arrivals beside Meta outbound clicks for the authorized workspace and selected trailing window.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
PlainRouter Configuration
Yandex Direct MCP Configuration