Production-grade Ozon Seller MCP server
Ozon Seller MCP Server
An MCP server for the Ozon Seller API with a PostgreSQL audit log, Redis caching and rate limits, a circuit breaker and a no-key demo mode
- 3 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Bulk-updates product prices and stock in the live account
- Stores credentials and a log of every operation in its own PostgreSQL database
A similar tool with a larger community: Ozon MCP Server for buyer-side search, 88 ★ on the repository
Install
- Works in
- Services
Manual install
docker compose up -dBrings up the server together with Redis and PostgreSQL; keys go in .env.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Bulk-updates product prices and stock in the live account
- Stores credentials and a log of every operation in its own PostgreSQL database
This is third-party code. Review the repository files before installing.
What it does
The server provides 13 tools for the Ozon Seller API: product cards, warehouse stock, bulk price and stock updates, archiving, FBS and FBO orders, sales analytics, financial reports and a warehouse list. Around the API sits a six-layer defense: input validation, credential masking in logs, rate limiting, a PostgreSQL audit log of every call with response time and trace ID, a circuit breaker that cuts off Ozon calls after a run of failures, and SSRF protection. Write tools are marked destructiveHint, so clients like Claude Desktop prompt for confirmation before running them. A DEMO_MODE=true mode ships mock data and needs no Ozon keys, Redis or PostgreSQL at all.
Who it is for. For teams that need not just a working server but a production setup with audit logging and defenses around the Ozon Seller API.
Good fit when
- You need an audit log of every Ozon Seller API call for later review
- You need rate limiting and automatic cutoff during Ozon outages
- You want to try the tools on mock data first, without a real Ozon account
Not a fit when
- You want a simple server with no infrastructure: full operation here needs PostgreSQL and Redis (outside demo mode)
- You do not want to run Docker Compose: a local uv run is possible, but the README is built around docker compose up
Example request
Show this week's sales analytics and update stock for products the warehouse shows as zeroMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
OZON_CLIENT_IDrequired- Seller Client Id from the Ozon Seller dashboard.
OZON_API_KEYrequired, secret- Seller Api Key from the same pair.
POSTGRES_PASSWORDrequired, secret- Password for the audit log database, required with no default.
DEMO_MODE- true runs the server on mock data with no real keys or infrastructure.
Limitations
Full operation needs PostgreSQL and Redis running, which is noticeably heavier than single-file alternatives. POSTGRES_PASSWORD is required with no default value. The README calls the project the first MCP server for the Ozon Seller API, though several independent implementations already exist.
How to disable. Stop docker compose (docker compose down) and remove the server from your MCP client config.
FAQ
Can I try it without Ozon keys?
Yes, DEMO_MODE=true gives five products, four orders, three warehouses and analytics on mock data, with no Ozon, Redis or PostgreSQL needed.
Will it confirm before changing data?
Yes, write tools are marked destructiveHint, and MCP clients like Claude Desktop show a confirmation prompt.
Discussion
No questions or reviews yet.
Related
All Ozon toolsOzon MCP
ozon-mcp
MCP server for Ozon Seller API and Performance API: method search, calls guarded against accidental writes and ready analytics workflows
Ozon MCP Server for Seller and Performance APIs
Ozon MCP Server
MCP server for the Ozon Seller and Performance APIs: prices, promotions, ads, orders, returns and finance across several stores
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
Ozon Seller MCP server
mcp-ozon-seller
MCP server for Ozon Seller API: products, prices, stocks, FBO and FBS orders, seller analytics and finances
An MCP server with 9 read-only tools over the Ozon Seller API v3: products, FBS and FBO orders, analytics, finance and returns
Ozon Seller MCP server (Go)
ozon-seller-mcp
A Go MCP server for the Ozon Seller API with 68 tools: catalog, prices, stock, promotions, analytics, finance, FBS and FBO, read-only by default
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Production-grade Ozon Seller MCP server (this card) | no | API key | 3 | |
| Ozon Seller MCP server | no | API key | 7 | products, prices, orders |
| Ozon Seller API MCP server | no | API key | 4 | FBS and stock |
| Ozon Seller MCP server (Go) | no | API key | 0 | 68 tools |
README in short
The English README, with an architecture diagram, shows six defense layers, OWASP MCP Top 10 compliance, a Redis cache with write-time invalidation, and a PostgreSQL audit log. It gives a table of the 13 tools with read/write type and the matching Ozon endpoint, docker compose and local uv run instructions, and a demo mode with no real keys.