yandex-direct-mcp
Related Servers
Alternatives to yandex-direct-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables managing Yandex.Direct contextual advertising campaigns directly from an MCP client chat, covering campaigns, ad groups, ads and moderation, keywords and bids, negative keywords, bid adjustments, retargeting, feeds, statistics, search queries, and account balance. All monetary values are handled in rubles and 64-bit IDs are kept as strings to avoid precision loss.5955 npm1MIT
- AlicenseAqualityBmaintenanceEnables safe, informed management of Yandex.Direct accounts through 11 MCP tools, covering reads, planned two-phase writes, reports, media attachment, Wordstat, Metrika, and Audience operations, while exposing platform knowledge as resources such as limits, traps, and the red line of deliberately absent destructive actions.11MIT
- AlicenseBqualityAmaintenanceEnables managing Yandex Direct PPC campaigns, ad groups, ads, and keywords, plus pulling performance statistics via the Yandex Direct API v5.44124 npm2MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to manage Yandex Direct advertising campaigns, ads, keywords, and reports via natural language using the Yandex Direct API v5.21MIT
- AlicenseAqualityAmaintenanceMCP server that enables natural-language interaction with the Avito Ads advertising API, including campaign, ad group, and creative management, statistics retrieval, fund transfers, and ORD paperwork filing.26110 npmMIT
- AlicenseNot gradedqualityFmaintenanceMCP server for Yandex Direct, Metrika, Wordstat, and Webmaster APIs, providing 132 tools to manage advertising campaigns, analytics, keyword research, and reporting through any MCP-compatible client.59MIT
TDQS
Scored across 13 tools
Each tool targets a specific Direct service (adgroups, ads, campaigns, etc.) with clear descriptions. The only potential overlap is campaigns_get vs direct_inventory, but inventory explicitly explains when to use it instead, so no confusion.
All tools share the direct_ prefix and snake_case. Most use the _get suffix for read operations, but inventory, fields, schema, and catalog deviate from this pattern. Still, the naming is consistent in style and readable.
13 tools is well within the optimal range. Each tool serves a distinct purpose, and the meta tools (schema, fields, catalog) add value without bloat.
The set covers read operations for all major entities and reports, plus meta tools for discovery. However, it lacks create/update/delete operations, making it incomplete for full lifecycle management. The catalog tool hints that other methods exist but are hidden, so the current surface is read-only.