Ozon API MCP server

Ozon API MCP Server

A 31-tool MCP server for the Ozon Seller API and Performance API: products, stock, prices, orders, finance, ads and reviews

MCP serverRussian stack

antondrpq/ozon-api-mcp-serverAuthor:antondrpq

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/ozon-api-mcp-server

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

Assembled automatically, review before installing.

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 stdio --env 'OZON_CLIENT_ID=<your OZON_CLIENT_ID>' --env 'OZON_API_KEY=<your OZON_API_KEY>' ozon-api-mcp-server -- node start

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "ozon-api-mcp-server": {
      "command": "node",
      "args": [
        "start"
      ],
      "env": {
        "OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
        "OZON_API_KEY": "<your OZON_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

OZON_CLIENT_IDsecret, required: Client-Id из личного кабинета Ozon Seller
OZON_API_KEYsecret, required: Api-Key из личного кабинета Ozon Seller
OZON_PERF_CLIENT_IDsecret, optional: Client-Id для Performance API (опционально)
OZON_PERF_CLIENT_SECRETsecret, optional: Client-Secret для Performance API (опционально)
MCP_API_KEYsecret, optional: Опциональный секрет для защиты MCP-эндпоинта

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 ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "ozon-api-mcp-server": {
      "command": "node",
      "args": [
        "start"
      ],
      "env": {
        "OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
        "OZON_API_KEY": "<your OZON_API_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_CLIENT_IDsecret, required: Client-Id из личного кабинета Ozon Seller
OZON_API_KEYsecret, required: Api-Key из личного кабинета Ozon Seller
OZON_PERF_CLIENT_IDsecret, optional: Client-Id для Performance API (опционально)
OZON_PERF_CLIENT_SECRETsecret, optional: Client-Secret для Performance API (опционально)
MCP_API_KEYsecret, optional: Опциональный секрет для защиты MCP-эндпоинта

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

code --add-mcp '{"name":"ozon-api-mcp-server","type":"stdio","command":"node","args":["start"],"env":{"OZON_CLIENT_ID":"<your OZON_CLIENT_ID>","OZON_API_KEY":"<your OZON_API_KEY>"}}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "ozon-api-mcp-server": {
      "type": "stdio",
      "command": "node",
      "args": [
        "start"
      ],
      "env": {
        "OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
        "OZON_API_KEY": "<your OZON_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

OZON_CLIENT_IDsecret, required: Client-Id из личного кабинета Ozon Seller
OZON_API_KEYsecret, required: Api-Key из личного кабинета Ozon Seller
OZON_PERF_CLIENT_IDsecret, optional: Client-Id для Performance API (опционально)
OZON_PERF_CLIENT_SECRETsecret, optional: Client-Secret для Performance API (опционально)
MCP_API_KEYsecret, optional: Опциональный секрет для защиты MCP-эндпоинта

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-api-mcp-server --env 'OZON_CLIENT_ID=<your OZON_CLIENT_ID>' --env 'OZON_API_KEY=<your OZON_API_KEY>' -- node start

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.ozon-api-mcp-server]
command = "node"
args = ["start"]
env = { OZON_CLIENT_ID = "<your OZON_CLIENT_ID>", OZON_API_KEY = "<your OZON_API_KEY>" }

If the file already exists, append the block to the end.

Keys and settings

OZON_CLIENT_IDsecret, required: Client-Id из личного кабинета Ozon Seller
OZON_API_KEYsecret, required: Api-Key из личного кабинета Ozon Seller
OZON_PERF_CLIENT_IDsecret, optional: Client-Id для Performance API (опционально)
OZON_PERF_CLIENT_SECRETsecret, optional: Client-Secret для Performance API (опционально)
MCP_API_KEYsecret, optional: Опциональный секрет для защиты MCP-эндпоинта

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_CLIENT_ID=<your OZON_CLIENT_ID>' -e 'OZON_API_KEY=<your OZON_API_KEY>' ozon-api-mcp-server node start

Or add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "ozon-api-mcp-server": {
      "command": "node",
      "args": [
        "start"
      ],
      "env": {
        "OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
        "OZON_API_KEY": "<your OZON_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

OZON_CLIENT_IDsecret, required: Client-Id из личного кабинета Ozon Seller
OZON_API_KEYsecret, required: Api-Key из личного кабинета Ozon Seller
OZON_PERF_CLIENT_IDsecret, optional: Client-Id для Performance API (опционально)
OZON_PERF_CLIENT_SECRETsecret, optional: Client-Secret для Performance API (опционально)
MCP_API_KEYsecret, optional: Опциональный секрет для защиты MCP-эндпоинта

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-api-mcp-server": {
      "command": "node",
      "args": [
        "start"
      ],
      "env": {
        "OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
        "OZON_API_KEY": "<your OZON_API_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_CLIENT_IDsecret, required: Client-Id из личного кабинета Ozon Seller
OZON_API_KEYsecret, required: Api-Key из личного кабинета Ozon Seller
OZON_PERF_CLIENT_IDsecret, optional: Client-Id для Performance API (опционально)
OZON_PERF_CLIENT_SECRETsecret, optional: Client-Secret для Performance API (опционально)
MCP_API_KEYsecret, optional: Опциональный секрет для защиты MCP-эндпоинта

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-api-mcp-server": {
      "command": "node",
      "args": [
        "start"
      ],
      "env": {
        "OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
        "OZON_API_KEY": "<your OZON_API_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_CLIENT_IDsecret, required: Client-Id из личного кабинета Ozon Seller
OZON_API_KEYsecret, required: Api-Key из личного кабинета Ozon Seller
OZON_PERF_CLIENT_IDsecret, optional: Client-Id для Performance API (опционально)
OZON_PERF_CLIENT_SECRETsecret, optional: Client-Secret для Performance API (опционально)
MCP_API_KEYsecret, optional: Опциональный секрет для защиты MCP-эндпоинта

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-api-mcp-server": {
      "command": "node",
      "args": [
        "start"
      ],
      "env": {
        "OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
        "OZON_API_KEY": "<your OZON_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

OZON_CLIENT_IDsecret, required: Client-Id из личного кабинета Ozon Seller
OZON_API_KEYsecret, required: Api-Key из личного кабинета Ozon Seller
OZON_PERF_CLIENT_IDsecret, optional: Client-Id для Performance API (опционально)
OZON_PERF_CLIENT_SECRETsecret, optional: Client-Secret для Performance API (опционально)
MCP_API_KEYsecret, optional: Опциональный секрет для защиты MCP-эндпоинта

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-api-mcp-server": {
      "type": "local",
      "command": [
        "node",
        "start"
      ],
      "environment": {
        "OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
        "OZON_API_KEY": "<your OZON_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

OZON_CLIENT_IDsecret, required: Client-Id из личного кабинета Ozon Seller
OZON_API_KEYsecret, required: Api-Key из личного кабинета Ozon Seller
OZON_PERF_CLIENT_IDsecret, optional: Client-Id для Performance API (опционально)
OZON_PERF_CLIENT_SECRETsecret, optional: Client-Secret для Performance API (опционально)
MCP_API_KEYsecret, optional: Опциональный секрет для защиты MCP-эндпоинта

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-api-mcp-server": {
      "command": "node",
      "args": [
        "start"
      ],
      "env": {
        "OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
        "OZON_API_KEY": "<your OZON_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

OZON_CLIENT_IDsecret, required: Client-Id из личного кабинета Ozon Seller
OZON_API_KEYsecret, required: Api-Key из личного кабинета Ozon Seller
OZON_PERF_CLIENT_IDsecret, optional: Client-Id для Performance API (опционально)
OZON_PERF_CLIENT_SECRETsecret, optional: Client-Secret для Performance API (опционально)
MCP_API_KEYsecret, optional: Опциональный секрет для защиты MCP-эндпоинта

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-api-mcp-server": {
      "command": "node",
      "args": [
        "start"
      ],
      "env": {
        "OZON_CLIENT_ID": "<your OZON_CLIENT_ID>",
        "OZON_API_KEY": "<your OZON_API_KEY>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

OZON_CLIENT_IDsecret, required: Client-Id из личного кабинета Ozon Seller
OZON_API_KEYsecret, required: Api-Key из личного кабинета Ozon Seller
OZON_PERF_CLIENT_IDsecret, optional: Client-Id для Performance API (опционально)
OZON_PERF_CLIENT_SECRETsecret, optional: Client-Secret для Performance API (опционально)
MCP_API_KEYsecret, optional: Опциональный секрет для защиты MCP-эндпоинта

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

You will need: Node.js

Checked against the repository on Sep 26, 2026, commit 4167a1e.

Text for your agent

Clone https://github.com/antondrpq/Ozon-API-MCP-Server, run npm install, copy .env.example to .env and fill in OZON_CLIENT_ID and OZON_API_KEY, run npm start, and connect your MCP client to http://localhost:3000/mcp.

Other ways from the author

npm install
cp .env.example .env
npm start

After filling .env with Ozon keys, the server starts on port 3000, MCP endpoint /mcp.

This is third-party code. Review the repository files before installing.

What it does

A Node.js server runs an Express app with JSON-RPC 2.0 over Streamable HTTP and gives an agent 31 tools spanning the Ozon Seller API and Performance API: product cards and stock, price and stock updates, FBS and FBO postings including cancellation, financial transactions and summaries, analytics, ad campaign stats, reviews with replies, and buyer chat. The Seller API is called with two headers, Client-Id and Api-Key, while Performance API uses a separate OAuth2 client with token caching. Write tools carry the readOnlyHint: false annotation, and posting cancellation also carries destructiveHint: true.

Who it is for. For Ozon sellers and agencies who want one server covering products, orders, finance, ads and buyer communication.

Good fit when

You need to change product prices and stock through an agent
You need to track and process FBS and FBO postings
You need financial summaries, ad stats and review or chat handling

Not a fit when

You need a read-only mode with no risk of accidental writes
You lack a Premium Plus subscription but need the review tools
You need stable, verified Performance API paths without checking before production

Example request

Update this product's stock and price in Ozon and show the current ad campaign's stats

Limitations

The review tools only work with a Premium Plus subscription in the seller account. The composite ozon_finance_summary and ozon_perf_ads_summary tools were not tested against a live account, only against the documented response shape. Exact Performance API paths are documented worse than the Seller API and can change. The server covers the main API areas, not all roughly 460 Ozon methods. The package is not published to npm; Ozon keys stay on your own server.

How to disable. Stop docker-compose or the Node.js process and remove the server from your MCP client configuration.

MCP

Transport: http
Authentication: API key

Environment variables
Environment variables
OZON_CLIENT_ID required, secret	The seller's Client-Id from Ozon Seller API settings.
OZON_API_KEY required, secret	The seller's Ozon Seller API key.
MCP_API_KEY secret	An optional separate secret protecting the MCP endpoint itself.

Security check

Changes product prices and stock and can cancel a posting
Can send messages to buyers and reply to reviews on behalf of the shop
Start with a read-only key if Ozon offers one

README in short

The README compares Ozon and Wildberries in detail on auth, API domains and pagination, lists all 31 tools by section with write and destructive flags, gives Node.js and Docker run commands, a curl example, and a security section: keys stay server-side, an optional MCP_API_KEY, and a non-root container user. It separately lists known limitations to check before production.

FAQ

Can the server cancel a posting or message a buyer?

Yes, ozon_fbs_posting_cancel and ozon_chat_send_message are in the tool list and flagged as side-effect actions.

Do I need Ozon ads for the server to work?

No, Performance API keys are optional and only needed for the ad-related tools.

Salesforce DX MCP Server

Official

Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent

MCP serverHigh risk483

Yandex Kit skills for store management

kit-skills

Official

Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex

PluginHigh riskRussian stackNo VPN needed28

YouGile MCP by Indalo

YouGile MCP

Editors’ pick

Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit

MCP serverHigh riskRussian stackNo VPN needed

Bitrix24 portal MCP server

MCP-сервер портала Битрикс24

Official

Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail

MCP serverHigh riskRussian stackNo VPN needed

Install

What it does

Good fit when

Not a fit when

Example request

Limitations

MCP

Security check

README in short

FAQ

Related

Salesforce DX MCP Server

Yandex Kit skills for store management

YouGile MCP by Indalo

Bitrix24 portal MCP server