Wildberries MCP server with plan and confirm
WB Hermes MCP
A 56-tool Wildberries seller MCP server where every change is a two-step plan-then-confirm operation
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
- 56 tools cover the seller's prices, orders, ad budget and financial documents
- The two-step confirmation reduces the risk of an accidental change but does not remove it
Install
Manual install
uv sync --all-groups && export WB_API_TOKEN='…' && uv run python -m wb_mcpThe README's local stdio run.
This is third-party code. Review the repository files before installing.
What it does
The server is built on wildberries-sdk and offers 56 tools covering the seller's core work: profile, tariffs, product cards, prices, stock and warehouses, FBS orders and supplies, ad campaigns with bids and negative phrases, funnel and reports, balance, financial documents, reviews, questions and chats. Tool names and errors are written in Russian specifically for GLM-class models and the Hermes agent. Every mutating operation is a two-step flow: a wb_plan_* tool only builds a plan, and wb_apply_change applies it once by a confirmation_id kept in process memory. Topping up the ad budget only works through a separate, explicit plan, and wb_describe_operation explains any tool's purpose and a safe example to the model.
Who it is for. For Wildberries sellers who want to automate ads and orders through an agent, but with explicit confirmation of every change.
Good fit when
- You need broad seller functionality in one server
- You want every change to start as a plan rather than an immediate action
- Your agent runs a GLM-class model and needs Russian tool names without SDK jargon
Not a fit when
- You need a packaged PyPI release rather than a source run
- You are not comfortable with confirmation_id living only in one MCP process's memory
Example request
Build a plan to top up the ad campaign budget and show it before applyingLimitations
You need a WB token with the right scopes and Python 3.12. The confirmation_id lives only in process memory, and the plan and apply calls must go through the same live server instance. The project targets the Hermes agent and GLM-class models, though the local run uses plain MCP stdio and works with other clients too. Two xlsx files with a stock export sit in the repo root, which looks like accidentally committed working data rather than part of the code; do not treat them as a template, and be aware of them when cloning.
How to disable. Stop the server process and remove it from your MCP client config, or run hermes mcp remove wb on a Hermes host.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| WB_API_TOKEN required, secret | A WB seller token with the right scopes, never passed as a tool argument |
Security check
- 56 tools cover the seller's prices, orders, ad budget and financial documents
- The two-step confirmation reduces the risk of an accidental change but does not remove it
README in short
The README covers 56 tools across seller sections, the two-step plan-then-apply model with an in-memory confirmation_id, a local run via uv and the WB_API_TOKEN variable, and a detailed Hermes host deployment scenario that pipes the token without saving it to command history and registers the server with hermes mcp add.
FAQ
Can the agent change a price or top up the budget right away?
No, a wb_plan_* tool builds a plan first, and only a separate wb_apply_change call with the confirmation_id applies it.
Do I need the Hermes agent specifically?
No, the local run uses plain MCP stdio; Hermes is only needed for the ready-made deployment scenario 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