MCP server for Ozon Seller API
mcp-server-ozon-seller
An MCP server, CLI tool and Pydantic models for the full Ozon Seller API: 111 actions across products, shipments, finance and reviews via search and execute
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 create and update products, and change prices and stock
- Can cancel FBS shipments and run other write actions from the catalog of 111
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/mcp-server-ozon-sellerDetects 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-seller -- uvx mcp-server-ozon-seller==0.3.1Or add to the file .mcp.json, in the project
{
"mcpServers": {
"ozon-seller": {
"command": "uvx",
"args": [
"mcp-server-ozon-seller==0.3.1"
],
"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, requiredOZON_API_KEYsecret, required
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": [
"mcp-server-ozon-seller==0.3.1"
],
"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, requiredOZON_API_KEYsecret, required
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":["mcp-server-ozon-seller==0.3.1"],"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": [
"mcp-server-ozon-seller==0.3.1"
],
"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, requiredOZON_API_KEYsecret, required
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 mcp-server-ozon-seller==0.3.1Or add to the file ~/.codex/config.toml, for all projects
[mcp_servers.ozon-seller]
command = "uvx"
args = ["mcp-server-ozon-seller==0.3.1"]
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, requiredOZON_API_KEYsecret, required
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-seller uvx mcp-server-ozon-seller==0.3.1Or add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"ozon-seller": {
"command": "uvx",
"args": [
"mcp-server-ozon-seller==0.3.1"
],
"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, requiredOZON_API_KEYsecret, required
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": [
"mcp-server-ozon-seller==0.3.1"
],
"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, requiredOZON_API_KEYsecret, required
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": [
"mcp-server-ozon-seller==0.3.1"
],
"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, requiredOZON_API_KEYsecret, required
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": [
"mcp-server-ozon-seller==0.3.1"
],
"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, requiredOZON_API_KEYsecret, required
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",
"mcp-server-ozon-seller==0.3.1"
],
"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, requiredOZON_API_KEYsecret, required
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": [
"mcp-server-ozon-seller==0.3.1"
],
"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, requiredOZON_API_KEYsecret, required
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": [
"mcp-server-ozon-seller==0.3.1"
],
"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, requiredOZON_API_KEYsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Get a Client-Id and Api-Key in Ozon Seller (Settings → API keys), then run claude mcp add ozon-seller -e OZON_CLIENT_ID=... -e OZON_API_KEY=... -- uvx mcp-server-ozon-seller.
Other ways from the author
claude mcp add ozon-seller -e OZON_CLIENT_ID=ваш_client_id -e OZON_API_KEY=ваш_api_key -- uvx mcp-server-ozon-sellerMethod via uvx, no package install needed.
This is third-party code. Review the repository files before installing.
What it does
Instead of 111 separate MCP tools the server exposes three: ozon_search finds the right action from a natural-language description, ozon_execute runs it by ID with parameters, ozon_execute_file does the same while downloading a file (for example an acceptance certificate). It covers products, fbs, fbo, categories, finance, analytics, warehouses, returns, chats, promos, strategies, rating, reports, reviews, questions, cancellations, certificates, barcodes and brands, including write actions: creating and updating products, prices, stock, cancelling shipments. The same package also works as the ozon-seller-cli command-line tool and as a library of typed Pydantic API models.
Who it is for. For Ozon sellers and developers who need full Seller API access from an agent, a terminal, or their own Python code.
Good fit when
- You need access to all Seller API sections, not a subset
- You need to manage prices, stock, product cards or FBS/FBO shipments from an agent
- You want the same functionality as a CLI for scripts too
Not a fit when
- You need read-only access with no risk of accidental changes
- You have no Ozon Seller key with the right permissions
- You dislike the search-plus-execute pattern instead of separate named tools
Example request
Cancel FBS shipment 12345678-0001-1 and show financial transactions for AprilLimitations
All data and keys stay on the user's machine, the server never forwards them anywhere. You need an Ozon Seller key (Client-Id and Api-Key) with the right permissions, and a number of the 111 actions change data in the cabinet. The search-plus-execute pattern requires the agent to look up an action's ID first rather than calling it directly by name.
How to disable. Run claude mcp remove ozon-seller or delete the server from your MCP client configuration.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| OZON_CLIENT_ID required, secret | Client-Id from the Ozon Seller cabinet |
| OZON_API_KEY required, secret | Api-Key from the Ozon Seller cabinet |
Security check
- Can create and update products, and change prices and stock
- Can cancel FBS shipments and run other write actions from the catalog of 111
README in short
The README lists 111 actions across 19 domains with links to detailed docs/*.md files, shows connecting to Claude Code and Claude Desktop via uvx or pip, CLI command examples for products, FBS, FBO, finance and returns, and an example of using the Pydantic models in custom Python code.
FAQ
Why only three tools instead of 111?
The server uses a search + execute pattern: ozon_search finds the right action, ozon_execute runs it, which is more compact for an agent than 111 separate calls.
Can it be used without an MCP client?
Yes, the same package works as the ozon-seller-cli command-line tool with the same commands and JSON output.
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