yandex-market-mcp-ru
This server exposes the Yandex Market Partner API to AI assistants, letting them search a 165-method catalog, call API endpoints (read/write/destructive), and manage credentials from chat.
Discover capabilities: check auth status, list sections, search methods by keyword (RU/EN), get an entity map, and describe any endpoint's schema, limits, and parameters.
Execute API methods: call catalog endpoints by operation_id with path/query/body parameters; write and destructive calls require explicit confirmation flags.
Call any raw path: full API coverage via arbitrary HTTP method and path, even endpoints not in the catalog.
Auto-paginate: fetch all rows from read endpoints with built-in pagination handling (offset, cursor, page, last_id styles).
Manage credentials: list/add/switch/remove cabinets (named API key sets) stored locally in ~/.marketplace-mcp/cabinets.json with chmod 600; rotate keys from chat with explicit warning.
Use ready workflows: list and fetch step-by-step analytical recipes for common marketplace tasks.
Convenience wrappers: get campaigns (shops), list orders, list offers, get stocks, get prices, and set a price for one offer.
yandex-market-mcp-ru
API Яндекс Маркета (Partner API) для ИИ-ассистентов: заказы и возвраты, товары и карточки, цены и тарифы, отчёты, отзывы и чаты. Каталог исполняется сервером.
Пакет поднимает один сервер, Яндекс Маркет, и ничего больше. Сервер, каталог и
ядро приходят зависимостью из marketplaces-mcp-ru:
здесь имя, точка входа и документация под один маркетплейс.
Установка
Пакет на PyPI, поэтому строка одна:
uvx yandex-market-mcp-ruЕсли нужна ветка main, а не релиз:
uvx --from git+https://github.com/ilyautov/yandex-market-mcp-ru yandex-market-mcp-ruClaude Desktop, claude_desktop_config.json:
{
"mcpServers": {
"ym": {
"command": "uvx",
"args": ["yandex-market-mcp-ru"],
"env": { "YANDEX_MARKET_API_KEY": "..." }
}
}
}Третий путь, если агент умеет скиллы: он поставит сервер и настроит клиент сам.
npx skills add ilyautov/yandex-market-mcp-ruRelated MCP server: vk-mcp-ru
Ключи
Где взять Api-Key. Кабинет партнёра partner.market.yandex.ru, раздел Настройки, пункт Доступ к API. Ключ уходит в заголовок Api-Key, хост api.partner.market.yandex.ru.
Бизнес и кампания это разные идентификаторы. Часть методов адресуется идентификатором бизнеса, часть номером кампании (магазина). Подставить один вместо другого даёт не ошибку доступа, а пустой ответ, что путает сильнее.
Где он лежит. В ~/.marketplace-mcp/cabinets.json с правами chmod 600, локально.
переменная | секрет | что это |
| да | API-ключ из кабинета партнёра, раздел Настройки → API. |
Ключи можно не держать в окружении: сервер умеет кабинеты и кладёт их в
~/.marketplace-mcp/cabinets.json с правами 600, вне репозитория. Магазинов
подключается сколько нужно, переключение прямо из чата.
Карта методов
Каталог лежит в зависимости как yandex_mcp/endpoints.yaml:
165 методов, из них 109 на чтение, 49 на запись и 7 необратимых.
Сервер исполняет ровно этот файл, поэтому таблица не может разойтись с кодом.
тема | методов | чтение | запись | необратимые |
Заказы, возвраты и невыкупы | 38 | 19 | 19 | 0 |
Отчёты | 27 | 27 | 0 | 0 |
Товары и карточки | 22 | 11 | 8 | 3 |
Отгрузки, поставки и склады | 21 | 15 | 6 | 0 |
Отзывы, вопросы и чаты | 18 | 11 | 6 | 1 |
Самовывоз и регионы доставки | 15 | 10 | 3 | 2 |
Цены, тарифы и карантин | 10 | 6 | 4 | 0 |
Продвижение и реклама | 8 | 4 | 3 | 1 |
Кабинет и служебное | 6 | 6 | 0 | 0 |
Подробный разбор с параметрами и лимитами: https://marketplaces-mcp-ru.aifrontier.tech/yandex-market-api.html
Что спросить в чате
покажи заказы на Яндекс Маркете за неделю
какой у меня индекс качества и что его роняет
собери отчёт по продажам за месяц
покажи товары в карантине цен
Частые ошибки
Пустой ответ вместо данных. Чаще всего перепутаны идентификатор бизнеса и номер кампании. Ошибки доступа при этом не будет, ответ придёт корректный и пустой.
Ошибка в имени поля. Каталог методов собран из официального OpenAPI-документа, а живой прогон на реальных кабинетах ещё не делался. Неточности в именах полей возможны. describe_method покажет схему, ym_get_raw даст поправить запрос на месте.
Метод не находится по названию. Ищите по теме, а не по имени: спросите агента «что ты умеешь по Яндекс Маркету», он покажет разделы и подберёт метод сам.
Чем это отличается от marketplaces-mcp-ru
Ничем, кроме состава. marketplaces-mcp-ru ставит четыре маркетплейса сразу и держит их
под одним сервером, yandex-market-mcp-ru ставит один. Код общий: правка в ядре доезжает
сюда обновлением зависимости, а не копированием.
нужно | пакет |
только Яндекс Маркет |
|
все четыре маркетплейса |
|
Кто это сделал
Илья Утов, лаборатория AI Frontier. Как эти инструменты устроены внутри, пишу в Telegram и LinkedIn.
Рядом стоят business-mcp-ru (hh.ru, VK, Диадок, СБИС, Честный знак), moysklad-mcp-ru и humanizer-ru.
Все проекты одним списком, разобранные по назначению: ilyautov.github.io.
Лицензия
MIT, см. LICENSE.
Available Tools
26 toolsym_add_cabinetAIdempotent
Add or update a cabinet (a named set of API credentials), from chat.
⚠️ This puts the key into the chat transcript — requires i_understand_key_goes_to_chat=true. The terminal-free safe alternative is the installer (install.py / double-click), where the key never enters chat.
Args: credentials: dict with the required fields for this service ({fields}). For Ozon: {{"client_id": "...", "api_key": "..."}}; for WB: {{"token": "..."}}. name: optional label. If omitted, the cabinet is named after the real shop name fetched from the marketplace (falls back to "main"). i_understand_key_goes_to_chat: must be true to proceed. Saved to ~/.marketplace-mcp/cabinets.json (local, chmod 600), never echoed.
Inputs: credentials (required), name, i_understand_key_goes_to_chat. Returns: result
ym_call_methodARead-only
Execute one READ endpoint from the catalog by operation_id.
Target API: https://yandex.ru/dev/market/partner-api/doc/ru/.
Reads only: nothing here changes data, so it runs without confirmation. To change data use ym_write_method, to delete use ym_delete_method.
Args: operation_id: id from the catalog (see ym_search_methods). path_values: values for {placeholders} in the path. query: query-string parameters. body: JSON request body (a few read endpoints take one). Returns JSON: {"ok": true, "status", "data"} or the error envelope.
Inputs: operation_id (required), body, query, path_values. Returns: result
ym_check_authARead-only
Check whether the required credentials are present in the environment.
Does NOT reveal secret values — only reports which variables are set. Returns JSON: {"ready": bool, "missing": [str], "required": [str]}.
Inputs: no named parameters. Returns: result
ym_delete_methodADestructive
Execute one DESTRUCTIVE endpoint: deletes or irreversibly changes data.
Target API: https://yandex.ru/dev/market/partner-api/doc/ru/.
Both confirm_write=true and i_understand_this_modifies_data=true are required; nothing is sent without both.
Args: operation_id: id from the catalog (see ym_search_methods). path_values: values for {placeholders} in the path. query: query-string parameters. body: JSON request body. confirm_write: must be true. i_understand_this_modifies_data: must be true. Returns JSON: {"ok": true, "status", "data"} or the error envelope.
Inputs: operation_id (required), body, query, path_values, +2 more. Returns: result
ym_delete_rawADestructive
Delete data at ANY path, including paths not in the catalog.
Target API: https://yandex.ru/dev/market/partner-api/doc/ru/.
DELETE only. Both confirm_write=true and i_understand_this_modifies_data=true are required.
Args: path: full path beginning with '/'. method: DELETE. host: host override; defaults to the service's default host. query: query-string parameters. body: JSON request body. confirm_write: must be true. i_understand_this_modifies_data: must be true. Returns JSON: {"ok": true, "status", "data"} or the error envelope.
Inputs: path (required), body, host, query, +3 more. Returns: result
ym_describe_methodARead-only
Return the full catalog record for one endpoint: method, host, path, scope, safety level, pagination style, rate limit, params and doc URL.
Inputs: operation_id (required). Returns: result
ym_fetch_allARead-only
Auto-paginate a read endpoint and return every row in one response.
Handles offset, last_id, cursor (Ozon v4/v5), page and WB lastChangeDate styles. The array path is taken from the catalog automatically.
Args: operation_id: a read endpoint from the catalog. query / body / path_values: base parameters (cursor fields are managed). items_path: override the array path (default: the endpoint's own). limit: page size to request. max_items: hard cap to protect context (default 10000). Returns JSON: {"ok", "items", "total_fetched", "pages_fetched", "truncated"}.
Inputs: operation_id (required), body, limit, query, +3 more. Returns: result
ym_get_campaignsARead-only
List the seller's shops (кампании) with their campaignId and businessId.
Call this first: nearly every other Yandex Market method needs a campaignId (магазин) or businessId (кабинет продавца). Both are in the response: campaigns[].id and campaigns[].business.id.
Args: page_token: pageToken from a previous page (empty for the first page). limit: page size (<=100). Returns JSON: {"ok": true, "data": {"campaigns": [...], "paging": {...}}}.
Inputs: limit, page_token. Returns: result
ym_get_offersARead-only
List the seller's offers (товары) with their Market card mapping (POST /v2/businesses/{businessId}/offer-mappings).
Args: business_id: cabinet id (campaigns[].business.id). offer_ids: comma-separated offerId (SKU) filter; empty = all. page_token: pageToken from a previous page. limit: page size (<=200). Returns JSON: {"ok": true, "data": {"result": {"offerMappings": [...], "paging": {...}}}}.
Inputs: business_id (required), limit, offer_ids, page_token. Returns: result
ym_get_ordersARead-only
List orders of one shop (GET /v2/campaigns/{campaignId}/orders).
Args: campaign_id: shop id from ym_get_campaigns. status: filter, e.g. PROCESSING | DELIVERY | PICKUP | DELIVERED | CANCELLED | UNPAID (comma-separated allowed). Empty = all. from_date: order creation date lower bound, DD-MM-YYYY (Yandex format). to_date: upper bound, DD-MM-YYYY. page_token: pageToken from a previous page. limit: page size (<=50). Returns JSON: {"ok": true, "data": {"orders": [...], "paging": {...}}}. For every order across pages use ym_fetch_all with ym_get_orders.
Inputs: campaign_id (required), limit, status, to_date, +2 more. Returns: result
ym_get_pricesARead-only
Base prices set for all shops of the cabinet (POST /v2/businesses/{businessId}/offer-prices).
Args: business_id: cabinet id. offer_ids: comma-separated offerId filter; empty = all. page_token: pageToken from a previous page. limit: page size (<=200). Returns JSON with result.offers[].price {value, currencyId, discountBase, updatedAt}.
Inputs: business_id (required), limit, offer_ids, page_token. Returns: result
ym_get_rawARead-only
Read ANY endpoint by path, including ones missing from the catalog.
Target API: https://yandex.ru/dev/market/partner-api/doc/ru/.
Safe verbs only (GET, HEAD, OPTIONS). To change data use ym_write_raw, to delete use ym_delete_raw.
Args: path: full path beginning with '/', e.g. "/v2/regions". method: safe verb, GET by default. host: host override; defaults to the service's default host. query: query-string parameters. body: JSON request body (rare on reads; some APIs want one). Returns JSON: {"ok": true, "status", "data"} or the error envelope.
Inputs: path (required), body, host, query, +1 more. Returns: result
ym_get_sectionARead-only
List all endpoints in one section.
Args: section: section name (see ym_list_sections), e.g. "statistics". Returns JSON list of {operation_id, method, path, safety, summary}.
Inputs: section (required). Returns: result
ym_get_stocksARead-only
Stock per offer per warehouse for one shop, with optional turnover (POST /v2/campaigns/{campaignId}/offers/stocks).
Args: campaign_id: shop id. offer_ids: comma-separated offerId filter; empty = all. with_turnover: also return turnover (оборачиваемость) per offer. page_token: pageToken from a previous page. limit: page size (<=200). Returns JSON: {"ok": true, "data": {"result": {"warehouses": [{"warehouseId", "offers": [...]}]}}}.
Inputs: campaign_id (required), limit, offer_ids, page_token, +1 more. Returns: result
ym_get_workflowARead-only
Return the full plan for one workflow: ordered steps (each naming a catalog operation_id and why), interpretation guidance, and common mistakes to avoid.
Args: name: workflow name (see {svc}_list_workflows).
Inputs: name (required). Returns: result
ym_list_cabinetsARead-only
List configured cabinets for this marketplace and which one is active.
Returns JSON: {"active": str|null, "cabinets": [names], "fields_needed": [...]}. Secret values are never returned.
Inputs: no named parameters. Returns: result
ym_list_sectionsARead-only
List API sections and how many catalog endpoints each contains.
Inputs: no named parameters. Returns: result
ym_list_workflowsARead-only
List ready-made analytical workflows (recipes) for this marketplace.
Returns JSON: [{name, category, when_to_use}]. Use {svc}_get_workflow to fetch the full step-by-step plan for one.
Inputs: no named parameters. Returns: result
ym_mapARead-only
The big picture: business entities this API covers and the go-to methods for each. Call with no args to see the whole map ("you are here"); pass entity="reviews" (or stocks/prices/orders/…) to list every method of one entity. Use this before guessing — it orients you fast.
Inputs: entity. Returns: result
ym_remove_cabinetADestructive
Delete a stored cabinet. If it was active, another becomes active.
Args: name: the cabinet to remove.
Inputs: name (required). Returns: result
ym_search_methodsARead-only
Search the endpoint catalog by keyword (works in Russian and English).
Args: query: free text, e.g. "остатки", "stocks", "update price". limit: max results (1-50). Returns JSON list of matching endpoints (best first).
Inputs: query (required), limit. Returns: result
ym_set_keyAIdempotent
Change / rotate the API key from chat (e.g. the old one expired or leaked).
⚠️ The key goes into the chat transcript — requires i_understand_key_goes_to_chat=true. The safe, terminal-free alternative is the installer, where the key never enters chat. Use a scoped key and rotate it in the seller cabinet if it was exposed.
Args: credentials: dict with the required fields ({fields}). cabinet: which cabinet to update. Default: the active one (so "my key expired" just works). If there is none, the cabinet is named from the marketplace's shop name, else "main". i_understand_key_goes_to_chat: must be true to proceed. On success the key is validated against the marketplace and the shop name is reported. Saved locally (chmod 600), never echoed back.
Inputs: credentials (required), cabinet, i_understand_key_goes_to_chat. Returns: result
ym_set_priceAIdempotent
Set the base price of ONE offer for all shops of the cabinet (POST /v2/businesses/{businessId}/offer-prices/updates). WRITE.
Requires confirm_write=true. discount_base is the strikethrough price (must be higher than price); 0 = no discount shown.
Args: business_id: cabinet id. offer_id: seller's SKU (offerId). price: new price, e.g. 1499. discount_base: pre-discount price, or 0 to clear. currency: RUR (default) — Yandex uses "RUR", not "RUB". confirm_write: must be true to send. Returns JSON: {"ok": true, "data": {"status": "OK"}} on success.
Inputs: price (required), offer_id (required), business_id (required), currency, +2 more. Returns: result
ym_use_cabinetAIdempotent
Switch the active cabinet. Subsequent API calls use its credentials.
Args: name: the cabinet to activate (see ym_list_cabinets).
Inputs: name (required). Returns: result
ym_write_methodA
Execute one WRITE endpoint from the catalog: create or update data.
Target API: https://yandex.ru/dev/market/partner-api/doc/ru/.
Requires confirm_write=true; nothing is sent without it. Irreversible operations live in ym_delete_method, reads in ym_call_method.
Args: operation_id: id from the catalog (see ym_search_methods). path_values: values for {placeholders} in the path. query: query-string parameters. body: JSON request body. confirm_write: must be true. Returns JSON: {"ok": true, "status", "data"} or the error envelope.
Inputs: operation_id (required), body, query, path_values, +1 more. Returns: result
ym_write_rawA
Create or update data at ANY path, including paths not in the catalog.
Target API: https://yandex.ru/dev/market/partner-api/doc/ru/.
POST, PUT and PATCH only; requires confirm_write=true.
Args: method: POST, PUT or PATCH. path: full path beginning with '/'. host: host override; defaults to the service's default host. query: query-string parameters. body: JSON request body. confirm_write: must be true. Returns JSON: {"ok": true, "status", "data"} or the error envelope.
Inputs: path (required), method (required), body, host, +2 more. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 26 tools
The tools fall into clearly delineated groups: catalog discovery, generic catalog execution, raw-path execution, cabinet management, workflows, and domain convenience methods. Even paired tools like ym_call_method/ym_get_raw and ym_write_method/ym_write_raw are cleanly separated by catalog-based versus raw-path targeting, so an agent should not misselect.
All tools share the ym_ prefix and follow a consistent verb_noun or verb_adjective pattern, such as list_sections, get_offers, set_price, remove_cabinet, call_method, and write_raw. The few one-word names (ym_map, ym_fetch_all) still fit the overall style, and there is no mixing of camelCase or vague verbs.
At 26 tools, the server is above the ideal range and slightly heavy. However, the count is justified by the broad scope: catalog exploration, generic and raw API execution, cabinet management, workflows, and convenience endpoints all serve distinct purposes. It feels like a large but deliberate surface rather than bloated.
The generic catalog-based and raw-path executors cover read, write, and delete operations, meaning the entire Yandex Market Partner API is reachable and there are no dead ends. Convenience methods cover the core seller workflows (campaigns, offers, orders, stocks, prices), and cabinet/auth setup is fully handled, so the surface is effectively complete.
Maintenance
Related MCP Connectors
Russian APIs for AI agents: YooKassa, CDEK, Bitrix24 and more. Ready scenarios with code. No key.
AI service marketplace — agents discover, call, and pay for API services automatically.
Live data for AI agents. Search the catalog, read the price, call the tool; keys stay server-side.
RU merchant catalog for AI agents: live price, stock, choices and controlled checkout. Not x402.
Related MCP Servers
- AlicenseAqualityDmaintenanceIntegrates with Yandex Market Partner API, providing search and execute tools for managing orders, returns, shipments, offers, prices, and other seller operations via natural language.181MIT
- AlicenseAqualityBmaintenanceVK API for AI assistants: wall posts, communities, messages, market items, ads and stats. 373 methods in one catalog, each with a read/write/destructive safety class; the agent searches methods in plain language instead of receiving 373 tools.18158 PyPI3MIT
- AlicenseAqualityBmaintenanceOzon Seller API in your AI assistant: products, FBS and FBO orders, prices, stocks, finance and reviews. 441 methods live in a YAML catalog the server executes, the agent searches it in plain language and calls a method through three generic tools, and every method carries an access class so writes and irreversible calls ask for confirmation.2561 PyPI3MIT
- AlicenseAqualityBmaintenanceAvito business API in your AI assistant: listings and statistics, buyer messenger, orders and Avito Delivery, bulk upload, promotion and reviews. 64 methods live in a YAML catalog the server executes, the agent searches it in plain language, and every method carries an access class so writes and irreversible calls ask for confirmation.3061 PyPI4MIT