Skip to main content
Glama
ilyautov

marketplaces-mcp-ru

by ilyautov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to marketplaces-mcp-ru

No user-submitted related servers found.

    Related Servers

    • mcp-ozon-seller

      woyaxnini
      A
      license
      A
      quality
      D
      maintenance
      MCP server for Ozon Seller API that enables AI clients to manage products, prices, stocks, orders, analytics, and finances on Ozon marketplace.
      26
      32 npm
      6
      -

    • marketplaces-mcp-ru

      hehca42y1900
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to Wildberries and Ozon seller accounts for real-time access to sales, stocks, prices, finances, and reviews through official APIs.
      MIT

    • wb-mcp-server

      DeviceIngineering
      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
      3
      MIT

    • wildberries-mcp-ru

      ilyautov
      A
      license
      A
      quality
      A
      maintenance
      Wildberries seller API in your AI assistant: sales and stocks, product cards, prices and promotions, financial reports and reviews. 307 methods across all 17 Wildberries hosts live in a YAML catalog the server executes, the agent searches it in plain language, and every method carries an access class so writes and irreversible calls ask for confirmation.
      25
      1
      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

    A3.9/5.0

    Scored across 126 tools

    Disambiguation4/5

    The five marketplace prefixes (wb_, ozon_, ozon_perf_, ym_, avito_) cleanly separate otherwise identical tool families. Within a service, call_method, get_raw, and fetch_all are distinguishable by catalog-id vs raw-path vs auto-pagination, though convenience wrappers like wb_set_price and wb_write_method could briefly cause hesitation.

    Naming Consistency4/5

    Tools overwhelmingly follow a {marketplace}_{verb}_{noun} snake_case pattern, including the nested ozon_perf_ family. Minor deviations like avito_whoami and standalone convenience wrappers (wb_get_sales, ozon_get_products) break the strict verb_noun rhythm, but the overall scheme is predictable.

    Tool Count1/5

    126 tools is far beyond the recommended range and matches the rubric's extreme mismatch threshold. The five-marketplace scope explains some repetition, but the resulting surface still overwhelms agent context and makes tool selection disproportionately expensive.

    Completeness5/5

    Each marketplace receives a full lifecycle: auth and cabinet management, endpoint discovery, generic read/write/delete with raw fallbacks, auto-pagination, and convenience wrappers for core entities like prices, stocks, orders, and products. Common seller workflows have no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources