Skip to main content
Glama
SZhukovWork

wildberries-mcp

by SZhukovWork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to wildberries-mcp

No user-submitted related servers found.

    Related Servers

    • WB MCP Server

      u1ch1
      F
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to retrieve a Wildberries seller's product cards and customer reviews through the official Content and Feedbacks APIs.
      2
      16 npm
      -

    • yandex-market-mcp

      SZhukovWork
      A
      license
      A
      quality
      C
      maintenance
      Enables LLM agents to fetch live Yandex Market data via plain HTTP, with honest labeling of prices (pay-card vs plain vs discounted), sponsored tiles, seller and model-group ratings, reviews, questions, and seller legal details. It avoids common scraped-data traps such as misleading discounts, captcha pages, and cross-border or conditional offers.
      7
      MIT

    • ozon-mcp

      SZhukovWork
      A
      license
      A
      quality
      C
      maintenance
      Enables LLM agents to retrieve live, accurately-labelled product data from Ozon's public storefront, including search with pagination and sorting, all price variants, delivery dates, seller legal details, variants, and SKU-specific ratings and reviews, all without an Ozon account.
      4
      MIT

    • wildberries-mcp

      shndo1337
      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.
      -

    • marketplace-mcp

      stitcman
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets 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.
      50 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 5 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources