Skip to main content
Glama
ztemerbekov

A1 Yandex KIT MCP

Related Servers

Alternatives to A1 Yandex KIT MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      MCP server for Yandex Merchants API enabling management of product offers (prices, discounts, hide/show) via natural language from AI assistants like Claude and Cursor.
      13
      70 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A standalone MCP server that exposes the admin side of kitcommerce-api as tools, enabling AI assistants to manage products, categories, collections, coupons, orders, inventory, customers, and the dashboard.
      30
      1
      ISC
    • A
      license
      B
      quality
      A
      maintenance
      Production-grade MCP server for RetailCRM e-commerce CRM. Provides 39 tools and 2 prompt skills to manage orders, customers, products, inventory, payments, tasks, references, and analytics via API v5.
      39
      29 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Production-grade MCP server for RetailCRM e-commerce CRM, providing 39 tools and 2 prompt skills to manage orders, customers, products, inventory, payments, tasks, references, and analytics via API v5. Token-efficient summary outputs by default, Docker-ready, and supports both stdio and HTTP transports.
      39
      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
      3
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Universal MCP server for the Avito API (Russia's largest classifieds marketplace), built for autonomous AI agents to operate an account hands-free — 145 tools across 18 domains (listings, messenger, orders, delivery, promotion, autoload, reviews, analytics). Safe-by-default: dry-run, idempotency, structured errors, confirmation flow.
      144
      76 npm
      17
      MIT

    TDQS

    A3.5/5.0

    Scored across 88 tools

    Disambiguation3/5

    Most tools are clearly separated by resource, and descriptions are unusually detailed. However, list_products vs list_variants is a genuine selection trap, kit_request overlaps every dedicated tool, and pairs like update_variant/bulk_update_prices or update_discount/discount_action create boundary ambiguity. Agents will need careful prompting to avoid misselection.

    Naming Consistency3/5

    Most names follow snake_case verb_noun conventions (list_, get_, create_, update_), which is readable and predictable. But the *_action suffix tools (discount_action, category_action, warehouse_action, variant_action), bulk_update_prices, and plural-noun 'get' methods like get_customer_orders and get_order_addons break the otherwise consistent pattern.

    Tool Count1/5

    At 88 tools, the surface is far beyond the well-scoped 3-15 tool range and well past the 50+ extreme threshold. Even though the underlying API is broad, this many parallel tools create severe selection and context-window overhead rather than a coherent agent-facing interface.

    Completeness4/5

    The server covers nearly every e-commerce domain: catalog, variants, pricing, orders, customers, discounts, promocodes, content, videos, webhooks, and more, with lifecycle operations like archive/restore and status transitions. Minor gaps exist in dedicated tools (e.g., no delete_blog, no delete_characteristic, no permanent product/category deletion), but search_operations + get_operation_schema + kit_request fill those gaps.

    Maintenance

    ActivityActive
    ResponsivenessResponsive