Ozon MCP Server
Buyer-side Ozon MCP server: product search, product pages with prices and stock, customer reviews
Install
docker run -i --rm --init --shm-size=1g eduard256/ozon-mcp-server:latestUse this as the command and args in your MCP client config. Per-client guides are in the repository's docs folder.
This is third-party code. Review the repository files before installing.
What it does
The server gives the agent three tools: product search, reading a product page by SKU or link, and reading reviews. Ozon has no public buyer API, so the server keeps one headless Chromium on the site and pulls JSON from the page's internal API instead of parsing HTML. Prices come as numbers, and product pages include card and non-card prices, seller, attributes and description. The browser closes after idle time and restarts itself when the session expires.
Who it is for. For sellers and analysts watching competitor prices and reviews on Ozon, and for shoppers comparing products.
Good fit when
- You need a quick comparison of prices and ratings for similar Ozon products
- You need complaints gathered from reviews of a competitor's product
- You need stock and seller info from a product link
Not a fit when
- You need data from your own seller account: use the Seller API for that
- You need regular bulk data collection at scale
Example request
Find wireless earbuds under 5000 rubles on Ozon rated above 4.7 and show the three cheapestLimitations
The server relies on the site's internal API, not an official one: any change on Ozon's side can break it, and automated collection may conflict with the marketplace's terms. The first request takes about 12 seconds while the browser passes the site check. It needs Docker with memory for Chromium, or Node.js 20 with Playwright. The license is stated only in package.json.
How to disable. Remove the server block from your MCP client config and delete the eduard256/ozon-mcp-server Docker image.
MCP
- Transport
- stdio
- Authentication
- not required
Security check
- Runs a headless browser that visits the Ozon site
- Automated data collection may conflict with the marketplace's terms
README in short
The Russian README describes three tools and explains why the server uses a browser: Ozon has no public buyer API. The main way to run it is a Docker Hub image with required flags. Each client, from Claude Code and Cursor to Zed and Gemini CLI, has its own install file. It also outlines the module layout and gives commands for local development and offline parser tests.
FAQ
Do I need an Ozon API key?
No. The server acts as a shopper on the site and uses no seller account keys.
Why the --init and --shm-size flags?
The first lets Chromium shut down cleanly, the second gives the browser memory. Without them the container is unstable.
Related
CLI, skill and Python library for browser control: the agent clicks, fills forms and reads pages over CDP
A skill that gathers the last 30 days of discussion on a topic from Reddit, X, YouTube, HN, Polymarket and GitHub into one brief
The Chrome DevTools team's official MCP server: the agent drives a live Chrome, reads network and console, and records performance traces
A fast Rust CLI for agent browser automation: accessibility snapshots with element refs, an MCP server and skills