wildberries-mcp
Related Servers
Alternatives to wildberries-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceEnables AI assistants to retrieve a Wildberries seller's product cards and customer reviews through the official Content and Feedbacks APIs.247 npm-
- FlicenseNot gradedqualityCmaintenanceMCP server that turns Wildberries marketplace into a toolkit for LLM agents, enabling product search, detailed card inspection, price history, reviews, and cross-product comparison.-
- FlicenseBqualityCmaintenanceProvides MCP tools for searching and comparing products on Wildberries (and Ozon planned), including product search, detailed card retrieval, and review fetching, normalized for LLM consumption.32-
- 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.57 npmMIT
- 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.1757 npmMIT
- AlicenseAqualityBmaintenanceEnables read-only analytics and product search for a Wildberries seller account, covering items, advertising, sales, stock, reviews, finances, and tariffs through MCP clients like ChatGPT or Cursor.12MIT
TDQS
Scored across 5 tools
Each tool has a clear primary purpose (fetch one product, search, history, reviews, compare), but get_product and compare_products overlap for a single article, and get_reviews vs get_product both surface rating info. Descriptions clarify the differences, so ambiguity is low but not zero.
All tools follow a consistent verb_noun pattern: get_product, search_products, get_price_history, get_reviews, compare_products. The verbs (get, search, compare) and nouns are clear and uniform.
5 tools is well-scoped for a read-only product data server. Each tool addresses a distinct need—single product detail, search, price history, reviews, and multi-product comparison—without unnecessary duplication or bloat.
For a marketplace data retrieval server, the tool set covers the core workflows: finding products, deep-diving a product, checking price trends, reading reviews, and comparing offers. No obvious gaps for the stated purpose; it's read-only so CRUD operations are not expected.