Wildberries MCP Server

Connect Wildberries to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for Wildberries Seller API — products, orders, supplies, analytics, advertising. The wildberries mcp server is what makes that connection.

Installation

The server ships on PyPI as mcp-server-wildberries, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Windows — Подключение к Claude Code (токен в командной строке): cmd set WB_TOKEN=ваш-токен && claude mcp add wildberries -e WB_TOKEN -- mcp-server-wildberries

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Wildberries's toolset — Windows — is a fair guide to whether it matches your workflow. It is maintained by dontsovcmc; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.