Server detail
The Wildberries MCP Server exposes the full Wildberries Seller API through the Model Context Protocol, giving agents direct access to 202 endpoints across product management, pricing, orders, supplies, advertising, reviews, finance, and analytics. Instead of juggling multiple REST calls or building a custom wrapper, developers can integrate once via MCP and let their agents query or update seller data conversationally. It supports multi-account workflows, so you can manage several Wildberries seller accounts from a single session, which is useful for agencies or large merchants. The server is community-maintained, written for easy deployment alongside existing MCP hosts, and maps cleanly onto Wildberries' official API structure without hiding the underlying semantics. Compared to hitting the REST API directly, you trade a bit of raw control for simpler authentication handling, automatic schema discovery, and reusable tool calls that agents can chain together. It's most valuable when you're building agentic workflows like auto-repricing based on analytics, order-to-supply automation, or review monitoring, where reducing boilerplate and keeping context in conversation matters more than micro-optimizing HTTP requests.
An MCP server that exposes Wildberries MCP Server capabilities to MCP-compatible AI clients.
Collections featuring this MCP
Tool testing
wildberries-mcp-server
Call the MCP capabilities provided by Wildberries MCP Server and return a structured result.
inputPass arguments according to the server tool schema.Connection modes
{
"mcpServers": {
"Wildberries MCP Server": {
"url": "Generated by the provider after deployment"
}
}
}The Remote endpoint is generated by the provider after deployment; this page does not fabricate an unusable endpoint.
No npm package is recorded. Open the source repository to complete command and args.If no npm package is registered, follow the installation method in the source repository.
How to use
- 01Step 1
Review server capabilities and permission scope.
- 02Step 2
Copy the install command or JSON configuration.
- 03Step 3
Run a small connection test in your client.
- 04Step 4
Adopt it long term only after reviewing access and maintenance.
Discussions
Use this space to keep checking source information, usage experience and maintenance status.
Open source page