A1 Yandex KIT MCP
Related Servers
Alternatives to A1 Yandex KIT MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for Yandex Merchants API enabling management of product offers (prices, discounts, hide/show) via natural language from AI assistants like Claude and Cursor.1347 npmMIT
- AlicenseAqualityCmaintenanceA 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.301ISC
- AlicenseBqualityBmaintenanceProduction-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.3937 npm1MIT
- AlicenseAqualityBmaintenanceProduction-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.39MIT
- AlicenseCqualityBmaintenanceMCP 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.1973MIT
- AlicenseAqualityAmaintenanceUniversal 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.144209 npm18MIT
TDQS
Scored across 91 tools
Every tool targets a distinct resource and action, and potentially confusing pairs like list_products vs list_variants or upload_video vs upload_video_from_url are explicitly disambiguated in their descriptions. Even the many *_action tools are cleanly separated by resource, and kit_request is clearly framed as an escape hatch rather than a parallel path.
The overwhelming majority follow a predictable verb_noun snake_case pattern (list_*, get_*, create_*, update_*, delete_*, manage_*). Minor deviations like kit_request and the resource_action tools (variant_action, discount_action) break the pattern slightly, but they remain readable and follow a consistent style overall.
91 tools is far beyond the 25+ upper bound for a well-scoped set and crosses the 50+ threshold for an extreme mismatch. Even though the server wraps a large commerce API, the presence of search_operations and kit_request as an escape hatch makes this many dedicated tools excessive and cognitively overwhelming for an agent.
The surface covers full lifecycle management for products, variants, categories, collections, orders, customers, discounts, promocodes, warehouses, files, videos, characteristics, blogs, webhooks, and alerts. Minor gaps exist such as no dedicated permanent delete for products or variants, but archive actions and the kit_request escape hatch cover these dead ends.