Wildberries MCP server on FastMCP from OpenAPI

wildberries-fast-mcp

A Python wrapper on FastMCP that builds a Wildberries MCP server directly from OpenAPI specs by scope

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

Broad access

Why this level

  • The server is generated straight from the API spec, so write scopes like discounts and prices can change the seller's data
All reasons and checks
Russian stack

bigancientmammoth/wildberries-fast-mcp

Install

Services

Manual install

pip install wildberries-fast-mcp

Or uv add wildberries-fast-mcp.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • The server is generated straight from the API spec, so write scopes like discounts and prices can change the seller's data

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

What it does

The package installs via pip or uv and runs an MCP server through FastMCP.from_openapi, parsing the Wildberries API specs. Since one spec can cover several domains at once and FastMCP does not support that out of the box, the author split it into separate scopes, for example products:content and products:discounts-prices, each run as its own process with a --scope flag.

Who it is for. For developers who want a Wildberries MCP server generated straight from OpenAPI without hand-writing every tool.

Good fit when

  • You want an MCP server that follows the official Wildberries OpenAPI spec
  • You are fine running several server processes, each for its own API scope

Not a fit when

  • You want a single process with every tool at once: here scopes run separately
  • You need usage documentation: the README is limited to installation and one config example

Example request

Connect the Wildberries MCP server for the product content scope and list its available tools

MCP

Transport
stdio
Authentication
API key

Limitations

The project is very small, maintained by one author, with no stars. The README does not describe environment variables beyond the token in launch arguments and does not give a full tool list: tools are generated from the OpenAPI spec at runtime.

How to disable. Remove the server entries from claude_desktop_config.json and uninstall the package with pip uninstall wildberries-fast-mcp.

FAQ

Why do I need to specify a scope?

One Wildberries OpenAPI spec covers several domains at once, and FastMCP.from_openapi does not support that without splitting it into scopes.

Discussion

No questions or reviews yet.

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
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

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

README in short

The English README explains the package as a FastMCP wrapper over the Wildberries OpenAPI, gives two install commands via pip and uv, and shows a Claude Desktop config example with two server processes for different API scopes, with the token passed as a launch argument.

README badge

Report a problem