Skip to main content
Glama
woraphol-j

LINE Shopping API MCP

by woraphol-j

Related Servers

Alternatives to LINE Shopping API MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      MCP server that integrates the LINE Messaging API to enable AI agents to send messages and manage LINE Official Accounts.
      12
      883 npm
      783
      Apache 2.0
    • A
      license
      Not graded
      quality
      F
      maintenance
      Model Context Protocol server implementation that integrates the LINE Messaging API to connect AI agents with LINE Official Accounts, enabling agents to send messages to users.
      883 npm
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      An open-source MCP server that wraps the Shopline Open API into 143 AI-callable tools for e-commerce data analysis, enabling AI agents to query orders, products, inventory, customer behavior, and promotions from Shopline stores through natural language.
      100
      20
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      AI-powered MCP server for managing LINE Official Accounts. Send broadcasts, push messages, check analytics, manage rich menus — all through natural language via Claude, ChatGPT, or Cursor. 10 tools included: * Account info, friend count, message quota * Broadcast, push message, multicast * Delivery stats, user profiles, follower list * Rich menu management Supports 95M+ LINE users across Jap
      10
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for the Shopline Open API. Exposes 140+ tools for querying and managing orders, products, customers, promotions, analytics, and store settings from your Shopline store via Claude.
      100
      MIT

    TDQS

    C2.7/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools target distinct resources and actions. However, Adjust_inventory overlaps with Increase_inventory and Decrease_inventory, as it also adjusts inventory by an amount, causing potential confusion. The order and product tools are well-separated.

    Naming Consistency3/5

    Naming follows a mix of conventions: mostly verb_noun (e.g., Create_product), but some are noun_noun (Order_detail, Settlement_detail) or lengthy phrases (Send_message_via_OA_Plus_flex_message_services). Inconsistent use of 'Get' prefix (Get_all_orders vs Order_detail) adds to the inconsistency.

    Tool Count5/5

    22 tools cover the major operations of a shopping API: product and variant CRUD, order management, inventory adjustments, checkout, messaging, and settlements. This is a well-scoped set for the domain without being overwhelming.

    Completeness3/5

    The tool surface covers core product and order workflows, but lacks inventory querying (no get_inventory), order creation (orders are presumably customer-initiated), and refund/return operations. Also missing category management, though categories are referenced in product tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues