mcp-server-wildberries
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WB_TOKEN | Yes | API-токен Wildberries (JWT) | |
| WB_TIMEOUT | No | Таймаут HTTP-запросов к API (секунды) | 30 |
| WB_FILE_TIMEOUT | No | Таймаут скачивания файлов (секунды) | 60 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wb_searchB | Find available Wildberries API actions by intent. Args: query: natural language description of what you want to do domain: optional filter (general, content, fbs_orders, dbw_orders, dbs_orders, pickup_orders, fbw_supplies, advertising, communications, tariffs, analytics, reports, finance, wbd) limit: max results (default 10) |
| wb_executeA | Execute a Wildberries API action by ID. Use wb_search first to find the action ID and its parameter schema. Args: action: action ID from wb_search results (e.g. "wb_fbs_order_cancel") params_json: JSON object with action parameters matching the schema |
| wb_execute_fileC | Execute a Wildberries API action that downloads a file. Args: action: action ID for download actions file_path: local file path to save the downloaded file params_json: JSON object with action parameters |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: wb_search for discovering actions, wb_execute for executing non-file actions, and wb_execute_file for file downloads. No overlap or ambiguity.
All tools follow a consistent 'wb_verb' pattern, with wb_execute_file extending the pattern for file-specific actions. The naming is predictable and uniform.
With only 3 tools, the server is lightweight but well-scoped for its purpose of providing a searchable interface to a large API. The count is slightly low but appropriate given the abstraction pattern.
The tool surface covers the essential workflow: search for actions, execute actions, and handle file downloads. A minor gap is the lack of a direct listing or schema retrieval tool, but the search tool mitigates this.