Skip to main content
Glama
A1-x-Tech

Yango Tech Retail MCP

by A1-x-Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Yango Tech Retail MCP

No user-submitted related servers found.

    Related Servers

    • yandex-market-mcp-ru

      ilyautov
      A
      license
      A
      quality
      A
      maintenance
      Yandex Market Partner API in your AI assistant: orders and returns, products and cards, prices and tariffs, reports, reviews and chats. 165 methods 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.
      26
      320 PyPI
      1
      MIT

    • yandex-lavka-mcp

      Dudude-bit
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to search products, manage a cart, and place orders with Yandex Lavka, requiring explicit human confirmation before charging.
      17
      16
      MIT

    • Korral StoreLink MCP

      kartparash-cmd
      F
      license
      A
      quality
      C
      maintenance
      Enables an AI grocery replenishment agent to interface with Korral's StoreLink stock API, providing tools to look up SKUs, get stock positions and gaps across stores, create replenishment orders (with buyer approval), and track order status.
      4
      -

    • mcp-yandex-dostavka

      A1-x-Tech
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Yandex Delivery B2B API, enabling natural language interaction to calculate delivery costs, create and manage express and platform delivery orders, track couriers, and handle pickup points.
      16
      79 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 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (price lists, orders, order state, events, receipts, stores, products, prices, discounts, stocks). Even similar tools like get_order and get_orders_state are clearly separated by their descriptions, making selection unambiguous.

    Naming Consistency5/5

    Tool names follow a consistent pattern: 'query_' for cursor-based feeds, 'get_' for direct retrieval, 'create_', 'set_', 'update_', 'cancel_' for writes, and 'raw_request' as an explicit escape hatch. The verbs are meaningful and consistent, with no mixed conventions.

    Tool Count4/5

    16 tools is slightly above the typical well-scoped range but appropriate for a comprehensive retail API that spans orders, catalog, pricing, inventory, discounts, and receipts. Each tool serves a distinct purpose, and the count feels justified rather than bloated.

    Completeness4/5

    Core workflows are covered with dedicated tools for order creation/cancellation/query, product listing/creation, price get/set, stock query/update, and discount creation. Some operations (e.g., order update, price list creation, product update) lack dedicated tools but are reachable via raw_request, so agents can work around minor gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources