ozon

This MCP server implements a set of tools to interact with Ozon marketplace data via an HTTP MCP streamable interface. It exposes tools to search products (ozon_search), fetch detailed product information (ozon_product_details), retrieve multiple products at once (ozon_products_list), set delivery location (ozon_set_location), and query available filters and categories (ozon_get_filters and ozon_get_categories). The server uses Playwright to automate a headless browser, maintaining a persistent session to bypass antibot protections and to extract structured data from Ozon pages. You can access the MCP endpoint at /mcp, subscribe to the SSE stream for status, and issue JSON-RPC calls to request tool results. The provided examples show how to perform a search or fetch product details by sending a JSON-RPC request with the appropriate tool name and arguments.

Prerequisites:

• Node.js installed (compatibility with npm/yarn used by the project)
• Git installed
• Optional: Docker if you prefer containerized deployment

Installation steps (Node.js option):

1. Clone the repository git clone https://github.com/eduard256/ozon-mcp-server.git cd ozon-mcp-server

2. Install dependencies npm install

3. Install Playwright browsers (Chromium in particular) and dependencies npx playwright install chromium npx playwright install-deps chromium

4. Start the server npm start

Alternative (Docker):

1. Clone the repository and navigate to it git clone https://github.com/eduard256/ozon-mcp-server.git cd ozon-mcp-server

2. Use Docker Compose to run docker-compose up -d

Notes:

• The server may take a little longer on the first request due to browser initialization.
• Ensure environment variable PORT is set if you customize the port; the default is 3001 as described in the configuration.
• If you run behind a firewall, ensure the chosen port is accessible from clients.

Optional: If you prefer to run via a published npm package (if available in the future), replace the node command with the package execution as appropriate.

Tips and caveats:

• First request may take longer due to browser initialization.
• The system relies on natural navigation to bypass anti-bot measures; avoid very rapid successive requests.
• If Ozon changes their anti-bot protections, you may need to update scripts or selectors used for data extraction.
• The environment variable PORT controls the HTTP server port; adjust as needed for your deployment environment.
• For remote Claude Desktop integration, you can point Claude at http://<server_ip>:3001/mcp to use the tools directly.
• Use the provided tools in moderation to avoid triggering rate limits or blocks on Ozon’s site.