Ozon Seller API MCP server
ozon-seller-mcp
An MCP server for the Ozon Seller API: categories, attributes, analytics, stock and turnover through typed tools
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- The key grants access to a real seller account's analytics and stock data
- Based on the README the server offers no write tools, but the key should still be read-only if Ozon allows it
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/kirillwinter1-ozon-seller-mcpDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Assembled automatically, review before installing.
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 -- npx -y ozon-seller-mcpOr add to the file .mcp.json, in the project
{
"mcpServers": {
"ozon": {
"command": "npx",
"args": [
"-y",
"ozon-seller-mcp"
],
"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- Seller Client ID from Ozon
OZON_API_KEYsecret, required- API Key from Ozon
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"ozon": {
"command": "npx",
"args": [
"-y",
"ozon-seller-mcp"
],
"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- Seller Client ID from Ozon
OZON_API_KEYsecret, required- API Key from Ozon
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Run in a terminal
code --add-mcp '{"name":"ozon","type":"stdio","command":"npx","args":["-y","ozon-seller-mcp"],"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": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"ozon-seller-mcp"
],
"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- Seller Client ID from Ozon
OZON_API_KEYsecret, required- API Key from Ozon
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 --env 'OZON_CLIENT_ID=<your OZON_CLIENT_ID>' --env 'OZON_API_KEY=<your OZON_API_KEY>' -- npx -y ozon-seller-mcpOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.ozon]
command = "npx"
args = ["-y", "ozon-seller-mcp"]
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- Seller Client ID from Ozon
OZON_API_KEYsecret, required- API Key from Ozon
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": {
"command": "npx",
"args": [
"-y",
"ozon-seller-mcp"
],
"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- Seller Client ID from Ozon
OZON_API_KEYsecret, required- API Key from Ozon
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": {
"command": "npx",
"args": [
"-y",
"ozon-seller-mcp"
],
"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- Seller Client ID from Ozon
OZON_API_KEYsecret, required- API Key from Ozon
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": {
"command": "npx",
"args": [
"-y",
"ozon-seller-mcp"
],
"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- Seller Client ID from Ozon
OZON_API_KEYsecret, required- API Key from Ozon
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": {
"command": "npx",
"args": [
"-y",
"ozon-seller-mcp"
],
"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- Seller Client ID from Ozon
OZON_API_KEYsecret, required- API Key from Ozon
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": {
"type": "local",
"command": [
"npx",
"-y",
"ozon-seller-mcp"
],
"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- Seller Client ID from Ozon
OZON_API_KEYsecret, required- API Key from Ozon
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": {
"command": "npx",
"args": [
"-y",
"ozon-seller-mcp"
],
"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- Seller Client ID from Ozon
OZON_API_KEYsecret, required- API Key from Ozon
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": {
"command": "npx",
"args": [
"-y",
"ozon-seller-mcp"
],
"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- Seller Client ID from Ozon
OZON_API_KEYsecret, required- API Key from Ozon
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/kirillwinter1/ozon-seller-mcp, run npm install, build with npm run build, and add the server to your MCP client config as node dist/index.js with the Ozon key and client id as environment variables.
Other ways from the author
git clone https://github.com/kirillwinter1/ozon-seller-mcp.git
cd ozon-seller-mcp
npm install
npm run buildDefault branch is feature/ozon-seller-mcp. After building, run the server with node dist/index.js.
This is third-party code. Review the repository files before installing.
What it does
A Node.js MCP server wraps the Ozon Seller API in tools grouped by area: categories and their attributes, attribute values, sales analytics, warehouse stock and product turnover. Each tool has a zod parameter schema and its own test. The server runs locally over stdio and needs the seller's key and client id from environment variables.
Who it is for. For Ozon sellers and developers who want a predictable, test-covered MCP server for analytics and categories.
Good fit when
- You need to check a category's attributes before filling out a listing
- You need sales and turnover analytics by warehouse
- You want a test-covered MCP server rather than a one-off script
Not a fit when
- You need tools to change prices, stock or orders; the server does not provide them
- You need a ready npm registry package; none is published
Example request
Show the required attributes for the kids' shoes category on Ozon and warehouse turnover for the monthLimitations
The default branch is feature/ozon-seller-mcp, not main, worth noting when cloning. The package is not published to npm; the server is built and run from source. It needs an Ozon Seller API key. The README does not describe every tool in detail.
How to disable. Remove the ozon-seller-mcp server from your MCP client configuration.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| OZON_CLIENT_ID required, secret | The seller's Client Id from the Ozon Seller account. |
| OZON_API_KEY required, secret | The Ozon Seller API key. |
Security check
- The key grants access to a real seller account's analytics and stock data
- Based on the README the server offers no write tools, but the key should still be read-only if Ozon allows it
README in short
The README describes the server as an MCP wrapper over the Ozon Seller API for managing products, orders and analytics, lists Node.js 18+ requirements, the key and client id environment variables, and build and test commands. It shows the tool structure by category and analytics sections. MIT licensed.
FAQ
Are there tools to change prices or stock?
No, based on the repository tree and README the server only reads categories, attributes, analytics, stock and turnover.
Can I install it via npx?
The package is not published to npm, you need to build the server from source with npm run build.
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