Skip to main content
Glama
Raleose

ozon-customer-mcp

by Raleose
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to ozon-customer-mcp

No user-submitted related servers found.

    Related Servers

    • marketplace-mcp

      YegorMy
      A
      license
      D
      quality
      C
      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
      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

    • dns-customer-mcp

      Raleose
      A
      license
      A
      quality
      B
      maintenance
      Enables querying DNS Shop product data via MCP: search, product details, reviews, specifications, variants, categories, brand catalogs, availability by city, and store listings.
      18
      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.2/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool maps to a distinct resource/action: search vs category browsing vs filters, product details vs specs vs variants vs offers vs reviews vs questions, and seller info vs seller catalog vs city lookup vs city setting. No two tools appear to do the same thing; close pairs like ozon_search and ozon_category_browse are clearly separated by text-search vs department-browsing.

    Naming Consistency3/5

    All tools share the consistent ozon_ prefix, which helps recognize them as a family. However, naming conventions are mixed: many are noun-first resources (ozon_product_details, ozon_seller_catalog) while several are verb-first actions (ozon_search_cities, ozon_set_city, ozon_compare_products), and ozon_search contains no noun at all. It is readable but not a uniform verb_noun pattern.

    Tool Count4/5

    19 tools is above the typical 3–15 sweet spot and feels slightly heavy, but the toolset covers a broad e-commerce domain with distinct workflows: search, category browsing, product details, variants, reviews, questions, offers, seller/brand catalogs, comparison, and delivery-city management. Each tool earns its place, so the count is reasonable rather than bloated.

    Completeness5/5

    The surface covers the full product-research lifecycle: category discovery, search/filtering, product details/specs/variants, social proof via reviews/questions/offers/seller info, comparison and related products, and delivery-location setup. There are no obvious dead ends or missing critical operations for a browsing-focused Ozon customer assistant.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources