Ozon Seller
Let Claude Code or Cursor call Ozon Seller API for listings, FBS/FBO fulfillment, finances, analytics, and returns from one MCP install.
Overview
io.github.dontsovcmc/ozon-seller is an MCP server for the Grow phase that connects coding agents to the Ozon Seller API for products, FBS/FBO, finance, analytics, and returns.
What is this MCP server?
- Stdio MCP package mcp-server-ozon-seller v0.3.1 runnable via uvx from PyPI
- Covers products plus FBS/FBO fulfillment flows exposed by Ozon Seller API
- Finance and analytics tooling for seller P&L-style checks from the agent
- Returns workflow access for post-purchase operational questions
- Requires OZON_CLIENT_ID and OZON_API_KEY as secret environment variables
- Server schema version 0.3.1 on PyPI identifier mcp-server-ozon-seller
- Stdio transport with uvx runtime hint
- 2 required secret environment variables: OZON_CLIENT_ID, OZON_API_KEY
Community signal: 2 GitHub stars.
What problem does it solve?
Managing an Ozon shop means constant context switching between seller UI, spreadsheets, and your codebase when you only want quick answers about stock, money, and returns.
Who is it for?
Indie sellers and solo devs on Ozon who already use Claude Code or Cursor and want marketplace ops callable as MCP tools.
Skip if: Builders with no Ozon seller account, or teams that need a hosted dashboard instead of agent-driven API access.
What do I get? / Deliverables
After registration, your agent can query and act on Ozon seller data in the same session where you ship fixes to your storefront or ops scripts.
- Registered stdio MCP server exposing Ozon Seller API tool surface
- Agent-callable access to products, fulfillment, finance, analytics, and returns endpoints
- Repeatable seller ops workflows without manual cabinet navigation
Recommended MCP Servers
Journey fit
Canonical shelf on Grow because indie marketplace sellers primarily adopt this to read performance and returns data, even though fulfillment touches Operate and wiring is Build. Analytics is the default discovery path for sellers comparing SKUs, campaigns, and refund trends—not raw API plumbing.
How it compares
Ozon Seller API MCP integration, not a copywriting or listing-optimization skill.
Common Questions / FAQ
Who is io.github.dontsovcmc/ozon-seller for?
It is for Ozon marketplace sellers and solo builders who want their AI agent to read and update seller data through the official API via MCP.
When should I use io.github.dontsovcmc/ozon-seller?
Use it when you are automating catalog, FBS/FBO, finance, analytics, or returns tasks from Claude Code, Cursor, or another stdio MCP client.
How do I add io.github.dontsovcmc/ozon-seller to my agent?
Add the mcp-server-ozon-seller stdio server to your MCP config, set OZON_CLIENT_ID and OZON_API_KEY, and run it with the documented uvx PyPI package.