Skip to main content
Glama

Related Servers

Alternatives to mcp-amazon-sp-api

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Amazon Selling Partner API and Advertising API, enabling access to orders, inventory, pricing, ads, and reports via natural language.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Amazon Seller Central MCP server. Connect Seller Central, Vendor Central and Amazon Ads to Claude, ChatGPT, Gemini or Cursor, and ask for net profit per SKU with your own COGS, VAT and FBM shipping costs, PPC down to the search term, SQP, inventory and listing health.
      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
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables building and running zero-dependency MCP servers with automatic JSON Schema generation, exposing Python tools to Claude Desktop, Cursor, and autonomous agent fleets.
      2
      Apache 2.0
    • 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.4/5.0

    Scored across 53 tools

    Disambiguation2/5

    There is significant overlap among tools related to pricing and competition (e.g., analyze_competitor_prices, compare_with_competitors, get_competitive_pricing, get_competitor_offers) and among inventory reporting tools (get_fba_inventory, get_inventory, get_fba_fees_report, get_profitability_report). This ambiguity would likely cause an agent to select the wrong tool.

    Naming Consistency4/5

    Tool names consistently follow verb_noun pattern (get_, list_, update_, check_, request_), with no mixing of casing styles. A few prefixes (check_, request_) deviate from the majority get_/list_/update_, but the pattern remains predictable overall.

    Tool Count2/5

    With 53 tools, the server is overly large for typical MCP usage. While it covers a broad domain (Amazon SP API), the high count increases cognitive load and makes it harder for agents to navigate. A more focused subset would improve coherence.

    Completeness3/5

    The tool set covers many essential areas (orders, inventory, listings, reports, A+ content, fees), but notable gaps exist: no tool for creating listings (only updating), no advertising management, and no returns processing beyond reporting. This leaves some workflows incomplete.

    Maintenance

    ActivityStale
    ResponsivenessNo issues