Wildberries MCP server with a CLI and per-section modules
mcp_server_wildberries
A Python MCP server for the Wildberries API with a separate tool module for each account section
- 0 ★ on the repository
- Last commit
Extended access
Why this level
- Without a README the exact permission scope is unclear, but the orders and supplies modules imply changing account data
Install
- Works in
- Services
Manual install
pip install -r requirements.txtDependency install; the exact run method is not documented by the author.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Without a README the exact permission scope is unclear, but the orders and supplies modules imply changing account data
This is third-party code. Review the repository files before installing.
What it does
The Python server is split into tool modules by Wildberries API section: advertising, analytics, reviews and questions, product cards, DBS, DBW and FBS orders, FBW supplies, finance, general methods, pickup, reports, tariffs and WBD digital goods. There is a separate cli.py and a __main__.py entry point. The repository has no README, so the module purposes are confirmed only from the file names.
Who it is for. For Wildberries sellers who want a Python server with tools clearly split by API section.
Good fit when
- You prefer a Python stack for a Wildberries MCP server
- You want tools clearly split by section: advertising separate, reports separate
Not a fit when
- You need documentation with examples: the repository has no README
- You need a ready pip package: the install method is undocumented
Example request
Show FBW supply orders and current warehouse tariffsMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
WB_API_KEYrequired, secret- Wildberries API key; the variable name is inferred from wb_api.py
Limitations
The repository has no README: no setup instructions, environment variables or examples. The project is small, maintained by one author, with no stars.
How to disable. Remove the server from your MCP client config and stop the process.
FAQ
Is there a run guide?
No, there is no README. The entry point has to be read from __main__.py and cli.py.
Discussion
No questions or reviews yet.
Related
All Wildberries toolsWildberries Seller API MCP server
wildberries-mcp-ru
An MCP server covering all seventeen Wildberries Seller API hosts: sales, stock, product cards, prices, financial reports and reviews
Wildberries Seller API MCP server: cards, prices, promotions, ads, orders, supplies, reviews and finance across several stores
Wildberries MCP
wildberries-mcp
MCP server for the Wildberries seller API: products, prices, stock, orders, FBS supplies, analytics, reviews and ads
OpenAPI-driven Wildberries MCP server
Wildberries MCP Server
A local Wildberries Seller API MCP server built from a 279-method OpenAPI catalog, with calls defaulting to dry-run
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
Wildberries Promotion MCP server
WB Promotion MCP Server
An MCP server for the Wildberries Promotion API: campaigns, bids, budget and advertising stats
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Wildberries MCP server with a CLI and per-section modules (this card) | no | API key | 0 | |
| Wildberries MCP server with plan and confirm | no | API key | 1 | plan then confirm |
| OpenAPI-driven Wildberries MCP server | no | API key | 0 | 279 methods |
README in short
The repository has no README. The code structure is transparent: server.py, cli.py, wb_api.py and thirteen modules in tools/, named after Wildberries API sections, from advertising to WBD digital goods.