Amazon Seller Central MCP Server

Amazon Seller Central

Marketplace sellers run orders, FBA inventory, listings, catalog research, competitive pricing, sales metrics, settlements, and flat-file reports across Amazon marketplaces.

First moves

1. Marketplace participations — discover seller id and active marketplace ids before any marketplace-scoped read.
2. Catalog search — find ASINs by keyword or product identifier in one marketplace.
3. Competitive pricing — price summaries for ASINs returned from catalog search.
4. Orders — list orders with created-after / created-before windows; open line items per order id.
5. Inventory — FBA inventory summaries when fulfillment stock matters.
6. Sales metrics — revenue and unit trends over a bounded interval.
7. Financial events — posted charges, fees, and refunds within a date window.

Data model

Seller → Marketplace → ASIN / SKU → Order → Order items. Listings are seller SKUs tied to ASINs per marketplace. Reports are async jobs that produce downloadable flat files when processing completes.

Operational order

1. Anchor marketplace ids from participations — most reads require an explicit marketplace scope.
2. Catalog search when you need ASINs; keywords and identifiers are mutually exclusive in one call.
3. Pull competitive pricing for ASINs discovered in step 2.
4. List orders with tight created-after filters — avoid unbounded national scans; paginate with continuation tokens.
5. Open order line items only for order ids returned in step 4.
6. Use inventory summaries, sales metrics, and financial events for stock, revenue, and settlement questions.
7. Listings — search active listings, open one SKU, then create, update (dry-run validation available), or delete when catalog permissions allow. Listing and shipment writes preview until confirm_write.
8. Reports — request a report type for a marketplace, poll until complete, then fetch the document download in the same session.

Order fulfillment

Daily ops list recent unshipped orders, inspect line items for sku and quantity, then confirm shipment with carrier and tracking when ready. Buyer name, full street address, and phone are not exposed in this bundle — operational order fields only. Shipment confirmation still needs appropriate Seller Central permissions for direct-to-consumer shipping.

Listing and catalog ops

Listing health checks search active SKUs and read issue payloads on each result. Catalog research combines keyword search with competitive pricing for repricing or launch decisions. Listing creates and patches support validate-only mode to check payloads before committing.

Gotchas

• Regional partition — Americas, Europe, and Far East sellers use different API regions; scope reads to the partition where the account is registered.
• Seller Central roles — catalog search, pricing, finances, and listing writes each need the matching role grant on the connected app.
• Finances window — settlement event queries span at most 180 days; the end timestamp must be slightly before request time.
• Buyer PII — restricted buyer identity and address fields are out of scope here even when Seller Central shows them in the UI.
• Rate limits — usage plans vary by operation; paginate orders instead of repeating wide date windows.
• Report documents — download links expire quickly after a report reaches done status — fetch the document in the same workflow pass.
• Writes need confirmation — listing changes, shipment confirmation, and report creation default to preview; set confirm_write after user approval.