Ozon Seller API MCP server
ozon-seller-mcp
A compact MCP server for the Ozon Seller API: products, prices, stock, FBS and FBO orders, finance, reviews and buyer chats
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
- Changes prices, stock and product cards in the live account with no sandbox
- Can confirm or cancel order shipment
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/ozon-seller-mcpDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Assembled automatically, review before installing.
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-seller -- uvx run --directory /path/to/ozon-seller-mcp python server.pyOr add to the file .mcp.json, in the project
{
"mcpServers": {
"ozon-seller": {
"command": "uvx",
"args": [
"run",
"--directory",
"/path/to/ozon-seller-mcp",
"python",
"server.py"
],
"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 from Ozon Seller API personal account
OZON_API_KEYsecret, required- API Key from Ozon Seller API personal account
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-seller": {
"command": "uvx",
"args": [
"run",
"--directory",
"/path/to/ozon-seller-mcp",
"python",
"server.py"
],
"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 from Ozon Seller API personal account
OZON_API_KEYsecret, required- API Key from Ozon Seller API personal account
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-seller","type":"stdio","command":"uvx","args":["run","--directory","/path/to/ozon-seller-mcp","python","server.py"],"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-seller": {
"type": "stdio",
"command": "uvx",
"args": [
"run",
"--directory",
"/path/to/ozon-seller-mcp",
"python",
"server.py"
],
"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 from Ozon Seller API personal account
OZON_API_KEYsecret, required- API Key from Ozon Seller API personal account
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-seller --env 'OZON_CLIENT_ID=<your OZON_CLIENT_ID>' --env 'OZON_API_KEY=<your OZON_API_KEY>' -- uvx run --directory /path/to/ozon-seller-mcp python server.pyOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.ozon-seller]
command = "uvx"
args = ["run", "--directory", "/path/to/ozon-seller-mcp", "python", "server.py"]
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 from Ozon Seller API personal account
OZON_API_KEYsecret, required- API Key from Ozon Seller API personal account
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 ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"ozon-seller": {
"command": "uvx",
"args": [
"run",
"--directory",
"/path/to/ozon-seller-mcp",
"python",
"server.py"
],
"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 from Ozon Seller API personal account
OZON_API_KEYsecret, required- API Key from Ozon Seller API personal account
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-seller": {
"command": "uvx",
"args": [
"run",
"--directory",
"/path/to/ozon-seller-mcp",
"python",
"server.py"
],
"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 from Ozon Seller API personal account
OZON_API_KEYsecret, required- API Key from Ozon Seller API personal account
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-seller": {
"command": "uvx",
"args": [
"run",
"--directory",
"/path/to/ozon-seller-mcp",
"python",
"server.py"
],
"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 from Ozon Seller API personal account
OZON_API_KEYsecret, required- API Key from Ozon Seller API personal account
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-seller": {
"command": "uvx",
"args": [
"run",
"--directory",
"/path/to/ozon-seller-mcp",
"python",
"server.py"
],
"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 from Ozon Seller API personal account
OZON_API_KEYsecret, required- API Key from Ozon Seller API personal account
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-seller": {
"type": "local",
"command": [
"uvx",
"run",
"--directory",
"/path/to/ozon-seller-mcp",
"python",
"server.py"
],
"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 from Ozon Seller API personal account
OZON_API_KEYsecret, required- API Key from Ozon Seller API personal account
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-seller": {
"command": "uvx",
"args": [
"run",
"--directory",
"/path/to/ozon-seller-mcp",
"python",
"server.py"
],
"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 from Ozon Seller API personal account
OZON_API_KEYsecret, required- API Key from Ozon Seller API personal account
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-seller": {
"command": "uvx",
"args": [
"run",
"--directory",
"/path/to/ozon-seller-mcp",
"python",
"server.py"
],
"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 from Ozon Seller API personal account
OZON_API_KEYsecret, required- API Key from Ozon Seller API personal account
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Clone https://github.com/Oxonomy/ozon-seller-mcp, run uv sync, copy .env.example to .env and set OZON_CLIENT_ID and OZON_API_KEY from your Ozon Seller settings, then connect the server with uv run --directory /path/to/ozon-seller-mcp python server.py.
Other ways from the author
{
"mcpServers": {
"ozon-seller": {
"command": "uv",
"args": ["run", "--directory", "/path/to/ozon-seller-mcp", "python", "server.py"],
"env": {
"OZON_CLIENT_ID": "your_client_id",
"OZON_API_KEY": "your_api_key"
}
}
}
}Entry from the README for claude_desktop_config.json; point it at your own repo path.
This is third-party code. Review the repository files before installing.
What it does
The server wraps the main sections of the Ozon Seller API into agent tools: view, create, update, archive and delete products with image upload, read and change prices and stock for both FBS and FBO, work with orders in both schemes including shipment confirmation and labels, list warehouses, browse the category tree with attributes, pull sales and conversion analytics, financial transactions, buyer chat, reviews and replies, seller rating and promotion lists. It is implemented in a single server.py file in Python.
Who it is for. For Ozon sellers who want a simple server with no extra infrastructure for basic Seller API operations.
Good fit when
- You want a compact server with no Docker, databases or queues for the Ozon Seller API
- You need to quickly view or update product prices and stock
- You need to reply to a review or a buyer message right from the agent chat
Not a fit when
- You need a production server with audit logging, rate limiting and monitoring: a more developed project like MASTER116/ozon-mcp-server fits better
- You need the Ozon Performance ad API: the server only covers the Seller API
Example request
Show FBO warehouse stock for my products and update the price on the SKU that is nearly out of stockLimitations
The install instructions in the README literally use a your-username placeholder instead of the real repository path, so the clone command needs fixing to Oxonomy/ozon-seller-mcp. There are no automated tests and no license file in the repository. All tools live in a single file with no module split, which makes it harder to extend for your own needs.
How to disable. Remove the server from your MCP client config.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| OZON_CLIENT_ID required | Seller Client Id from the Ozon Seller account. |
| OZON_API_KEY required, secret | Seller Api Key from the same pair as the Client Id. |
Security check
- Changes prices, stock and product cards in the live account with no sandbox
- Can confirm or cancel order shipment
README in short
The Russian README lists the Seller API sections the server covers: products, prices, stock, FBS and FBO orders, warehouses, categories, analytics, finance, chats, reviews, rating and promotions. It gives install steps via uv sync, .env setup with OZON_CLIENT_ID and OZON_API_KEY, and config examples for Claude Desktop and Claude Code.
FAQ
Where do I get the keys?
In the Ozon Seller account under Settings, Seller API.
Does the server apply changes immediately?
Yes, the price, stock and product update tools apply changes immediately in the live account; there is no sandbox for the Ozon Seller API.
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