Skip to main content
Glama

Related Servers

Alternatives to InSales MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to connect marketplace seller accounts, explore and call shop-level APIs, and manage orders, products, returns, inventory, pricing, and tracking with scoped read-only or read-write access.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to work with one or many Horoshop stores through the public API, control panel and storefront cart — reading and updating the catalog, processing orders, managing SEO, redirects, marketplace feeds, design and settings. Write operations preview changes by default, require confirmations for bulk or irreversible actions, and verify results by reading them back.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to connect once to self-hosted, user-owned upstream accounts and then discover and invoke granted tools through a single authenticated endpoint. Each client receives its own key with deny-by-default tool grants, while sensitive calls require durable human approval and credentials stay encrypted and never forwarded upstream.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI tools to use a store key to access a local marketplace for AI skills, MCP packages, and knowledge bundles, including browsing published items and supporting account-based submissions with admin review.
      MIT

    TDQS

    A4.5/5.0

    Scored across 2 tools

    Disambiguation3/5

    Both tools run JavaScript against the same InSales runtime, and execute_write can also perform reads, so the main boundary is write permission rather than a distinct operation type. Descriptions clarify the read/write split, but selection still requires understanding execution_id/idempotency and the permission model.

    Naming Consistency5/5

    Both tools follow the same execute_read / execute_write verb-permission pattern, which is predictable and consistent. There is no mixing of conventions.

    Tool Count3/5

    The server exposes only two meta-tools for the entire InSales API, and both carry long, nearly identical execution instructions. This may be intentional for a generic gateway, but it falls into the borderline 1-2 tool range.

    Completeness5/5

    Through catalog discovery and generic insales.<method> calls, the tools can cover arbitrary read and write operations. Result references, schema inspection, and idempotent writes round out the surface with no obvious lifecycle gaps for a gateway design.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues