Wildberries MCP server with plan and confirm

Install

Works in

• SourceCraft
• Koda
• Coddy
• Hermes Agent

Services

• Wildberries

Manual install

uv sync --all-groups && export WB_API_TOKEN='…' && uv run python -m wb_mcp

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.

Example request

Build a plan to top up the ad campaign budget and show it before applying

MCP

Transport

stdio

Authentication

API key

Limitations

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.

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.