Yandex Direct MCP
Related Servers
Alternatives to Yandex Direct MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to manage Yandex Direct advertising campaigns, ads, keywords, and reports via natural language using the Yandex Direct API v5.21MIT
- AlicenseAqualityDmaintenanceIntegrates with Yandex Direct API v5 to manage ads via 20 tools, with dry-run protection preventing accidental spending.21MIT
- AlicenseAqualityCmaintenanceEnables AI agents to manage Yandex Direct advertising accounts via the API v5, including reports, bids, campaign management, and semantic analysis through natural language requests.4396 npmMIT
- 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.5940 npm1AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables interaction with Yandex advertising and analytics APIs (Direct, Metrika, Audience, Webmaster, AdMetrica) through MCP tools, resources, and prompts for campaign management and data retrieval.MIT
- AlicenseAqualityAmaintenanceEnables natural language interaction with Yandex Direct API v5 via MCP, providing 113 generated methods with accurate handling of monetary amounts and 64-bit IDs, plus a command-line mode.1335 npm1MIT
TDQS
Scored across 43 tools
Each tool targets a distinct resource+operation (campaigns vs ad groups vs ads vs keywords vs bid modifiers vs sitelinks vs callouts vs libraries), and the descriptions explicitly differentiate the close pairs (add_bid_modifier vs set_bid_modifiers vs delete_bid_modifiers, campaign_action vs update_campaign). The only real overlaps are the client-related trio (list_clients, clients_overview, get_account_info) and raw_request acting as a catch-all for everything else, but both are clearly framed.
The dominant pattern is verb_noun (list_campaigns, create_text_ad, get_bid_modifiers, delete_callouts, upload_ad_image), with a consistent secondary family of <resource>_action (campaign_action, ad_action, keyword_action). Minor deviations exist — logout and auth_status break the pattern, and clients_overview/raw_request are noun-first — but overall the scheme is predictable.
43 tools is heavy and sits above the comfortable range, forcing an agent to scan a large surface. However, the domain (full Yandex Direct v5 advertising API: campaigns, groups, ads, keywords, bids, extensions, media libraries, reporting, clients, auth) genuinely spans this many distinct resources, so most tools do earn their place rather than being redundant.
Coverage is broad and lifecycle-oriented: create/list/update/action for campaigns, groups, and ads; add/list/action/bid-setting for keywords; add/get/set/delete for bid modifiers; create/get/delete for sitelinks and callouts; upload/get for images; plus reporting, balance, quota, clients, and auth. A few gaps remain (video/creative upload, image deletion, single-object getters) but raw_request is a documented escape hatch that prevents dead ends.