Read-only Ozon and Wildberries MCP in Rust
MCP Ozon
A Rust MCP server for Ozon Seller, Ozon Performance and part of Wildberries analytics: 76 read-only tools, no data-changing method at all
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Reads financial transactions, orders and ad spend for both accounts
- Stores Ozon keys and the Wildberries token on an always-on server
Install
Manual install
docker compose up -d --buildPrimary method: a persistent service for ChatGPT access via Secure MCP Tunnel.
This is third-party code. Review the repository files before installing.
What it does
The server gives ChatGPT and other MCP clients tools for Ozon stock, prices, orders, shipments, returns, finance, rating, reviews, questions and ad statistics, plus separate Wildberries analytics, stock and ad tools. The server has no write method at all: access to marketplace APIs is restricted by an explicit allowlist of exact method-plus-path pairs at the HTTP client level, not just in the tool description, so a forgotten check in a tool's code can't open a write. It supports multiple stores and role-based access (a manager sees only their own cabinet), and runs either as a Docker service for ChatGPT via Secure MCP Tunnel or as an stdio process for Claude Desktop.
Who it is for. For Ozon and Wildberries sellers who want operational analytics in ChatGPT or another MCP client with no risk of accidentally changing anything in the cabinet.
Good fit when
- You need Ozon and partial Wildberries stock, order, finance and ad analytics from ChatGPT
- It matters that the server has no physical ability to change anything in the cabinet
- You need access for several managers, each limited to their own store
Not a fit when
- You need to change prices, stock or orders: the server rules this out by design
- You have no separate server or VPS to run it persistently and tunnel to ChatGPT
- You are not ready to deal with Docker, JWT/OIDC and allowlist configuration
Example request
Show FBW and FBS stock across Wildberries warehouses and cross-check it against recent salesLimitations
The setup targets an always-on server (VPS, Docker Compose, systemd watchdog), not a one-off local run. WB ad tools need a token with the Promotion category and Read Only level, WB search analytics needs an active Джем subscription. The README has no single project tree in one place, details are spread across many docs/*.md files.
How to disable. Stop the container with docker compose down, remove the LaunchAgent/watchdog, and delete the MCP connection from ChatGPT or Claude Desktop.
MCP
- Transport
- stdio, http
- Authentication
- OAuth
| Environment variables | |
|---|---|
| EXAMPLE_OZON_CLIENT_ID secret | Ozon Seller store Client-Id |
| EXAMPLE_OZON_API_KEY secret | Ozon Seller store Api-Key |
| EXAMPLE_WB_API_TOKEN secret | Read Only Wildberries token for the configured account |
Security check
- Reads financial transactions, orders and ad spend for both accounts
- Stores Ozon keys and the Wildberries token on an always-on server
README in short
The README covers a hardened local run via a watchdog and provenance-verified releases, .env and config/access.json setup, a list of 76 stable read-only Ozon and WB tools, the read-only enforcement points at the client level, role and resource limits, running for ChatGPT via Docker and Secure MCP Tunnel, JWT/OIDC for shared access, and local verification via MCP Inspector.
FAQ
Can the server change a price or stock level?
No, the server has no write method at all, API access is restricted by an allowlist of exact read-only paths at the HTTP client level.
Do I need an always-on server?
Yes, the standard setup is a Docker container with a watchdog and a tunnel to ChatGPT, a one-off local run is only meant for development via cargo run.
Related
Official DataLens (Yandex) skills for Claude Code, Codex and OpenCode: SDK, HTML reports and RLS resolution
A Yandex Metrika MCP server generated from the API spec: 108 methods, 10 tools declared by default, transparent filters and response metadata
An open MCP server and agent skill set for SEO: keyword research, competitors, backlinks and site audits powered by DataForSEO
A Claude Code plugin for SEO audits: technical SEO, E-E-A-T, schema, local and AI search via parallel subagents