Ozon seller price monitoring with auto-login MCP
OZON MCP Server
A Playwright-based MCP server for the Ozon seller cabinet: automatic login via a QQ Mail code and a check for marketing-action prices below the minimum
- 0 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Automatically logs into the Ozon seller cabinet and stores a mail app code in .env
- Keeps a local browser profile with an active account session
A similar tool with a larger community: Ozon MCP Server for buyer-side search, 88 ★ on the repository
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/oychao1988-ozon-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Automatically logs into the Ozon seller cabinet and stores a mail app code in .env
- Keeps a local browser profile with an active account session
This is third-party code. Review the repository files before installing.
What it does
The server keeps a Playwright Chrome session and, via the login-with-email-code tool, signs itself into seller.ozon.ru by fetching a one-time code from a QQ Mail inbox over IMAP with a supplied app password. The get-marketing-actions tool reads product data from current marketing actions one page or all pages at a time, to find items priced below the allowed minimum. The same functionality is available outside the MCP protocol through a standalone cli.py, with CSV or JSON export and a headless mode. The Chrome profile is saved locally after the first login so verification doesn't repeat.
Who it is for. For Ozon sellers using QQ Mail who need a quick check on whether a product's marketing-action price has dropped below the allowed minimum.
Good fit when
- You have a QQ Mail account tied to Ozon with IMAP enabled
- You need to regularly check marketing-action prices in your cabinet
- You are fine logging in via an email code rather than a direct password
Not a fit when
- Your Ozon-linked mailbox is not on QQ: the login flow is built specifically for it
- You don't want an email app password sitting in .env on disk
- You need to change something in the cabinet rather than just view action prices: the server doesn't do that
Example request
Log into my Ozon cabinet and show marketing-action products priced below the minimumMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
ozon_usernamerequired, secret- The QQ Mail login tied to the Ozon account
qq_imap_auth_coderequired, secret- The 16-digit QQ Mail app authorization code for IMAP
Limitations
The README is in Chinese and English. Login is hard-tied to QQ Mail and a 16-digit app code fetched over IMAP/SMTP, it won't work with other mail providers. The server stores a saved Chrome session profile locally, and the README explicitly warns not to commit .env or chrome-profile/ to git.
How to disable. Run claude mcp remove ozon and delete the local .env and chrome-profile/ with the saved session.
FAQ
Can the server change a product's price?
No, per the README only login-with-email-code and get-marketing-actions are available, neither changes cabinet data.
Is QQ Mail mandatory?
Yes, auto-login is built around fetching a code from a QQ Mail inbox over IMAP, the README describes no alternative for other mail services.
Discussion
No questions or reviews yet.
Related
All Ozon toolsOzon buyer account MCP
Ozon MCP
An MCP server for one ozon.ru buyer account: orders, cart, favorites, selections, and, when explicitly allowed, placing and paying for an order
Ozon MCP Server for buyer-side search
Ozon MCP Server
Buyer-side Ozon MCP server: product search, product pages with prices and stock, customer reviews
Unofficial buyer-side Ozon MCP server: product search, prices, specs and reviews without Seller API keys
An MCP server reads the Ozon storefront as an anonymous buyer: paged search, three labelled prices, reviews and a comparison of up to 20 products
Ozon MCP
ozon-mcp
MCP server for Ozon Seller API and Performance API: method search, calls guarded against accidental writes and ready analytics workflows
An MCP server with 9 read-only tools over the Ozon Seller API v3: products, FBS and FBO orders, analytics, finance and returns
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Ozon seller price monitoring with auto-login (this card) | no | API key | 0 | |
| Ozon MCP | no | API key | 26 | Seller and Performance API for agents |
| Ozon buyer account MCP | no | not required | 9 | orders and cart |
README in short
The Chinese and English README describes installing via PyPI or from source, setting up .env with the login and a 16-digit QQ app code, connecting to Claude Code and Cursor, both MCP tools with call examples, the equivalent cli.py with pagination and output flags, and a changelog for versions 0.1.0 and 0.1.2.