Skip to main content
Glama
narkov

horoshop-mcp-server

by narkov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to horoshop-mcp-server

No user-submitted related servers found.

    Related Servers

    • nanocart-mcp

      ByteBunny-io
      A
      license
      A
      quality
      B
      maintenance
      Official MCP server for NanoCart, enabling AI agents to manage products, orders, coupons, categories, subscribers, settings, and pull sales reports from your store.
      31
      48 npm
      MIT
    • Melbis Shop by melbis

      Melbis Shopofficial

      melbis
      F
      license
      B
      quality
      A
      maintenance
      Official MCP server of Melbis Shop, a self-hosted e-commerce platform: an AI agent works in the store as an employee — project files with version history, database, catalogue trees, product files and storefront pages — under a staff login with per-command permissions. Ships with the Windows client; 56 built-in tools plus store-specific tools with a permission on every command.
      56
      3
      -

    • SellerChamp MCP Server

      WowWashington
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to manage multi-marketplace e-commerce operations by connecting to the SellerChamp API. It supports inventory reporting, cross-listing analysis, order management, and bulk updates across platforms like Amazon, eBay, and Shopify.
      -

    • Clind MCP Server

      lirad
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      A Shopify-focused MCP server that enables AI agents to manage store operations like order tracking, product discovery, and checkout link generation. It facilitates customer-facing interactions including shipping estimates and real-time inventory searches.
      -
    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

    B3.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools are clearly distinct (list vs get, orders vs products), and auth is separate. However, horoshop_call_api is a catch-all that could overlap with any tool, introducing some ambiguity about when to use it versus the specific tools.

    Naming Consistency5/5

    All tools follow the consistent pattern horoshop_ + verb + noun (e.g., list_orders, get_order, update_order_status). The only minor deviation is horoshop_auth, but it is still a recognizable action and fits the style.

    Tool Count5/5

    With 7 tools, the count is well-scoped for a typical e-commerce API integration. Each tool covers a distinct core operation without unnecessary bloat or sparseness.

    Completeness4/5

    The core workflows for orders (list, get, update status) and products (list, get) are covered. Missing product creation/update and order creation are notable, but the horoshop_call_api fallback fills these gaps, making the surface reasonably complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources