M.Video MCP
Related Servers
Alternatives to M.Video MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceMCP server for the Ozon Seller and Performance API: 151 tools for prices, promotions, ads, orders, returns, finance and analytics. Multi-store, encrypted keys, web dashboard and self-diagnostics; Docker with SSE or stdio.156194 PyPI5MIT
- 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.197126 PyPI3MIT
- AlicenseAqualityDmaintenanceMCP server for Ozon Seller API, enabling product, order, finance, and analytics management via natural language or CLI.32MIT
- AlicenseAqualityCmaintenanceAn unofficial MCP server for interacting with Pyaterochka (5ka.ru) grocery store, enabling product search, cart management, and order delivery.243MIT
- AlicenseAqualityDmaintenanceMCP server for Ozon Seller API that enables AI clients to manage products, prices, stocks, orders, analytics, and finances on Ozon marketplace.2646 npm6-
- 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.1355 npmMIT
TDQS
Scored across 12 tools
Each tool targets a distinct resource-action pair (stock, price, orders, shipments, mappings). Even the two order-read tools are clearly separated by 'orders' vs 'status updates'. No ambiguity in purpose across the set.
All tools use a consistent `mvideo_` prefix and snake_case. Most follow a resource_action pattern (e.g., stock_update, order_fbs_list), but `mvideo_health` breaks the pattern and action verbs vary between list/info/get/set. Still predictable overall.
12 tools is well-scoped for a marketplace integration covering core areas: locations, product mappings, stock, prices, orders, and shipments. Each tool has a clear purpose and the count feels neither sparse nor bloated.
The surface covers read/write for stock and price, read for mappings and locations, and a full FBS order workflow (list, status, labels, exemplar, shipment). Minor gaps exist (e.g., no product mapping update or order cancellation), but core operations are present.