Wildberries API MCP server with Cloudflare deploy
Wildberries API MCP Server
An MCP server for the Wildberries API with analytics, stock, CSV reports and a Cloudflare Workers deploy
- 0 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The server calls the Wildberries API with the seller's key and imports external CSV exports
Install
- Works in
- Services
Manual install
docker-compose upLocal run via Docker Compose after configuring .env from .env.example.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The server calls the Wildberries API with the seller's key and imports external CSV exports
This is third-party code. Review the repository files before installing.
What it does
The server acts as a middle HTTP layer over the Wildberries API: it centrally attaches the client's api-key to the Authorization header, handles errors and rate limits, normalizes responses, and ingests exports from the third-party EVIRMA PRO service. It covers analytics, promotion stats, stock and CSV reports. The repository is set up with CI, a published Docker image, and a Cloudflare Workers deploy via wrangler.
Who it is for. For sellers and developers who want one HTTP gateway to several parts of the Wildberries API with a ready cloud deploy.
Good fit when
- You want one server instead of several narrow ones for analytics, stock and CSV reports
- You need a Cloudflare Workers deploy without running your own server
- You work with EVIRMA PRO exports and want to import them through MCP
Not a fit when
- You need orders, pricing or reviews: this server focuses on analytics, stock and reports
- You do not want to deal with a Cloudflare or Docker deploy
Example request
Show product stock levels and promotion stats for the last weekMCP
- Transport
- stdio, http
- Authentication
- API key
Environment variables
WB_API_KEYrequired, secret- Wildberries API key attached to the Authorization header
Limitations
The project is maintained by one author, with no stars or known community. It needs a Wildberries API key. Some features depend on the export format of the third-party EVIRMA PRO service and are useless without it.
How to disable. Stop the container or worker and remove the server from your MCP client config.
FAQ
Can it run without hosting your own server?
Yes, the repository is set up to deploy to Cloudflare Workers via wrangler and to publish a Docker image in CI.
Discussion
No questions or reviews yet.
Related
All Wildberries toolsWildberries MCP
wildberries-mcp
MCP server for the Wildberries seller API: products, prices, stock, orders, FBS supplies, analytics, reviews and ads
Wildberries 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
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
Wildberries MCP search server
Wildberries MCP Server
A lightweight MCP server for searching Wildberries products via its public JSON API: product card, price, reviews with no browser
rf-marketplaces-mcp: Wildberries analytics and a seller cabinet
rf-marketplaces-mcp
An MCP server gives an agent Wildberries data by article without a token and, with a token, seller sales, stock and review replies
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
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Wildberries API MCP server with Cloudflare deploy (this card) | no | API key | 0 | |
| Wildberries MCP | no | API key | 16 | seller API for AI agents |
| A minimal Python Wildberries MCP server | no | API key | 0 | single-file server |
| Wildberries MCP server with 116 tools | no | API key | 0 | seller API |
README in short
The detailed Russian README describes the server as a middle HTTP layer over the Wildberries API that normalizes errors and rate limits, with sections on installation, available tools, MCP agents, examples and typical scenarios, getting a token, troubleshooting, a Cloudflare Workers deploy, and production safety rules.