Skip to main content
Glama

Related Servers

Alternatives to ru-marketplace-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that turns Wildberries marketplace into a toolkit for LLM agents, enabling product search, detailed card inspection, price history, reviews, and cross-product comparison.
      -
    • A
      license
      D
      quality
      B
      maintenance
      Enables product search and price comparison across Ozon and Yandex Market via a read-only MCP server, returning normalized data with source URLs.
      6
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP servers for Russian commerce and marketing APIs: Wildberries, Ozon, Yandex Market, Avito, Bitrix24, amoCRM, Yandex Direct, Yandex Metrika, Yandex Webmaster and DaData. Orders, stocks, prices, reviews, chats, CRM leads, ad stats and company lookup by INN; write actions require explicit confirmation.
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      MCP 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.
      197
      744 PyPI
      5
      MIT

    TDQS

    A3.7/5.0

    Scored across 39 tools

    Disambiguation4/5

    Almost every tool is scoped to one marketplace plus action (wb_card vs ozon_card vs cian_card), and the descriptions explicitly delineate near-neighbours like wb_categories → wb_category_products → wb_search and compare_prices vs per-source search. Two genuine ambiguities remain: compare_sources and marketplace_sources both answer 'which marketplaces are available?', and wb_card vs wb_root_info both read WB card data for a SKU (the latter for imt_id) with only subtle framing difference.

    Naming Consistency5/5

    Every tool follows a strict <source>_<action> convention with a tiny, predictable action vocabulary (search, card, reviews, seller, categories). The intentional singular/plural distinction (detmir_categories = browse tree, detmir_category = list products) is applied consistently across WB and Detsky Mir, and no camelCase or verb-style drift appears anywhere.

    Tool Count3/5

    39 tools is heavy and exceeds the comfortable 3-15 band, but it is not padded: the surface is 13 marketplaces each needing at least search+card, plus a compare layer. Each tool earns its place, though the long tail of near-identical search/card pairs (taobao, lamoda, dns, citilink, aliexpress, megamarket) makes the roster feel larger than the average agent will ever explore.

    Completeness4/5

    Exceptionally thorough for a price-research server: search, card detail, reviews, buyer questions, seller identity, category trees, cross-marketplace comparison, offer verification, plus health/source diagnostics that prevent false 'no results' conclusions. Gaps are secondary rather than blocking — seller/entity lookup exists only for WB and Avito, review tooling exists only for WB/Ozon (elsewhere folded into the card), and there is no price-history tool outside Cian.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled