wildberries-mcp-ru
Related Servers
Alternatives to wildberries-mcp-ru
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceOzon Seller API in your AI assistant: products, FBS and FBO orders, prices, stocks, finance and reviews. 441 methods live in a YAML catalog the server executes, the agent searches it in plain language and calls a method through three generic tools, and every method carries an access class so writes and irreversible calls ask for confirmation.2541 PyPI3MIT
- AlicenseAqualityAmaintenanceYandex Market Partner API in your AI assistant: orders and returns, products and cards, prices and tariffs, reports, reviews and chats. 165 methods live in a YAML catalog the server executes, the agent searches it in plain language, and every method carries an access class so writes and irreversible calls ask for confirmation.2626 PyPI2MIT
- AlicenseAqualityAmaintenanceAvito business API in your AI assistant: listings and statistics, buyer messenger, orders and Avito Delivery, bulk upload, promotion and reviews. 64 methods live in a YAML catalog the server executes, the agent searches it in plain language, and every method carries an access class so writes and irreversible calls ask for confirmation.3043 PyPI2MIT
- AlicenseAqualityCmaintenanceEnables AI agents to read and work with Wildberries, Ozon, and Yandex Market seller accounts through typed tools, multi-account support, unified data schemas, rate limiting, audit, and encrypted credential storage.1780 npmMIT
- AlicenseNot gradedqualityCmaintenanceConnects AI assistants to Wildberries and Ozon seller accounts for real-time access to sales, stocks, prices, finances, and reviews through official APIs.MIT
- AlicenseNot gradedqualityBmaintenanceLets AI agents read and query Wildberries, Ozon, and Yandex Market seller accounts through unified typed tools, with multi-account support, rate limiting, and encrypted credentials.80 npmMIT
TDQS
Scored across 25 tools
Each tool has a distinct role: discovery, catalog-based execution, raw path-based execution, credentials, workflows, and high-level business operations. The main ambiguity risk is between call/write/delete_method and the raw variants, but the descriptions clearly differentiate operation_id-based vs path-based invocation.
All tools share the wb_ prefix and mostly follow a verb_noun pattern (list_cabinets, search_methods, set_price). wb_map is a minor deviation, and list vs get is used consistently for collections vs single items.
25 tools sits at the upper boundary of the borderline-heavy range. The count is justified by the server's broad purpose as a full Wildberries API gateway with discovery, execution, credentials, workflows, and convenience operations, but it still feels dense for an agent to navigate.
The raw read/write/delete tools cover any path and HTTP verb, so no Wildberries endpoint is unreachable. Catalog discovery, pagination, credential lifecycle, and workflow recipes cover the surrounding operational needs, leaving no obvious dead ends.