Ozon Seller MCP server with a full method catalog
ozon-mcp-ru
An MCP server for the Ozon Seller API with a catalog of 441 methods, read and write access classes, and keys stored outside the repository
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
- 240 catalog methods change data in the live account
- 11 methods are marked irreversible, including order and return operations
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/ozon-mcp-ruDetects 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 'OZON_CLIENT_ID=<your OZON_CLIENT_ID>' --env 'OZON_API_KEY=<your OZON_API_KEY>' ozon-mcp-ru -- uvx ozon-mcp-ru==0.6.0Or add to the file .mcp.json, in the project
{
"mcpServers": {
"ozon-mcp-ru": {
"command": "uvx",
"args": [
"ozon-mcp-ru==0.6.0"
],
"env": {
"OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
"OZON_API_KEY": "<your OZON_API_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
OZON_CLIENT_IDsecret, required- Client-Id из кабинета seller.ozon.ru, Настройки → API-ключи.
OZON_API_KEYsecret, required- Api-Key из той же пары. Оба уходят в одноимённые заголовки.
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": {
"ozon-mcp-ru": {
"command": "uvx",
"args": [
"ozon-mcp-ru==0.6.0"
],
"env": {
"OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
"OZON_API_KEY": "<your OZON_API_KEY>"
}
}
}
}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
OZON_CLIENT_IDsecret, required- Client-Id из кабинета seller.ozon.ru, Настройки → API-ключи.
OZON_API_KEYsecret, required- Api-Key из той же пары. Оба уходят в одноимённые заголовки.
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":"ozon-mcp-ru","type":"stdio","command":"uvx","args":["ozon-mcp-ru==0.6.0"],"env":{"OZON_CLIENT_ID":"<your OZON_CLIENT_ID>","OZON_API_KEY":"<your OZON_API_KEY>"}}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"ozon-mcp-ru": {
"type": "stdio",
"command": "uvx",
"args": [
"ozon-mcp-ru==0.6.0"
],
"env": {
"OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
"OZON_API_KEY": "<your OZON_API_KEY>"
}
}
}
}If the file already exists, add the server inside the servers key.
Keys and settings
OZON_CLIENT_IDsecret, required- Client-Id из кабинета seller.ozon.ru, Настройки → API-ключи.
OZON_API_KEYsecret, required- Api-Key из той же пары. Оба уходят в одноимённые заголовки.
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 ozon-mcp-ru --env 'OZON_CLIENT_ID=<your OZON_CLIENT_ID>' --env 'OZON_API_KEY=<your OZON_API_KEY>' -- uvx ozon-mcp-ru==0.6.0Or add to the file ~/.codex/config.toml, for all projects
[mcp_servers.ozon-mcp-ru]
command = "uvx"
args = ["ozon-mcp-ru==0.6.0"]
env = { OZON_CLIENT_ID = "<your OZON_CLIENT_ID>", OZON_API_KEY = "<your OZON_API_KEY>" }If the file already exists, append the block to the end.
Keys and settings
OZON_CLIENT_IDsecret, required- Client-Id из кабинета seller.ozon.ru, Настройки → API-ключи.
OZON_API_KEYsecret, required- Api-Key из той же пары. Оба уходят в одноимённые заголовки.
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 'OZON_CLIENT_ID=<your OZON_CLIENT_ID>' -e 'OZON_API_KEY=<your OZON_API_KEY>' ozon-mcp-ru uvx ozon-mcp-ru==0.6.0Or add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"ozon-mcp-ru": {
"command": "uvx",
"args": [
"ozon-mcp-ru==0.6.0"
],
"env": {
"OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
"OZON_API_KEY": "<your OZON_API_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
OZON_CLIENT_IDsecret, required- Client-Id из кабинета seller.ozon.ru, Настройки → API-ключи.
OZON_API_KEYsecret, required- Api-Key из той же пары. Оба уходят в одноимённые заголовки.
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": {
"ozon-mcp-ru": {
"command": "uvx",
"args": [
"ozon-mcp-ru==0.6.0"
],
"env": {
"OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
"OZON_API_KEY": "<your OZON_API_KEY>"
}
}
}
}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
OZON_CLIENT_IDsecret, required- Client-Id из кабинета seller.ozon.ru, Настройки → API-ключи.
OZON_API_KEYsecret, required- Api-Key из той же пары. Оба уходят в одноимённые заголовки.
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": {
"ozon-mcp-ru": {
"command": "uvx",
"args": [
"ozon-mcp-ru==0.6.0"
],
"env": {
"OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
"OZON_API_KEY": "<your OZON_API_KEY>"
}
}
}
}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
OZON_CLIENT_IDsecret, required- Client-Id из кабинета seller.ozon.ru, Настройки → API-ключи.
OZON_API_KEYsecret, required- Api-Key из той же пары. Оба уходят в одноимённые заголовки.
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": {
"ozon-mcp-ru": {
"command": "uvx",
"args": [
"ozon-mcp-ru==0.6.0"
],
"env": {
"OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
"OZON_API_KEY": "<your OZON_API_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
OZON_CLIENT_IDsecret, required- Client-Id из кабинета seller.ozon.ru, Настройки → API-ключи.
OZON_API_KEYsecret, required- Api-Key из той же пары. Оба уходят в одноимённые заголовки.
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": {
"ozon-mcp-ru": {
"type": "local",
"command": [
"uvx",
"ozon-mcp-ru==0.6.0"
],
"environment": {
"OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
"OZON_API_KEY": "<your OZON_API_KEY>"
}
}
}
}If the file already exists, add the server inside the mcp key.
Keys and settings
OZON_CLIENT_IDsecret, required- Client-Id из кабинета seller.ozon.ru, Настройки → API-ключи.
OZON_API_KEYsecret, required- Api-Key из той же пары. Оба уходят в одноимённые заголовки.
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": {
"ozon-mcp-ru": {
"command": "uvx",
"args": [
"ozon-mcp-ru==0.6.0"
],
"env": {
"OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
"OZON_API_KEY": "<your OZON_API_KEY>"
}
}
}
}If the file already exists, add the server inside the context_servers key.
Keys and settings
OZON_CLIENT_IDsecret, required- Client-Id из кабинета seller.ozon.ru, Настройки → API-ключи.
OZON_API_KEYsecret, required- Api-Key из той же пары. Оба уходят в одноимённые заголовки.
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": {
"ozon-mcp-ru": {
"command": "uvx",
"args": [
"ozon-mcp-ru==0.6.0"
],
"env": {
"OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
"OZON_API_KEY": "<your OZON_API_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
OZON_CLIENT_IDsecret, required- Client-Id из кабинета seller.ozon.ru, Настройки → API-ключи.
OZON_API_KEYsecret, required- Api-Key из той же пары. Оба уходят в одноимённые заголовки.
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Install the server with uvx ozon-mcp-ru and add it to claude_desktop_config.json with OZON_CLIENT_ID and OZON_API_KEY, or just run it and enter the keys at first launch: the server will ask for them and store them itself.
Other ways from the author
{
"mcpServers": {
"ozon": {
"command": "uvx",
"args": ["ozon-mcp-ru"],
"env": { "OZON_CLIENT_ID": "...", "OZON_API_KEY": "..." }
}
}
}Entry from the README, the package installs from PyPI.
This is third-party code. Review the repository files before installing.
What it does
The server executes the method catalog described in endpoints.yaml: 441 methods, 190 read, 240 write and 11 irreversible, grouped by topic such as FBS orders, FBO orders, products, FBP cross-docking, promotions, returns, reviews, finance and analytics. Because the server executes exactly this file, the method table cannot drift from the code. It supports several seller accounts at once with in-chat switching; keys live in ~/.marketplace-mcp/cabinets.json with 600 permissions rather than in environment variables or the repository.
Who it is for. For sellers and agencies that need broad Ozon Seller API coverage and work with several accounts at once.
Good fit when
- You need an Ozon Seller API method that simpler servers do not cover: the catalog spans 441 methods
- You run several Ozon shops and want to switch between them from the chat
- You need to authorize the Performance ad API separately via OAuth2
Not a fit when
- You want a minimal server with a couple of tools: this much coverage can be overkill
- You cannot trust the agent with irreversible actions unchecked: 11 methods in the catalog are marked irreversible
Example request
Switch to my second Ozon shop and show FBS orders due for shipment todayLimitations
This is an unofficial community project, not a server from Ozon itself. The Seller API and Performance API use different key pairs and are not interchangeable. The main ozon_mcp_ru package depends on the shared core and catalog from the author's separate marketplaces-mcp-ru repository.
How to disable. Remove the server from your MCP client config and delete the relevant account from ~/.marketplace-mcp/cabinets.json.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| OZON_CLIENT_ID required | Seller Client-Id from seller.ozon.ru, Settings, API keys. |
| OZON_API_KEY required, secret | Seller Api-Key from the same pair. |
Security check
- 240 catalog methods change data in the live account
- 11 methods are marked irreversible, including order and return operations
README in short
The Russian README explains the server is a thin wrapper over the marketplaces-mcp-ru dependency, gives three install paths, uvx from the release, uvx from the main branch, and npx skills add, a table breaking the 441 methods down by topic and by read/write/irreversible, and instructions for getting Seller API keys and separately Performance API keys.
FAQ
How many methods are available?
441 Ozon Seller API methods: 190 read, 240 write, 11 irreversible.
Can I connect several shops?
Yes, the server supports several accounts and switching between them from the chat, with keys stored locally at 600 permissions.
Related
Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent
Yandex Kit skills for store management
kit-skills
Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex
YouGile MCP by Indalo
YouGile MCP
Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit
Bitrix24 portal MCP server
MCP-сервер портала Битрикс24
Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail