ru-marketplace-mcp
Related Servers
Alternatives to ru-marketplace-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables querying and comparing prices, availability, ratings, reviews, and seller details from major Russian and Chinese marketplaces (Wildberries, Ozon, Yandex Market, and others) without requiring API keys, via a unified MCP interface.425MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that turns Wildberries marketplace into a toolkit for LLM agents, enabling product search, detailed card inspection, price history, reviews, and cross-product comparison.-
- AlicenseDqualityBmaintenanceEnables product search and price comparison across Ozon and Yandex Market via a read-only MCP server, returning normalized data with source URLs.6MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for retrieving Wildberries product reviews and formatting them as JSON for LLM analysis.1-
- AlicenseCqualityBmaintenanceMCP server for the Wildberries Seller API: 202 tools for prices, promotions, ads, orders, supplies, reviews, finance and analytics. Multi-store, encrypted tokens, web dashboard and self-diagnostics; Docker with SSE or stdio.197126 PyPI3MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that scrapes e-commerce product and category pages into structured JSON, enabling Claude to build presentations, market analyses, and competitive product comparisons. Currently optimized for Trendyol.MIT
TDQS
Scored across 40 tools
Most tools follow a clear <marketplace>_<operation> split (search vs card vs reviews), so selection is usually unambiguous. The main exception is compare_sources and marketplace_sources, which both report which marketplaces are available and are easy to confuse. wb_category/detmir_category vs their plural counterparts also require reading descriptions carefully.
Names consistently use snake_case with a marketplace prefix and an operation suffix (wb_search, ozon_card, avito_seller), making the set predictable. Minor deviations include marketplace_sources (noun-based), wb_root_info, and the awkward compare_verify_offer. The singular/plural category pair (detmir_category vs detmir_categories) is consistent once understood.
At 40 tools this is a heavy surface, though each marketplace genuinely needs at least search+card and there are many sources. The count is justified by the broad multi-marketplace scope, but a few redundant introspection tools (compare_sources vs marketplace_sources) could be merged. It sits at the high end of acceptable for a unified marketplace aggregator.
Core read-only workflows are well covered: search, product cards, reviews, categories, seller lookup, price comparison, and analytics across a dozen marketplaces. Notable gaps include category browsing only for WB and Detsky Mir, seller-detail tools only for WB and Avito, and missing review texts on AliExpress — but these are documented limitations. The compare_prices + compare_verify_offer pair closes the loop between aggregate and per-source data.