MCP and a living knowledge base for Ozon digital goods
Ozon MCP
An MCP server for one Ozon seller cabinet with a knowledge base on the digital-goods lifecycle: card, stock, order, activation code and delivery
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- It has confirmed changing digital-item stock in a real seller cabinet via an API write
- The documentation states intent to carry write access through the full order-shipment-code cycle
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/kvantexpert-ozon-mcpDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
This entry is high risk, so there is no one-click install. Review the code and add the config by hand.
Run in a terminal
claude mcp add --transport http kvantexpert-ozon-mcp https://ozon-mcp.kvantexpert.ru/mcpOr add to the file .mcp.json, in the project
{
"mcpServers": {
"kvantexpert-ozon-mcp": {
"type": "http",
"url": "https://ozon-mcp.kvantexpert.ru/mcp"
}
}
}If the file already exists, add the server inside the mcpServers key.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"kvantexpert-ozon-mcp": {
"url": "https://ozon-mcp.kvantexpert.ru/mcp"
}
}
}If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.
Run in a terminal
code --add-mcp '{"name":"kvantexpert-ozon-mcp","type":"http","url":"https://ozon-mcp.kvantexpert.ru/mcp"}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"kvantexpert-ozon-mcp": {
"type": "http",
"url": "https://ozon-mcp.kvantexpert.ru/mcp"
}
}
}If the file already exists, add the server inside the servers key.
Run in a terminal
codex mcp add kvantexpert-ozon-mcp --url https://ozon-mcp.kvantexpert.ru/mcpOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.kvantexpert-ozon-mcp]
url = "https://ozon-mcp.kvantexpert.ru/mcp"If the file already exists, append the block to the end.
Run in a terminal
gemini mcp add -s user -t http kvantexpert-ozon-mcp https://ozon-mcp.kvantexpert.ru/mcpOr add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"kvantexpert-ozon-mcp": {
"httpUrl": "https://ozon-mcp.kvantexpert.ru/mcp"
}
}
}If the file already exists, add the server inside the mcpServers key.
Add to the file ~/.config/devin/mcp_config.json, for all projects
{
"mcpServers": {
"kvantexpert-ozon-mcp": {
"serverUrl": "https://ozon-mcp.kvantexpert.ru/mcp"
}
}
}If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.
Formerly Windsurf.
Add to the file cline_mcp_settings.json, for all projects
{
"mcpServers": {
"kvantexpert-ozon-mcp": {
"type": "streamableHttp",
"url": "https://ozon-mcp.kvantexpert.ru/mcp"
}
}
}If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.
Add to the file .roo/mcp.json, in the project
{
"mcpServers": {
"kvantexpert-ozon-mcp": {
"type": "streamable-http",
"url": "https://ozon-mcp.kvantexpert.ru/mcp"
}
}
}If the file already exists, add the server inside the mcpServers key.
A fork of Roo Code, same .roo folders.
Add to the file opencode.json, in the project
{
"mcp": {
"kvantexpert-ozon-mcp": {
"type": "remote",
"url": "https://ozon-mcp.kvantexpert.ru/mcp"
}
}
}If the file already exists, add the server inside the mcp key.
Add to the file ~/.config/zed/settings.json, for all projects
{
"context_servers": {
"kvantexpert-ozon-mcp": {
"url": "https://ozon-mcp.kvantexpert.ru/mcp"
}
}
}If the file already exists, add the server inside the context_servers key.
Deploy your own server instance with your Ozon Seller and Performance keys in environment variables, never commit them to git, and follow the discover-read-validate-write-verify-document cycle before any write operation.
This is third-party code. Review the repository files before installing.
What it does
The project is both a working MCP server wired to one specific kvantexpert.ru seller cabinet, and a documented knowledge base in docs/ on how Ozon digital goods work: card lifecycle, characteristics and dictionaries, an API operation map, and the digital-delivery mechanics. Every new operation follows a discover-read-validate-write-verify-document cycle rather than a guess: on a reference card it has been confirmed that a digital item's stock actually flips from 0 to 1 through the MCP, and this is independently verified with a direct call to the Ozon API. The full order-shipment-code-delivery chain has not yet been proven on a real shipment and is honestly marked unverified in the docs.
Who it is for. For developers studying how publishing and delivering Ozon digital goods actually works through an MCP, including documented failed attempts.
Good fit when
- You need an example of a genuinely verified, not theoretical, path for creating an Ozon digital good
- You are interested in the discover-read-validate-write-verify-document methodology for risky API operations
- You want to deploy a similar server for your own seller cabinet
Not a fit when
- You are looking for a ready multi-tenant service: the public endpoint runs on the author's own account and cabinet, not yours
- You need a finished code-delivery-to-buyer chain: it isn't proven in practice yet
- You have no Ozon Seller and Performance keys of your own to deploy this for yourself
Example request
Check how the digital-good lifecycle in Ozon currently works per the project's documentationLimitations
The public MCP endpoint at kvantexpert.ru runs on the author's own account and credentials: it is not a multi-tenant service, but a personal working instance documented for continued development. Only the card-to-stock chain is confirmed, the full code delivery to a buyer (order-shipment-code-delivery) has not been proven on a real shipment. The README explicitly requires never publishing Client-Id, Api-Key, cookies, tokens or real digital codes to the repository.
How to disable. Disconnect the ozon-mcp.kvantexpert.ru server from your MCP client, or stop your own deployed instance.
MCP
- Transport
- http
- Authentication
- API key
Security check
- It has confirmed changing digital-item stock in a real seller cabinet via an API write
- The documentation states intent to carry write access through the full order-shipment-code cycle
README in short
The README describes the project as working documentation meant to be resumed a month or a year later with an AI assistant, gives the public MCP endpoint, a list of secrets never to publish, a reference digital-good card with confirmed and unconfirmed steps, the discover-read-validate-write-verify-document methodology, and a requirement to log both successful and negative test results in docs/.
FAQ
Can I connect to the public endpoint and use it for my own store?
No, the public https://ozon-mcp.kvantexpert.ru/mcp runs on the project author's own cabinet and keys, it does not accept your own credentials.
Is full digital code delivery to a buyer confirmed?
No, only the card-to-stock chain is confirmed, the full cycle through code delivery is honestly marked unverified in the docs.
Related
Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent
Yandex Kit skills for store management
kit-skills
Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex
YouGile MCP by Indalo
YouGile MCP
Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit
Bitrix24 portal MCP server
MCP-сервер портала Битрикс24
Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail