MoySklad MCP Server
Related Servers
Alternatives to MoySklad MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP servers for Russian commerce and marketing APIs: Wildberries, Ozon, Yandex Market, Avito, Bitrix24, amoCRM, Yandex Direct, Yandex Metrika, Yandex Webmaster and DaData. Orders, stocks, prices, reviews, chats, CRM leads, ad stats and company lookup by INN; write actions require explicit confirmation.MIT
- 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
- 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
- AlicenseNot gradedqualityDmaintenanceMCP server for Fulfil.io ERP with 29 tools for inventory, orders, shipments, customers, purchasing, returns, warehouse operations, and analytics. Integrates with Claude Desktop and other MCP clients via Fulfil.io REST API v2.6 npmMIT
- AlicenseCqualityBmaintenanceMCP 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.156147 PyPI11MIT
- AlicenseBqualityCmaintenanceWildberries Seller API MCP server providing 15 tools for managing products, prices, stocks, orders, sales, warehouses, supplies, statistics, feedbacks, and ABC analysis with built-in rate limiting and 409 penalty protection.3016MIT
TDQS
Scored across 60 tools
Most tools have clearly distinct purposes, but there is some overlap among stock reports (get_stock, get_stock_by_store, get_stock_current) and among search tools (search_products, search_assortment, search_variants). The descriptions help resolve ambiguity, but an agent might still struggle to pick the right one in edge cases.
The naming mostly follows a consistent verb_noun pattern (search_*, get_*, create_*, update_*, list_*, delete_*). However, there is a mix of 'get' and 'list' for collection endpoints (get_orders vs list_invoices_out), and some verbs are more specific than others (update_prices, update_customer_order_status). Overall, the pattern is readable and predictable.
With 60 tools, this is far beyond the 25+ threshold for 'too many'. Even for an ERP-like system like MoySklad, the sheer number makes the toolset unwieldy and difficult for an agent to navigate efficiently. The scope is broad, but the count is excessive.
The toolset covers a wide range of MoySklad operations, including products, orders, stock, payments, webhooks, and reports. However, there are notable gaps: many entities only have create and read but lack update and delete (e.g., products, counterparties, payments). The generic get_documents/get_document partially compensate, but the missing CRUD operations create dead ends.