Skip to main content
Glama
ilyautov

moysklad-mcp-ru

by ilyautov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to moysklad-mcp-ru

No user-submitted related servers found.

    Related Servers

    • moysklad-mcp-ru

      marfarin
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to read and write MoySklad inventory, orders, reports, and documents via JSON API 1.2 with safety gates.
      -

    • MoySklad MCP Server

      theYahia
      A
      license
      C
      quality
      B
      maintenance
      MCP server for MoySklad (МойСклад) warehouse and CRM management API. 21 tools covering the full order lifecycle: products, stock, counterparties, customer orders, shipments, supplies, warehouses, organizations, reports, and webhooks.
      60
      49 npm
      6
      MIT

    • bas-mcp-server

      qkiomat
      F
      license
      A
      quality
      C
      maintenance
      Enables AI agents to interact with 1С:Enterprise and BAS ERP systems through REST and HTTP services, providing tools for searching catalogs, creating documents, and querying stock balances.
      6
      -

    • mcploy

      ogarciabrena
      A
      license
      A
      quality
      B
      maintenance
      Exposes the Loyverse API as MCP tools to manage stores, products, inventory, customers, receipts, and more from AI assistants.
      54
      MIT

    • SmartUp MCP

      ASPanferov
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to read orders, stock, prices, contractors, payments, debts, and sales from SmartUp ERP, with optional write capabilities for creating and updating orders and contractors when explicitly enabled.
      19
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 36 tools

    Disambiguation3/5

    Several tool families overlap: catalog navigation (ms_list_sections vs ms_get_section vs ms_map vs ms_search_methods), generic execution vs raw paths (ms_call_method vs ms_get_raw), and the purchase-order-specific tools duplicate the generic document tools (ms_build_purchaseorder vs ms_build_document, ms_create_purchaseorder vs ms_create_document). Detailed descriptions help, but an agent could easily misselect when exploring the catalog or creating documents.

    Naming Consistency4/5

    Nearly all tools follow a consistent ms_verb_noun snake_case pattern with a uniform ms_ prefix, and verbs like get/create/post/delete are used predictably across families. Minor deviations include 'ms_map' and 'ms_ping' not following the verb_noun pattern, and some inconsistency between list and get for similar actions (ms_list_sections vs ms_get_section).

    Tool Count2/5

    36 tools is well above the 25-tool threshold and feels over-scoped. The set is inflated by multiple overlapping layers: catalog/metadata exploration, generic call/write/delete methods, raw-path fallbacks, and specialized build/create wrappers that duplicate the generic document tools. Several tools could be consolidated without losing functionality.

    Completeness4/5

    The surface covers the main MoySklad domains well: discovery, read/write/delete via the catalog, raw fallback, pagination, cabinet/auth management, common reports, and a full document lifecycle (preview, create, post, delete). Minor convenience gaps exist (e.g., no dedicated product/counterparty update or customer-order create), but the generic ms_write_method and raw tools provide escape hatches, so there are no true dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources