Yandex Merchants MCP
Related Servers
Alternatives to Yandex Merchants MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for the Yandex Webmaster API, enabling natural-language queries about site indexing, search queries, IKS, diagnostics, sitemaps, and external links, as well as actions like recrawling, from AI assistants such as Claude, Cursor, and Codex.2021 npmMIT
- AlicenseAqualityDmaintenanceMCP server for Ozon Seller API, enabling product, order, finance, and analytics management via natural language or CLI.32MIT
- AlicenseAqualityAmaintenanceMCP server for Yandex Metrica analytics: query web analytics metrics, goals, conversions, and raw API data using natural language from AI clients like Claude and Cursor.896 npm2MIT
- AlicenseAqualityCmaintenanceMCP server for Yandex Eats Vendor Management API, enabling AI agents to manage partner operations like orders, busy mode, menu import, and feedback.112 npmMIT
- AlicenseAqualityAmaintenanceMCP server for managing Yandex Audiences (segments, pixels, lookalikes) from AI clients via natural language.2097 npmMIT
- AlicenseAqualityDmaintenanceMCP server for Wildberries Seller API enabling management of products, orders, supplies, analytics, advertising, and finance through natural language commands.32MIT
TDQS
Scored across 13 tools
Most tools have clear and distinct purposes: auth flow, feed listing, price updates, and offer visibility. The main ambiguity is between list_feeds and check_access, which both call the same endpoint, and set_offer_price vs set_offer_discount overlap partially since the price update tool already accepts a discount_base parameter.
Tool names generally follow a verb_noun pattern with snake_case: start_login, finish_login, list_feeds, set_offer_price, hide_offer, show_offers. Minor inconsistencies exist between set_offer_price and update_offer_prices, and singular/plural pairing is not fully symmetric (hide_offer/hide_offers but only show_offers), plus raw_request is a deliberate fallback outlier.
13 tools is well within the ideal range for this domain. Each tool addresses a distinct part of the workflow: authentication, diagnostics, feed listing, price updates, and offer hiding/showing, with bulk and single-item variants justified by operational limits.
The core workflows are covered: OAuth login/logout, feed discovery, price and discount updates, and offer visibility control. Some gaps exist, such as no way to read the hidden-offers list and no feed creation/deletion, but these appear to be API limitations rather than server omissions, and raw_request provides an escape hatch.