A strictly read-only MCP for the Ozon seller cabinet
Ozon Readonly MCP
An MCP server for ChatGPT and Cursor: products, orders, finance, ads and reviews from the Ozon seller cabinet, with no way to change the cabinet
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 from the seller cabinet
- Runs as an always-on service on a VPS with Ozon keys in .env
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/ozon-readonly-mcpDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Assembled automatically, review before installing.
Run in a terminal
claude mcp add --transport stdio --env 'OZON_SELLER_KEY=<your OZON_SELLER_KEY>' --env 'OZON_PERFORMANCE_KEY=<your OZON_PERFORMANCE_KEY>' 'ozon readonly mcp' -- nodeOr add to the file .mcp.json, in the project
{
"mcpServers": {
"ozon readonly mcp": {
"command": "node",
"args": [],
"env": {
"OZON_SELLER_KEY": "<your OZON_SELLER_KEY>",
"OZON_PERFORMANCE_KEY": "<your OZON_PERFORMANCE_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
OZON_SELLER_KEYsecret, required- API ключ продавца Ozon
OZON_PERFORMANCE_KEYsecret, required- API ключ Performance Ozon
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"ozon readonly mcp": {
"command": "node",
"args": [],
"env": {
"OZON_SELLER_KEY": "<your OZON_SELLER_KEY>",
"OZON_PERFORMANCE_KEY": "<your OZON_PERFORMANCE_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.
Keys and settings
OZON_SELLER_KEYsecret, required- API ключ продавца Ozon
OZON_PERFORMANCE_KEYsecret, required- API ключ Performance Ozon
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Run in a terminal
code --add-mcp '{"name":"ozon readonly mcp","type":"stdio","command":"node","args":[],"env":{"OZON_SELLER_KEY":"<your OZON_SELLER_KEY>","OZON_PERFORMANCE_KEY":"<your OZON_PERFORMANCE_KEY>"}}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"ozon readonly mcp": {
"type": "stdio",
"command": "node",
"args": [],
"env": {
"OZON_SELLER_KEY": "<your OZON_SELLER_KEY>",
"OZON_PERFORMANCE_KEY": "<your OZON_PERFORMANCE_KEY>"
}
}
}
}If the file already exists, add the server inside the servers key.
Keys and settings
OZON_SELLER_KEYsecret, required- API ключ продавца Ozon
OZON_PERFORMANCE_KEYsecret, required- API ключ Performance Ozon
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run in a terminal
codex mcp add 'ozon readonly mcp' --env 'OZON_SELLER_KEY=<your OZON_SELLER_KEY>' --env 'OZON_PERFORMANCE_KEY=<your OZON_PERFORMANCE_KEY>' -- nodeOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers."ozon readonly mcp"]
command = "node"
args = []
env = { OZON_SELLER_KEY = "<your OZON_SELLER_KEY>", OZON_PERFORMANCE_KEY = "<your OZON_PERFORMANCE_KEY>" }If the file already exists, append the block to the end.
Keys and settings
OZON_SELLER_KEYsecret, required- API ключ продавца Ozon
OZON_PERFORMANCE_KEYsecret, required- API ключ Performance Ozon
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run in a terminal
gemini mcp add -s user -e 'OZON_SELLER_KEY=<your OZON_SELLER_KEY>' -e 'OZON_PERFORMANCE_KEY=<your OZON_PERFORMANCE_KEY>' 'ozon readonly mcp' nodeOr add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"ozon readonly mcp": {
"command": "node",
"args": [],
"env": {
"OZON_SELLER_KEY": "<your OZON_SELLER_KEY>",
"OZON_PERFORMANCE_KEY": "<your OZON_PERFORMANCE_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
OZON_SELLER_KEYsecret, required- API ключ продавца Ozon
OZON_PERFORMANCE_KEYsecret, required- API ключ Performance Ozon
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/devin/mcp_config.json, for all projects
{
"mcpServers": {
"ozon readonly mcp": {
"command": "node",
"args": [],
"env": {
"OZON_SELLER_KEY": "<your OZON_SELLER_KEY>",
"OZON_PERFORMANCE_KEY": "<your OZON_PERFORMANCE_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.
Keys and settings
OZON_SELLER_KEYsecret, required- API ключ продавца Ozon
OZON_PERFORMANCE_KEYsecret, required- API ключ Performance Ozon
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Formerly Windsurf.
Add to the file cline_mcp_settings.json, for all projects
{
"mcpServers": {
"ozon readonly mcp": {
"command": "node",
"args": [],
"env": {
"OZON_SELLER_KEY": "<your OZON_SELLER_KEY>",
"OZON_PERFORMANCE_KEY": "<your OZON_PERFORMANCE_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.
Keys and settings
OZON_SELLER_KEYsecret, required- API ключ продавца Ozon
OZON_PERFORMANCE_KEYsecret, required- API ключ Performance Ozon
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .roo/mcp.json, in the project
{
"mcpServers": {
"ozon readonly mcp": {
"command": "node",
"args": [],
"env": {
"OZON_SELLER_KEY": "<your OZON_SELLER_KEY>",
"OZON_PERFORMANCE_KEY": "<your OZON_PERFORMANCE_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
OZON_SELLER_KEYsecret, required- API ключ продавца Ozon
OZON_PERFORMANCE_KEYsecret, required- API ключ Performance Ozon
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
A fork of Roo Code, same .roo folders.
Add to the file opencode.json, in the project
{
"mcp": {
"ozon readonly mcp": {
"type": "local",
"command": [
"node"
],
"environment": {
"OZON_SELLER_KEY": "<your OZON_SELLER_KEY>",
"OZON_PERFORMANCE_KEY": "<your OZON_PERFORMANCE_KEY>"
}
}
}
}If the file already exists, add the server inside the mcp key.
Keys and settings
OZON_SELLER_KEYsecret, required- API ключ продавца Ozon
OZON_PERFORMANCE_KEYsecret, required- API ключ Performance Ozon
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/zed/settings.json, for all projects
{
"context_servers": {
"ozon readonly mcp": {
"command": "node",
"args": [],
"env": {
"OZON_SELLER_KEY": "<your OZON_SELLER_KEY>",
"OZON_PERFORMANCE_KEY": "<your OZON_PERFORMANCE_KEY>"
}
}
}
}If the file already exists, add the server inside the context_servers key.
Keys and settings
OZON_SELLER_KEYsecret, required- API ключ продавца Ozon
OZON_PERFORMANCE_KEYsecret, required- API ключ Performance Ozon
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .codeassistant/mcp.json, in the project
{
"mcpServers": {
"ozon readonly mcp": {
"command": "node",
"args": [],
"env": {
"OZON_SELLER_KEY": "<your OZON_SELLER_KEY>",
"OZON_PERFORMANCE_KEY": "<your OZON_PERFORMANCE_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
OZON_SELLER_KEYsecret, required- API ключ продавца Ozon
OZON_PERFORMANCE_KEYsecret, required- API ключ Performance Ozon
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Deploy the server on an Ubuntu VPS following DEPLOY.md, set the Ozon keys in .env, for ChatGPT connect via OAuth with the MCP login and password, for Cursor run it locally over stdio.
Other ways from the author
git clone https://github.com/zimuspro156-lab/mcp-ozon-readonly.git && cd mcp-ozon-readonly && npm ciInstalling dependencies before deploying per DEPLOY.md.
This is third-party code. Review the repository files before installing.
What it does
The server allows only 268 read operations out of the 511 available in the Ozon Seller and Performance API, everything else is excluded at the catalog level regardless of the key's own permissions. Fifteen tools cover product cards, FBO/FBS/rFBS orders with cancellation reasons, view-only supply orders and slots, returns without approve/reject, financial transactions and realization reports, sales and turnover analytics, ad campaigns and Performance API statistics, read-only reviews, questions and chats, promotions, candidates and seller rating. For ChatGPT the server is deployed on an Ubuntu VPS and connects via OAuth with an MCP login and password, not Ozon keys, behind a Cloudflare Tunnel; for Cursor a local stdio run is available.
Who it is for. For Ozon sellers who want operational analytics in ChatGPT or Cursor and need the assistant to be technically unable to change anything in the cabinet.
Good fit when
- You need to review Ozon products, orders, finance and ads from ChatGPT or Cursor
- You need the operation limit enforced at the catalog level, not just described in a tool's text
- You are ready to deploy the server on your own Ubuntu VPS
Not a fit when
- You need to change prices, stock, reply to reviews or approve returns: the server excludes all of that entirely
- You have no separate VPS for a persistent run: local stdio is available only for Cursor
- You lack the Ozon Premium subscription where it's required (for example the sales funnel)
Example request
Build a financial summary of my Ozon cabinet for the last month and show the top FBS cancellation reasonsLimitations
Full ChatGPT operation targets a separate Ubuntu VPS and a Cloudflare tunnel, local-run instructions exist only for Cursor via stdio. Ozon secrets (Client-Id, Api-Key) live in .env on the server and are never handed to ChatGPT, but the MCP login itself is separate. Some analytics (for example the Premium sales funnel) are unavailable without the matching Ozon subscription.
How to disable. Disable the MCP connection in ChatGPT or remove the server from Cursor's config, then stop the process on the VPS.
MCP
- Transport
- stdio, http
- Authentication
- OAuth
Security check
- Reads financial transactions, orders and ad spend from the seller cabinet
- Runs as an always-on service on a VPS with Ozon keys in .env
README in short
The README lists the analysis areas in a table (products, orders, supplies, returns, finance, analytics, ads, communications, promotions and ratings), the 15-tool list, an architecture diagram from ChatGPT through OAuth and a Cloudflare Tunnel to api-seller.ozon.ru, and links to separate DEPLOY.md, PROMPT.md, USAGE.md, AI_GUIDE.md and CAPABILITIES.md files.
FAQ
Can the server change the cabinet if the key has write access?
No, the server's catalog allows only 268 of 511 read operations, everything else is excluded regardless of the key's own rights.
Does ChatGPT see the Ozon keys?
No, Ozon keys live in .env on the server and are only used for outgoing requests, ChatGPT connects through OAuth with a separate MCP login.
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