Ozon MCP Server
MCP server for the Ozon Seller and Performance APIs: prices, promotions, ads, orders, returns and finance across several stores
Install
uvx ozon-mcp-serverRuns over stdio. Alternatively pip install ozon-mcp-server, then ozon-mcp.
This is third-party code. Review the repository files before installing.
What it does
The server lets an agent run an Ozon store: products and stock, prices and strategies, promotions, FBS and FBO orders, returns, reviews and chats, reports and finance. Unlike many alternatives it also covers the Performance API for ads: campaigns, bids, budgets and statistics. Every call takes a shop_id, so one rule can apply to several seller accounts. In Docker mode there is a Russian web dashboard with call stats, key management and diagnostics that flag broken Ozon endpoints early.
Who it is for. Sellers and agencies running one or more Ozon stores.
Good fit when
- You want to compare the price index with competitors and adjust prices
- You need weekly ad spend and want to stop losing campaigns
- You need to answer new reviews or handle rFBS returns
- The same rules must apply to several seller accounts
Not a fit when
- You only need read access and the agent must not change prices or ads
- Your store is on Wildberries: the author has a separate server for it
Example request
Which products in store alpha is Ozon planning to add to promotions, and where is the price index worse than competitors?Limitations
Requires a Seller API Client-Id and API key, plus a separate Performance API Client-Id and Client-Secret for ads. All accounts reach Ozon from one IP, so many stores can hit rate limits. The web UI and /api are not token-protected, so port 8000 must not be exposed to the internet. Client guides in docs are Russian only. The author updates it for his own needs.
How to disable. Remove the server from your client config, for example claude mcp remove ozon. Stop the Docker version with docker compose down; data stays in the ozon_data volume.
MCP
- Transport
- stdio, sse
- Authentication
- API key
| Environment variables | |
|---|---|
| OZON_CLIENT_ID | Seller API Client-Id for stdio mode |
| OZON_API_KEY secret | Seller API key for stdio mode |
| DATA_DIR | Folder for stores, keys and stats, defaults to /data |
| MCP_AUTH_TOKEN secret | Token protecting the SSE endpoint in Docker mode |
Security check
- Changes prices, promotions, ad bids and budgets in live seller accounts
- Handles financial data and keys for several stores
- The unauthenticated dashboard lets anyone who can reach the port add stores
README in short
The README, available in English, Russian and Chinese, lists tool groups from promotions and prices to finance and seller rating. It offers stdio launch via uvx or pip and a Docker option with a dashboard and SSE on port 8000. Each popular client has its own guide with ready JSON. It covers multi-store use, key encryption, per-IP limits and exactly what MCP_AUTH_TOKEN protects. MIT license.
FAQ
Where are store keys kept?
In shops.json inside DATA_DIR, encrypted with a Fernet key from the same folder. When moving servers copy the whole folder or volume, or the encryption key is lost.
Is Docker required?
No, uvx ozon-mcp-server runs over stdio. Docker is only needed for the dashboard, diagnostics and SSE.
Related
Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent
E-Commerce Skills
E-Commerce Skills by Nexscope
A large set of text skills for Amazon, Shopify, eBay, Etsy, TikTok Shop and Walmart sellers: pricing, listings, ads and growth
153 cross-border e-commerce skills via the LinkFox API: Amazon, Ozon, TikTok Shop, 1688, keywords, ads and patents
An MCP server for Bitrix24 CRM contacts and deals via an inbound webhook: search, lists and deal stage changes