Wildberries Analytics MCP server

WB Analytics MCP Server

An MCP server for the Wildberries Analytics API: orders by search query and product search terms

  • 0 ★ on the repository
  • Last commit
  • MIT
MCP server

Extended access

Why this level

  • The server calls the Wildberries analytics API with a seller token
  • Only reads orders by search query and the phrase list
All reasons and checks
Russian stack

rcd27/wildberries-analytics-mcp-server

A similar tool with a larger community: Wildberries MCP, 16 ★ on the repository

Install

Services

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/wb-analytics-mcp-server

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

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

  • The server calls the Wildberries analytics API with a seller token
  • Only reads orders by search query and the phrase list

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

What it does

The server wraps two methods of the Wildberries Analytics API as MCP tools: product orders broken down by search query for a period, and the list of search phrases buyers use to find a product. The README marks the server as minimal, with wider API coverage listed as a future task.

Who it is for. For Wildberries sellers who want a quick check on which search queries bring orders for a product.

Good fit when

  • You need to know which search phrases buyers use to find a product
  • You need orders broken down by search query for a period

Not a fit when

  • You need full analytics: sales funnel, stock levels, complete reports. This server does not cover that yet
  • You need finance, review or advertising tools: those are separate servers by the same author

Example request

Show which search queries brought orders for this product over the last month

MCP

Transport
stdio
Authentication
API key

Environment variables

WB_ANALYTICS_OAUTH_TOKEN required, secret
Wildberries OAuth token with access to the Analytics API

Limitations

The server calls itself minimal: only two methods of the much wider Analytics API are covered. The project is small, maintained by one author, with no releases. It needs a Wildberries OAuth token with access to the Analytics API.

How to disable. Remove the server from your MCP client config and stop the node process.

FAQ

How many tools does the server have?

Two: order details by search query and the product's search text list. The usage section in the README is marked TODO.

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

Wildberries MCP search server

Wildberries MCP Server

Russian stack

A lightweight MCP server for searching Wildberries products via its public JSON API: product card, price, reviews with no browser

MCP serverExtended access2Repository stars

Wildberries Communications MCP server

WB Communications MCP Server

Russian stack

An MCP server for the Wildberries Communications API: reviews, buyer questions and seller claims

MCP serverExtended access

Wildberries Promotion MCP server

WB Promotion MCP Server

Russian stack

An MCP server for the Wildberries Promotion API: campaigns, bids, budget and advertising stats

MCP serverBroad access
Russian stack

A local Wildberries Seller API MCP server built from a 279-method OpenAPI catalog, with calls defaulting to dry-run

MCP serverBroad access

README in short

The README is short: install via npm install, set WB_ANALYTICS_OAUTH_TOKEN in .env, run modes for development, production and MCP Inspector debugging. The tool description section is marked TODO, but endpoints and src/tools show two API methods.

README badge

Report a problem