SkillFoxx

Type a name, a task or a service

mcp-server-yandex-market-seller

An MCP server and CLI for the Yandex Market Partner API: 131 actions across orders, prices, stock, shipments and reviews via a search-and-execute pattern

MCP server

High risk

We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.

Why this level

  • Can change product prices and stock on a live store
  • Can perform actions on orders, returns and shipments
  • The entire API is reachable through the generic ym_execute, including write operations
All reasons and checks
Russian stack

dontsovcmc/mcp-server-yandex-market-sellerAuthor:dontsovcmc

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/mcp-server-yandex-market-seller

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

This entry is high risk, so there is no one-click install. Review the code and add the config by hand.

Run in a terminal

claude mcp add --transport stdio --env 'YM_TOKEN=<your YM_TOKEN>' yandex-market-seller -- uvx mcp-server-yandex-market-seller==0.6.0

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "yandex-market-seller": {
      "command": "uvx",
      "args": [
        "mcp-server-yandex-market-seller==0.6.0"
      ],
      "env": {
        "YM_TOKEN": "<your YM_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

YM_TOKENsecret, required
YM_CAMPAIGN_IDoptional
YM_BUSINESS_IDoptional
YM_AUTH_TYPEoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "yandex-market-seller": {
      "command": "uvx",
      "args": [
        "mcp-server-yandex-market-seller==0.6.0"
      ],
      "env": {
        "YM_TOKEN": "<your YM_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Keys and settings

YM_TOKENsecret, required
YM_CAMPAIGN_IDoptional
YM_BUSINESS_IDoptional
YM_AUTH_TYPEoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

code --add-mcp '{"name":"yandex-market-seller","type":"stdio","command":"uvx","args":["mcp-server-yandex-market-seller==0.6.0"],"env":{"YM_TOKEN":"<your YM_TOKEN>"}}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "yandex-market-seller": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-server-yandex-market-seller==0.6.0"
      ],
      "env": {
        "YM_TOKEN": "<your YM_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

YM_TOKENsecret, required
YM_CAMPAIGN_IDoptional
YM_BUSINESS_IDoptional
YM_AUTH_TYPEoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

codex mcp add yandex-market-seller --env 'YM_TOKEN=<your YM_TOKEN>' -- uvx mcp-server-yandex-market-seller==0.6.0

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.yandex-market-seller]
command = "uvx"
args = ["mcp-server-yandex-market-seller==0.6.0"]
env = { YM_TOKEN = "<your YM_TOKEN>" }

If the file already exists, append the block to the end.

Keys and settings

YM_TOKENsecret, required
YM_CAMPAIGN_IDoptional
YM_BUSINESS_IDoptional
YM_AUTH_TYPEoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

gemini mcp add -s user -e 'YM_TOKEN=<your YM_TOKEN>' yandex-market-seller uvx mcp-server-yandex-market-seller==0.6.0

Or add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "yandex-market-seller": {
      "command": "uvx",
      "args": [
        "mcp-server-yandex-market-seller==0.6.0"
      ],
      "env": {
        "YM_TOKEN": "<your YM_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

YM_TOKENsecret, required
YM_CAMPAIGN_IDoptional
YM_BUSINESS_IDoptional
YM_AUTH_TYPEoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "yandex-market-seller": {
      "command": "uvx",
      "args": [
        "mcp-server-yandex-market-seller==0.6.0"
      ],
      "env": {
        "YM_TOKEN": "<your YM_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Keys and settings

YM_TOKENsecret, required
YM_CAMPAIGN_IDoptional
YM_BUSINESS_IDoptional
YM_AUTH_TYPEoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "yandex-market-seller": {
      "command": "uvx",
      "args": [
        "mcp-server-yandex-market-seller==0.6.0"
      ],
      "env": {
        "YM_TOKEN": "<your YM_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Keys and settings

YM_TOKENsecret, required
YM_CAMPAIGN_IDoptional
YM_BUSINESS_IDoptional
YM_AUTH_TYPEoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "yandex-market-seller": {
      "command": "uvx",
      "args": [
        "mcp-server-yandex-market-seller==0.6.0"
      ],
      "env": {
        "YM_TOKEN": "<your YM_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

YM_TOKENsecret, required
YM_CAMPAIGN_IDoptional
YM_BUSINESS_IDoptional
YM_AUTH_TYPEoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "yandex-market-seller": {
      "type": "local",
      "command": [
        "uvx",
        "mcp-server-yandex-market-seller==0.6.0"
      ],
      "environment": {
        "YM_TOKEN": "<your YM_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

YM_TOKENsecret, required
YM_CAMPAIGN_IDoptional
YM_BUSINESS_IDoptional
YM_AUTH_TYPEoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "yandex-market-seller": {
      "command": "uvx",
      "args": [
        "mcp-server-yandex-market-seller==0.6.0"
      ],
      "env": {
        "YM_TOKEN": "<your YM_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

YM_TOKENsecret, required
YM_CAMPAIGN_IDoptional
YM_BUSINESS_IDoptional
YM_AUTH_TYPEoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .codeassistant/mcp.json, in the project

{
  "mcpServers": {
    "yandex-market-seller": {
      "command": "uvx",
      "args": [
        "mcp-server-yandex-market-seller==0.6.0"
      ],
      "env": {
        "YM_TOKEN": "<your YM_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

YM_TOKENsecret, required
YM_CAMPAIGN_IDoptional
YM_BUSINESS_IDoptional
YM_AUTH_TYPEoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

You will need: uv

Checked against the repository on Sep 25, 2026, commit c1c0398.

Text for your agent

Get an API key in the Yandex Market partner dashboard under Settings, API keys, find campaignId and businessId with mcp-server-yandex-market-seller campaigns, then add the server with claude mcp add yandex-market-seller -e YM_TOKEN=key -e YM_CAMPAIGN_ID=id -e YM_BUSINESS_ID=id -- uvx mcp-server-yandex-market-seller.

Other ways from the author
claude mcp add yandex-market-seller \
  -e YM_TOKEN=ваш_api_ключ \
  -e YM_CAMPAIGN_ID=12345 \
  -e YM_BUSINESS_ID=67890 \
  -- uvx mcp-server-yandex-market-seller

Method via uvx, no package installation required.

This is third-party code. Review the repository files before installing.

What it does

The server, its CLI utility and a Pydantic model library sit on top of the Yandex Market Partner API and cover 131 actions across 23 domains: orders and their documents, returns, shipments, warehouses, offers and their cards, prices, stock, delivery, customer reviews and questions, quality rating, promotions, bids, points of sale, regions, categories, tariffs, buyer chats, reports, stats and supply requests. Instead of 131 separate MCP tools, the server exposes three: ym_search finds the right action from a natural-language description, ym_execute runs it by id, and ym_execute_file runs an action while downloading a file, such as order labels. Every request goes straight to the API from the local machine; the token is never sent anywhere but Yandex Market.

Who it is for. For Yandex Market sellers who want to run orders, prices and stock through an agent instead of the partner dashboard.

Good fit when

  • You want to quickly find the right action among 131 without memorizing exact tool names
  • You need to download labels, deeds or other order documents right from a conversation with an agent
  • You need a CLI for automation and scripts without running an MCP client

Not a fit when

  • You need a small, fixed tool set instead of the search-and-execute pattern: the whole API surface is reachable via ym_search and ym_execute here
  • You have no Yandex Market seller API key or OAuth token

Example request

Download the labels for order 12345 and show me its current status

Limitations

No license is explicitly declared in the repository. It needs a seller API key or OAuth token, plus the campaign and business IDs, which must be looked up separately via the campaigns command after install. The natural-language action search depends on description quality, so specific operations are worth checking against the docs folder before running them on a live store.

How to disable. Remove the server with claude mcp remove yandex-market-seller and revoke the API key in the Yandex Market partner dashboard under Settings, API keys.

MCP

Transport
stdio
Authentication
API key
Environment variables
YM_TOKEN
required, secret		Yandex Market seller API key or OAuth token
YM_CAMPAIGN_ID
required		Seller campaign ID, found via the campaigns command
YM_BUSINESS_ID
required		Seller business ID, found via the campaigns command

Security check

  • Can change product prices and stock on a live store
  • Can perform actions on orders, returns and shipments
  • The entire API is reachable through the generic ym_execute, including write operations

README in short

The Russian README describes the server as an MCP, a CLI utility and a Pydantic model library on top of the Yandex Market Partner API. It explains the search-and-execute architecture instead of 131 separate tools, and gives a table of 23 action domains linking to detailed docs for each. It covers getting an API key, finding campaignId and businessId, connecting to Claude Code and Claude Desktop via uvx or pip, and a temporary --mcp-config connection with nothing saved to settings. It separately lists environment variables and a development section with tests.

FAQ

Why are there only three tools instead of 131?

The server uses a search-and-execute pattern: ym_search finds the right action by description, and ym_execute or ym_execute_file runs it, which is easier for an LLM than a hundred separate tools.

Where does the seller token go?

Only to the Yandex Market API; every request runs directly from the user's machine with no third-party server in between.

Official

Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent

MCP serverHigh risk483
Official

Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex

PluginHigh riskRussian stackNo VPN needed28
Editors’ pick

Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit

MCP serverHigh riskRussian stackNo VPN needed

Bitrix24 portal MCP server

MCP-сервер портала Битрикс24

Official

Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail

MCP serverHigh riskRussian stackNo VPN needed
Foxx AImcp-server-yandex-market-seller

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.