Skip to main content
Glama

Related Servers

Alternatives to amazon-seller-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      D
      maintenance
      A local MCP server that enables querying Amazon Selling Partner API for profitability analysis (revenue, fees, COGS, net margin) and inventory alerts (FBA stock levels and low-stock warnings) using read-only operations.
      9
      -
    • A
      license
      Not graded
      quality
      B
      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
    • A
      license
      Not graded
      quality
      C
      maintenance
      A local, read-only MCP server that reconciles Stripe payouts against bank deposits and QuickBooks or Xero books against bank statements month by month from existing CSV exports, reporting what does not tie with the likely reason. It accepts file paths only, requires no account or bank linking, and writes nothing.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      agentcentral is a hosted MCP server for Amazon sellers that connects Claude, ChatGPT, and other AI clients to Amazon Ads, Seller Central, inventory, orders, catalog, rankings, finance, and fulfillment data. It provides fast reads from pre-materialized Amazon data, scoped API keys, OAuth-based Amazon connections, encrypted tokens, per-tenant isolation, and guarded write tools with audit log
      100
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects Amazon Seller Central and Amazon Advertising to any MCP client, with a settlement-accurate P&L underneath: every fee, refund and reimbursement as Amazon actually posted it, so contribution margin and breakeven are per product, per marketplace, per day. 107 tools spanning P&L, full Sponsored Products/Brands/Display management, Search Query Performance and Brand Analytics, inventory and for
      1
      MIT

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing local settlement files, reading one report's totals, grouping one report by SKU, and explaining live-data onboarding. The two report-reading tools are differentiated by whole-report summary versus per-SKU breakdown.

    Naming Consistency3/5

    All names use snake_case, but the conventions are mixed: list_settlement_reports and read_settlement_report use verb_noun, while settlement_profit_by_sku and agentxray_live_setup are noun-phrase style. Still readable, but not a predictable pattern across the set.

    Tool Count5/5

    Four tools are well-scoped for a settlement-report-focused server: one listing tool, two analysis tools, and one conditional onboarding helper. The count is small but each tool has a clear role.

    Completeness4/5

    The core settlement workflow is covered: discover local files, read totals, and break down profit by SKU. Minor gaps exist around multi-report comparison or date filtering, and the live-data option is only described rather than implemented as query tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues