A1 Yandex KIT MCP
Related Servers
Alternatives to A1 Yandex KIT MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for Yandex Merchants API enabling management of product offers (prices, discounts, hide/show) via natural language from AI assistants like Claude and Cursor.13114 npmMIT
- AlicenseAqualityDmaintenanceA 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.3942 npm2MIT
- AlicenseNot gradedqualityBmaintenanceTurns an online store's catalog into MCP tools so agents can search products, fetch details, look up barcodes, analogs, categories, promotions and pickup points, and hand off a cart as a payment link rather than checking out. It is driven by a single TOML config with capability-based tool sets, bilingual model-facing texts, public catalog access plus OAuth 2.1-scoped personal tools like order history, and ready adapters for YML/Google Merchant feeds and WooCommerce across ten store engine presets.Apache 2.0
- AlicenseAqualityCmaintenanceProduction-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.197687 PyPI9MIT
TDQS
Scored across 97 tools
Tools are overwhelmingly resource-specific, and descriptions sharply distinguish close pairs such as list_products vs list_variants and the manage_*_objects family. A few generic lifecycle tools (variant_action, discount_action) and the meta tools require reading descriptions, but misselection risk is low.
Almost all names use snake_case, but the pattern is not perfectly uniform: many tools use verb_noun (create_variant, update_discount), while several lifecycle tools use noun_action (warehouse_action, category_action). The mix remains predictable and readable.
97 tools is far beyond the 3-15 well-scoped range and pushes into extreme surface area even for a broad e-commerce platform. The kit_request escape hatch already exists, so many dedicated tools feel like optional redundancy or candidates for consolidation.
Coverage is very broad across catalog, orders, customers, promotions, webhooks, warehouses, media, and an escape hatch to all 179 API operations. Some resources such as gift cards have only read operations, and a few CRUD paths rely on kit_request or soft-delete actions, but there are no hard dead ends.