SkillFoxx

Type a name, a task or a service

Wildberries MCP server (search + execute)

mcp-server-wildberries

A Wildberries Seller API MCP server using a search + execute pattern: 235 actions exposed through just three tools

MCP server

High risk

We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.

Why this level

  • 235 actions cover orders, supplies, prices and finance, and some of them write seller data
  • Cancelling orders and handling supplies is irreversible
All reasons and checks
Russian stack

dontsovcmc/mcp-server-wildberriesAuthor:dontsovcmc

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/mcp-server-wildberries

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

Other ways to install

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 'WB_TOKEN=<your WB_TOKEN>' wildberries -- uvx mcp-server-wildberries==0.2.1

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

{
  "mcpServers": {
    "wildberries": {
      "command": "uvx",
      "args": [
        "mcp-server-wildberries==0.2.1"
      ],
      "env": {
        "WB_TOKEN": "<your WB_TOKEN>"
      }
    }
  }
}

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

Keys and settings

WB_TOKENsecret, required

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": {
    "wildberries": {
      "command": "uvx",
      "args": [
        "mcp-server-wildberries==0.2.1"
      ],
      "env": {
        "WB_TOKEN": "<your WB_TOKEN>"
      }
    }
  }
}

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_TOKENsecret, required

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":"wildberries","type":"stdio","command":"uvx","args":["mcp-server-wildberries==0.2.1"],"env":{"WB_TOKEN":"<your WB_TOKEN>"}}'

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

{
  "servers": {
    "wildberries": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-server-wildberries==0.2.1"
      ],
      "env": {
        "WB_TOKEN": "<your WB_TOKEN>"
      }
    }
  }
}

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

Keys and settings

WB_TOKENsecret, required

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_TOKEN=<your WB_TOKEN>' -- uvx mcp-server-wildberries==0.2.1

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

[mcp_servers.wildberries]
command = "uvx"
args = ["mcp-server-wildberries==0.2.1"]
env = { WB_TOKEN = "<your WB_TOKEN>" }

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

Keys and settings

WB_TOKENsecret, required

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 'WB_TOKEN=<your WB_TOKEN>' wildberries uvx mcp-server-wildberries==0.2.1

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

{
  "mcpServers": {
    "wildberries": {
      "command": "uvx",
      "args": [
        "mcp-server-wildberries==0.2.1"
      ],
      "env": {
        "WB_TOKEN": "<your WB_TOKEN>"
      }
    }
  }
}

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

Keys and settings

WB_TOKENsecret, required

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": [
        "mcp-server-wildberries==0.2.1"
      ],
      "env": {
        "WB_TOKEN": "<your WB_TOKEN>"
      }
    }
  }
}

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_TOKENsecret, required

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": [
        "mcp-server-wildberries==0.2.1"
      ],
      "env": {
        "WB_TOKEN": "<your WB_TOKEN>"
      }
    }
  }
}

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_TOKENsecret, required

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": [
        "mcp-server-wildberries==0.2.1"
      ],
      "env": {
        "WB_TOKEN": "<your WB_TOKEN>"
      }
    }
  }
}

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

Keys and settings

WB_TOKENsecret, required

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",
        "mcp-server-wildberries==0.2.1"
      ],
      "environment": {
        "WB_TOKEN": "<your WB_TOKEN>"
      }
    }
  }
}

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

Keys and settings

WB_TOKENsecret, required

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": [
        "mcp-server-wildberries==0.2.1"
      ],
      "env": {
        "WB_TOKEN": "<your WB_TOKEN>"
      }
    }
  }
}

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

Keys and settings

WB_TOKENsecret, required

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": [
        "mcp-server-wildberries==0.2.1"
      ],
      "env": {
        "WB_TOKEN": "<your WB_TOKEN>"
      }
    }
  }
}

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

Keys and settings

WB_TOKENsecret, required

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

You will need: uv

Checked against the repository on Sep 25, 2026, commit 41e392c.

Text for your agent

Install with pip install mcp-server-wildberries, connect in Claude Code with claude mcp add wildberries -e WB_TOKEN=token -- mcp-server-wildberries, where the token comes from seller.wildberries.ru, Settings, API access.

Other ways from the author
pip install mcp-server-wildberries

Package install from the README.

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

What it does

The server follows the official Wildberries API documentation and covers products, orders, supplies, analytics, advertising and finance, 235 actions across every section. Instead of 235 separate tools, the agent gets three: wb_search finds an action from a natural-language description, wb_execute runs it by id with parameters, and wb_execute_file does the same while downloading a file. This keeps the LLM's context small, since only three tool schemas are exposed instead of hundreds. A separate CLI can run actions without an agent.

Who it is for. For Wildberries sellers who want an agent with access to the whole seller API without bloating context with dozens of tools.

Good fit when

  • You need full Wildberries Seller API coverage in one server
  • You care about not bloating the agent's context with many tool schemas
  • You want a CLI for the same actions without an agent, such as ping or a token check

Not a fit when

  • You need a pre-defined separate tool per action rather than a description-based search
  • You need one server covering several marketplaces at once

Example request

Find the Wildberries action for cancelling an FBS order and cancel order 12345

Limitations

You need a Wildberries seller JWT token from the seller dashboard. The project is at version 0.2.1, still young. The search + execute pattern requires the agent to look up an action id before calling it, an extra step compared to direct tools.

How to disable. Remove the server with claude mcp remove wildberries or delete it from your MCP client configuration.

MCP

Transport
stdio
Authentication
API key
Environment variables
WB_TOKEN
required, secret		Wildberries API token (JWT) from the seller dashboard
WB_TIMEOUT
HTTP request timeout in seconds, defaults to 30
WB_FILE_TIMEOUT
File download timeout in seconds, defaults to 60

Security check

  • 235 actions cover orders, supplies, prices and finance, and some of them write seller data
  • Cancelling orders and handling supplies is irreversible

README in short

The README explains the search + execute architecture with an example LLM dialogue, gives step-by-step install via pip or uvx for macOS, Linux and Windows, Claude Code setup with a token from a variable or file, a one-off connection via --mcp-config, and a table of environment variables with timeouts.

FAQ

Why only three tools instead of 235?

The server uses a search + execute pattern: wb_search finds the action, wb_execute runs it, saving context tokens.

Can I connect the server without saving it to Claude's settings?

Yes, with the --mcp-config flag for a single session, keeping the token in a separate .env.mcp file.

Official

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

MCP serverHigh risk483
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
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
Foxx AIWildberries MCP server (search + execute)

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.