OZON MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ozon_username | Yes | Your OZON account username (QQ email address) | |
| ozon_login_url | No | The OZON login URL, default is https://sso.ozon.ru/auth/ozonid?localization_language_code=zh-Hans | |
| qq_imap_auth_code | Yes | 16-digit QQ email IMAP authorization code for reading verification codes | |
| chrome_profile_path | No | Path to Chrome profile directory, default is ./chrome-profile/ |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| login-with-email-codeB | 登录 OZON 卖家后台，使用 QQ 邮箱接收验证码 |
| get-marketing-actionsB | 获取营销活动数据（产品名称、SKU、当前价格、最低价） |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools serve entirely different purposes: one handles authentication and the other retrieves marketing data. There is no functional overlap, making it trivial for an agent to distinguish between them.
Both tool names use hyphens and follow a verb-noun structure. However, one uses 'get' with a noun phrase while the other uses 'login' with a prepositional phrase, which is a minor inconsistency in verb pattern.
With only two tools, the server feels underpopulated for its apparent scope as an OZON seller platform. Most servers in this domain would require a dozen or more tools to cover basic operations.
The server severely lacks expected functionality. After logging in, users would need tools for products, orders, campaigns, and more. A single data retrieval tool leaves massive gaps in the tool surface.