Ozon MCP Server

What ozon-mcp-server does

The ozon-mcp-server MCP server exposes Ozon marketplace operations to MCP-compatible AI clients. It covers both the Ozon Seller API and the Performance API, so an assistant can work with catalog data and seller workflows alongside paid advertising. The project is designed for sellers managing multiple stores: calls identify the target shop with a shop_id.

Its 156 tools are organized around common marketplace tasks. These include promotions, discounts, pricing, competitor price indexes, automatic pricing strategies, sponsored-placement campaigns, cost-per-order advertising, products, stock, media, orders, fulfillment, returns, reviews, buyer questions, chats, reports, finance, analytics, ratings, notifications, company details, and store discovery. Diagnostics tools check Ozon API availability and detect degradation.

How it works

A local installation communicates over stdio, which suits clients that launch MCP processes directly. The Docker and web installation also provides an SSE endpoint at /sse; clients that do not support SSE directly can use the mcp-remote bridge. The web application includes a dashboard, store management pages, health information, and API diagnostics.

Each configured shop has a handle, display name, and Ozon credentials. Seller API access uses a Client-Id and API key. Performance API access uses a Client-Id and Client-Secret. The server stores shop information, encrypted keys, call statistics, and diagnostic history in its configured data directory. The tool catalog is generated from the server’s tool definitions and is also available through the MCP tools/list method.

Setup and configuration

For a direct local setup, install the package with uvx ozon-mcp-server or install it with pip and run ozon-mcp. The stdio configuration can provide OZON_CLIENT_ID, OZON_API_KEY, and DATA_DIR. DATA_DIR must point to a writable location; its documented default is /data.

For the browser dashboard, clone the repository, create a .env file from .env.example, and start the Docker Compose deployment. It serves on port 8000 and persists data in the ozon_data volume. Add shops through /shops, where the credentials can be tested with a live Ozon request. Set MCP_AUTH_TOKEN when the service may be reachable by other users. The dashboard and installation guides are in Russian, although the supplied JSON configuration is language-neutral.

Tools and capabilities

The ozon-mcp-server MCP server groups its tools into these supported areas:

• Promotions, discount requests, price controls, and pricing strategies
• CPC and pay-per-order advertising, including bids, budgets, and statistics
• Product listings, attributes, inventory, imports, bulk updates, media, and certificates
• FBS and FBO orders, packing, labels, cancellations, supplies, and delivery workflows
• Returns, rFBS claims, reviews, replies, buyer questions, and chats
• Warehouses, reports, balances, transactions, accruals, settlements, and cash flow
• SKU analytics, stock turnover, search positions, seller ratings, and diagnostics

Limitations and notes

The available client guides are Russian-only. SSE compatibility varies by client: Claude Desktop and OpenAI Codex CLI require the mcp-remote bridge, while Zed support is unconfirmed and the bridge is recommended. Ozon credentials and API availability still determine which operations succeed. The repository describes the tool as maintained according to the author’s ongoing use rather than a stated support commitment.