Ozon buyer-side MCP with delivery city selection
ozon-customer-mcp
A Docker MCP server for the Ozon buyer side: search, product cards, reviews, questions, sellers, categories, brands, and live delivery-city selection
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- Runs an anonymous session with no personal account login, only reads the public catalog
Install
Manual install
git clone https://github.com/Raleose/ozon-customer-mcp.git && cd ozon-customer-mcp && docker build -t ozon-customer-mcp:latest .Building the Docker image before connecting it to an MCP client.
This is third-party code. Review the repository files before installing.
What it does
The server keeps a Camoufox anti-detect browser session, passes the JS anti-bot challenge once, and then reads the internal composer-api as JSON without parsing HTML. Of its 17 tools, there is search with filters, a single card and a batch read of up to 40 cards at once, reviews and Q&A with sorting, the same product's offers from other sellers together with delivery dates, comparison of 2-8 products, a seller profile and catalog, a live category tree with no hardcoding, a brand showcase, and related products. A separate tool group manages the delivery city: by default the session is anonymous and set to Moscow, ozon_search_cities looks up a city through Ozon's own live Maps suggest, ozon_set_city switches it in 20-40 seconds, after which dates in ozon_product_offers reflect the chosen region.
Who it is for. For people who want an agent to have anonymous access to the Ozon catalog with delivery-region awareness, without logging into a personal account.
Good fit when
- You need Ozon search, comparison and product cards with delivery dates for a specific city
- You need a seller or brand catalog with no account login
- You are ready to run a Docker container with Camoufox per MCP session
Not a fit when
- You need personal account, cart or order access: the server only works anonymously
- You have no Docker or don't want to spend about 1 GB of shm on the container
- You need it to work with no proxy or Camoufox in regions where Ozon's anti-bot is aggressive
Example request
Find this product on Ozon, show alternatives from other sellers and delivery dates to KazanLimitations
Needs Docker and a container that stays alive for the MCP session, it self-terminates on idle after OZON_EXIT_IDLE_MS. The category for ozon_category_browse needs a real slug specifically from ozon_list_categories or ozon_search_filters: Ozon keys on the numeric id, not the string prefix, a guessed slug can open the wrong category. On a CAPTCHA or anti-bot block the README recommends a different IP or a Russian proxy, there is no built-in bypass beyond that.
How to disable. Remove the ozon-customer block from your MCP client config and stop the Docker container.
MCP
- Transport
- stdio
- Authentication
- not required
| Environment variables | |
|---|---|
| OZON_HEADLESS | Runs Camoufox headless, defaults to true |
| OZON_CHALLENGE_WAIT_MS | Wait time for the anti-bot challenge, defaults to 15000 ms |
Security check
- Runs an anonymous session with no personal account login, only reads the public catalog
README in short
The README lists all 17 tools in a table, explains the Camoufox-plus-internal-composer-api mechanism instead of HTML parsing, gives a delivery-city-change scenario example, a Docker quick start with an mcp.json example, a Node/Python bridge architecture diagram, and an environment variable table covering OZON_HEADLESS, OZON_GEOIP and OZON_CHALLENGE_WAIT_MS.
FAQ
Do you need an Ozon account?
No, the server runs an anonymous session with no login, defaulting to Moscow as the delivery city.
How do you find the correct category slug?
Only via ozon_list_categories or ozon_search_filters, never by guessing from a name: Ozon keys on the numeric id.
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