A minimal Python Wildberries MCP server
Wildberries MCP
A small Python MCP server for the Wildberries API, run through uv as a single wb.py file
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
- The tool set is undocumented, so it is unclear whether the server can change data in the seller account
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/roma-mgcom-wildberries-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 'WB_API_KEY=<your WB_API_KEY>' wildberries -- uvx --directory FULL/PATH/TO/wildberries-mcp run wb.pyOr add to the file .mcp.json, in the project
{
"mcpServers": {
"wildberries": {
"command": "uvx",
"args": [
"--directory",
"FULL/PATH/TO/wildberries-mcp",
"run",
"wb.py"
],
"env": {
"WB_API_KEY": "<your WB_API_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
WB_API_KEYsecret, required- API key for Wildberries
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": {
"wildberries": {
"command": "uvx",
"args": [
"--directory",
"FULL/PATH/TO/wildberries-mcp",
"run",
"wb.py"
],
"env": {
"WB_API_KEY": "<your WB_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
WB_API_KEYsecret, required- API key for Wildberries
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":"wildberries","type":"stdio","command":"uvx","args":["--directory","FULL/PATH/TO/wildberries-mcp","run","wb.py"],"env":{"WB_API_KEY":"<your WB_API_KEY>"}}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"wildberries": {
"type": "stdio",
"command": "uvx",
"args": [
"--directory",
"FULL/PATH/TO/wildberries-mcp",
"run",
"wb.py"
],
"env": {
"WB_API_KEY": "<your WB_API_KEY>"
}
}
}
}If the file already exists, add the server inside the servers key.
Keys and settings
WB_API_KEYsecret, required- API key for Wildberries
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 wildberries --env 'WB_API_KEY=<your WB_API_KEY>' -- uvx --directory FULL/PATH/TO/wildberries-mcp run wb.pyOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.wildberries]
command = "uvx"
args = ["--directory", "FULL/PATH/TO/wildberries-mcp", "run", "wb.py"]
env = { WB_API_KEY = "<your WB_API_KEY>" }If the file already exists, append the block to the end.
Keys and settings
WB_API_KEYsecret, required- API key for Wildberries
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 ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"wildberries": {
"command": "uvx",
"args": [
"--directory",
"FULL/PATH/TO/wildberries-mcp",
"run",
"wb.py"
],
"env": {
"WB_API_KEY": "<your WB_API_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
WB_API_KEYsecret, required- API key for Wildberries
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": {
"wildberries": {
"command": "uvx",
"args": [
"--directory",
"FULL/PATH/TO/wildberries-mcp",
"run",
"wb.py"
],
"env": {
"WB_API_KEY": "<your WB_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
WB_API_KEYsecret, required- API key for Wildberries
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": {
"wildberries": {
"command": "uvx",
"args": [
"--directory",
"FULL/PATH/TO/wildberries-mcp",
"run",
"wb.py"
],
"env": {
"WB_API_KEY": "<your WB_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
WB_API_KEYsecret, required- API key for Wildberries
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": {
"wildberries": {
"command": "uvx",
"args": [
"--directory",
"FULL/PATH/TO/wildberries-mcp",
"run",
"wb.py"
],
"env": {
"WB_API_KEY": "<your WB_API_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
WB_API_KEYsecret, required- API key for Wildberries
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": {
"wildberries": {
"type": "local",
"command": [
"uvx",
"--directory",
"FULL/PATH/TO/wildberries-mcp",
"run",
"wb.py"
],
"environment": {
"WB_API_KEY": "<your WB_API_KEY>"
}
}
}
}If the file already exists, add the server inside the mcp key.
Keys and settings
WB_API_KEYsecret, required- API key for Wildberries
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": {
"wildberries": {
"command": "uvx",
"args": [
"--directory",
"FULL/PATH/TO/wildberries-mcp",
"run",
"wb.py"
],
"env": {
"WB_API_KEY": "<your WB_API_KEY>"
}
}
}
}If the file already exists, add the server inside the context_servers key.
Keys and settings
WB_API_KEYsecret, required- API key for Wildberries
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": {
"wildberries": {
"command": "uvx",
"args": [
"--directory",
"FULL/PATH/TO/wildberries-mcp",
"run",
"wb.py"
],
"env": {
"WB_API_KEY": "<your WB_API_KEY>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
WB_API_KEYsecret, required- API key for Wildberries
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Clone roma-mgcom/wildberries-mcp, set WB_API_KEY in your MCP client config, and run it with uv --directory /path/to/wildberries-mcp run wb.py.
Other ways from the author
{
"mcpServers": {
"wildberries": {
"command": "uv",
"args": ["--directory", "FULL/PATH/TO/wildberries-mcp", "run", "wb.py"],
"env": {"WB_API_KEY": "WB_API_KEY"}
}
}
}The config snippet from the project's README.
This is third-party code. Review the repository files before installing.
What it does
The project provides a minimal MCP server over the Wildberries API in Python, with all the code in a single wb.py file and run through the uv package manager. The README is limited to a connection config snippet; it does not list or describe the tools.
Who it is for. For people who want a short, readable Python example of a Wildberries MCP server and are willing to read the code themselves.
Good fit when
- You want a compact, low-dependency example to study the approach
- You already use uv for Python projects
Not a fit when
- You need a documented tool list: the README does not provide one
- You need broad Wildberries API coverage: this server is minimal
Example request
Connect to the Wildberries MCP server and list its toolsLimitations
The README does not describe which tools the server exposes, only the connection config. The project is small, maintained by one author, with no stars and no updates for over a year.
How to disable. Remove the server entry from your MCP client config.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| WB_API_KEY required, secret | Wildberries seller API key |
Security check
- The tool set is undocumented, so it is unclear whether the server can change data in the seller account
README in short
The README is short and contains only a JSON config snippet for connecting the server via uv run wb.py with a WB_API_KEY variable. There is no description of tools or features, just the run setup via pyproject.toml and uv.lock.
FAQ
Which environment variables are needed?
WB_API_KEY, based on the config example in the README.
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