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

  • 2 ★ on the repository
  • Last commit
MCP server

Extended access

Why this level

  • Runs a Docker container that calls public Wildberries hosts via curl
  • Only reads search, product cards and reviews, no seller token needed
All reasons and checks
Russian stack

eduard256/wb-mcp-server

Install

Services

Manual install

docker run -i --rm --init eduard256/wb-mcp-server:latest

Runs the published image over stdio, no Chromium needed.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Runs a Docker container that calls public Wildberries hosts via curl
  • Only reads search, product cards and reviews, no seller token needed

This is third-party code. Review the repository files before installing.

What it does

The server gives an agent three tools: product search by query with price, rating, brand and seller, a product card by SKU or link with stock and specs, and customer reviews with text, pros and cons. It talks directly to Wildberries' public hosts search.wb.ru, card.wb.ru and feedbacks.wb.ru and parses the JSON they return, with no browser and no seller token. Requests to Wildberries go through the system curl, because WB blocks a plain Node fetch by its TLS fingerprint, with throttling and retry on 429 and 403 errors. The Docker image is built on node:20-slim and weighs about 80 megabytes.

Who it is for. For shoppers and analysts who want to find and compare Wildberries products right from a chat with an agent.

Good fit when

  • You want to find and compare Wildberries products without a seller account
  • You need specs, stock and reviews for a specific product by SKU
  • You want a lightweight container with no Chromium to deploy

Not a fit when

  • You need seller-dashboard data or actions: sales, ads, prices
  • You need the official Seller API rather than public-host parsing

Example request

Find wireless headphones on Wildberries under 3000 rubles with a rating above 4.5

MCP

Transport
stdio
Authentication
not required

Limitations

The repository has no license file. It reads Wildberries' public, undocumented hosts, so the response format can change without notice: the README already notes the product-detail endpoint moved from v2 to v4. Wildberries throttles frequent requests with 429 and 403, so a burst of calls slows responses.

How to disable. Stop the server container or remove its entry from your MCP client configuration.

FAQ

Do I need a Wildberries seller token?

No, the server only reads the public catalog and reviews without authorization.

Why use curl instead of fetch?

Wildberries blocks a plain Node fetch by its TLS fingerprint, and curl passes that check.

Discussion

No questions or reviews yet.

Wildberries MCP

wildberries-mcp

Russian stack

MCP server for the Wildberries seller API: products, prices, stock, orders, FBS supplies, analytics, reviews and ads

MCP serverBroad access16Repository stars
Russian stack

An MCP server covering all seventeen Wildberries Seller API hosts: sales, stock, product cards, prices, financial reports and reviews

MCP serverBroad access4Repository stars
Russian stack

Wildberries Seller API MCP server using a search and execute scheme: 235 actions instead of 235 separate tools

MCP serverBroad access2Repository stars
Russian stack

Wildberries Seller API MCP server: cards, prices, promotions, ads, orders, supplies, reviews and finance across several stores

MCP serverBroad access8Repository stars

README in short

The README describes the server's three tools, one-command launch from Docker Hub, and separate install guides for twelve clients from Claude Code to Zed and JetBrains. An internals section explains why requests go through curl, where the product description comes from, and which id to use for reviews.

README badge

Report a problem