Yandex Market Seller MCP: Documentation

Connection

uvx mcp-server-yandex-market-seller (stdio, Python, requires uv). Via Claude Code: claude mcp add yandex-market-seller -e YM_TOKEN=... -e YM_CAMPAIGN_ID=... -e YM_BUSINESS_ID=... -- uvx mcp-server-yandex-market-seller. Auth: YM_TOKEN, a key from the Yandex Market partner cabinet (Settings → API keys) or an OAuth token; find YM_CAMPAIGN_ID and YM_BUSINESS_ID by running mcp-server-yandex-market-seller campaigns after install (the output lists campaignId and businessId).

Capabilities

A "search + execute" architecture: not 131 separate MCP functions, but 3 meta-tools — ym_search (find the right action from a plain-language description, returning an action_id and its parameter schema), ym_execute (run an action by id), ym_execute_file (run an action that downloads a file, such as order labels). The 131 actions themselves span 24 sections of the Yandex Market Partner API: campaigns (6), orders (28), returns (9), shipments (14), warehouses (4), offers (8), prices (6), stocks (2), feedbacks (5), promos (4), reports (3) and 13 more sections (offer_cards, delivery, questions, quality, bids, outlets, geo, categories, tariffs, chats, stats, supply, operations).

Agent flow

"Download the shipping labels for order 987654", "update stock for SKU-1 to 25 units", "show today's new orders and create a shipment".

Note

A community project (dontsovcmc), not affiliated with Yandex Market. Actively pushed (last commit 10.05.2026), but early-stage: just 1 GitHub star, and there's no confirmation gate for destructive actions inside the server itself — check parameters before calling ym_execute.