Skip to main content
Glama
moneyan9
by moneyan9

Related Servers

Alternatives to rakuten-rms-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Remote MCP host for Rakuten RMS, providing Streamable HTTP endpoint with OAuth 2.1/PKCE and Bearer auth. It enables MCP clients like ChatGPT and Claude to access Rakuten RMS tools via natural language.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Official remote MCP server for Color Me Shop (GMO Pepabo). Manage orders, products, customers, coupons, and inventory of your online store through natural language.
      49
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Rakuraku Hanbai (楽楽販売) that enables Claude to call the official API for file upload, CSV import/export, and record CRUD operations through natural language. It supports authentication via API token and can be deployed on cloud platforms like Render.
      -
    • 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
    • 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
    • F
      license
      A
      quality
      B
      maintenance
      An MCP server that exposes marketplace seller operations (Shopee first) as tools Claude can call, enabling automation of product, pricing, inventory, customer service, and other seller tasks.
      32
      -

    TDQS

    C2.1/5.0

    Scored across 58 tools

    Disambiguation3/5

    Several tools have overlapping purposes, such as multiple inventory retrieval methods (rms_get_inventory, rms_get_variant_inventory, rms_bulk_get_inventory, rms_get_variant_lists) and product update methods (rms_update_price, rms_patch_product, rms_upsert_product). The rms_inquiries tool bundles count/list/detail/reply/read/complete operations into one, creating significant ambiguity for agents. While descriptions are clear, the sheer number of similar tools makes selection error-prone.

    Naming Consistency2/5

    Naming conventions are mixed: most tools follow a verb_noun pattern (e.g., rms_get_product, rms_update_orderer), but some place the verb at the end (rms_thanks_coupon_get, rms_inquiry_attachment_post). Noun-only names like rms_health and rms_inquiries, and adjective-noun names like rms_daily_sales, further break consistency. The irregular placement of actions across similar functions makes tool names unpredictable.

    Tool Count1/5

    With 58 tools, the server's tool count is excessively high, far beyond the typical range for an MCP server and making agent tool selection unwieldy. The broad domain coverage does not justify this count, as many tools could be consolidated (e.g., the inquiry operations could be split into separate tools or grouped). This is an extreme mismatch with recommended server scoping.

    Completeness4/5

    The server provides comprehensive coverage of core lifecycles for orders, products, inventory, coupons, and inquiries, including create, read, update, delete, and search operations. Notable features like payment info retrieval, shipping updates (sync and async), and analytics tools are present. Minor gaps exist (e.g., no explicit return/refund management), but overall the surface is well-rounded and functional.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues