Amazon SP-API MCP

Amazon SP-API MCP

Open-source Amazon Selling Partner API MCP (mansournorouzi/amazon-sp-mcp). LWA-only auth — no AWS IAM keys — for orders, FBA inventory, fees, settlements, and Brand Analytics-style reports in Claude.

Added on Popularity 2

Details

Overview

Amazon SP-API MCP (mansournorouzi/amazon-sp-mcp) connects Claude and other MCP clients to Amazon Seller Central through the Selling Partner API. The README highlights LWA (Login with Amazon) OAuth-only authentication — no AWS IAM credentials — which matches Amazon's post-2023 SP-API auth model and simplifies seller setup.

Typical use cases: pull orders and order items, inspect FBA inventory health, estimate fees, read settlement and reimbursement reports, and query sales/traffic or search-term analytics when your SP-API roles allow.

Key Features

  • Orders: List orders by date/status/channel and inspect order details/items.
  • Inventory: FBA summary and detailed reserved/unfulfillable breakdowns.
  • Financial reports: Reimbursements, settlements, fee estimates, storage and long-term storage fee reads.
  • Analytics: Sales & traffic style metrics; Brand Analytics search terms when Brand Registry / roles permit.
  • Inventory ledger: Movement and adjustment visibility for reconciliation workflows.
  • Marketplace configuration: Documented marketplace IDs and NA/EU/FE SP-API endpoints.

How to Use

  1. Install an MCP-compatible host (Claude Desktop, Cursor, Claude Code, etc.).
  2. Clone or install the server from https://github.com/mansournorouzi/amazon-sp-mcp and follow the README for build / npx / Docker commands.
  3. Create API credentials for the underlying platform and put them in the MCP env block — never commit secrets.
  4. Register the server in your client MCP config (Claude Desktop claude_desktop_config.json or Cursor mcp.json), then restart the client.
  5. Start with read-only prompts; enable write tools only after you understand scopes and confirmation settings.

Pricing

The MCP server is open source. Amazon SP-API access requires a Seller Central account and a developer application with LWA client id/secret and refresh token. Amazon may charge for certain APIs or impose role approval; the MCP repo itself is free to self-host.

Plan Billing Price Notes
amazon-sp-mcp — Free (OSS) Node 18+; self-host
Amazon SP-API Amazon seller / developer Per Amazon LWA credentials + role approval

Best For

Amazon sellers and operators who want Claude to answer operational questions from live SP-API data (orders, inventory, fees) without maintaining one-off scripts.

FAQ

AWS keys required?

The project advertises LWA-only auth — no AWS credentials — aligned with modern SP-API requirements.

Is this an official Amazon MCP?

No. It is a community GitHub project. Prefer Amazon's own developer docs for API contracts and ToS.

What env vars are needed?

LWA client id/secret, refresh token, seller id, marketplace id, and optional SP-API endpoint overrides as documented in the README.

Brand Analytics tools?

Search-term style tools typically need Brand Registry and the corresponding SP-API roles; without them those calls will fail.