Amazon Selling Partner API MCP server

Retail-side analytics for a seller account, read-only by construction.

Connect Amazon Selling Partner API All connectors

Tools: 5
Read-only: 5
Write: 0; Off by default
Destructive: 0; Flagged distinctly

What it does

Amazon Selling Partner API through an assistant

FBA inventory levels, product pricing, and sales and traffic performance across the marketplaces you authorise -- the retail context that explains what advertising numbers alone can't. There is no write tool in this connector at all, and a test enforces that. It also feeds the Amazon Ads root-cause analysis when both connections exist in the same workspace.

FBA inventory levels by ASIN
Current product pricing and competitive context
Sales and traffic performance: units, ordered sales, sessions, page views
Buy Box share movement between two periods
Marketplace participation discovery across regions
Read-only throughout -- no write tool exists to enable

Ask your assistant

What people actually ask

Real questions, answered from live Amazon Selling Partner API data.

“Which of my FBA ASINs are close to running out of stock?”

amazon_spapi_inventory_status

“How did sessions and conversion move across my marketplaces last month?”

amazon_spapi_retail_performance

“Did my Buy Box share change between these two periods?”

amazon_spapi_retail_context_analysis

Tool catalogue

5 Amazon Selling Partner API tools

Grouped by what they touch. Every tool is individually toggleable — you expose only what you want.

All tools

5 tools5 read-only · 0 write

Showing 5 of 5 tools

amazon_spapi_inventory_status
Read-only
FBA inventory levels for this marketplace -- fulfillable/inbound/reserved quantities per SKU. Synchronous, no polling needed.
amazon_spapi_list_marketplace_participations
Read-only
List every marketplace this connection's token can see, across all three regions (North America, Europe, Far East) -- not filtered to just the ones authorized on this connection. Use this to find marketplace IDs to authorize from Settings -> Connections -> Manage Marketplaces.
amazon_spapi_pricing
Read-only
Current competitive pricing and offers for up to 20 ASINs in this marketplace, including Buy Box status. Synchronous, no polling needed.
amazon_spapi_retail_context_analysis
Read-only
Retail-side signals (Buy Box percentage change) for two periods, in the shape amazon_ads_roas_root_cause's retailContext input expects. Fetches one report spanning both periods, which can take longer than one call allows -- see report_id for resuming. newStockouts and priceChanges are always empty under ServeMCP's live-fetch model -- FBA Inventory and Product Pricing are current-state-only APIs with no historical endpoint, so there is nothing to diff against period1. Not a bug: documented here rather than fabricated.
amazon_spapi_retail_performance
Read-only
Live retail sales and traffic (sessions, page views, units ordered, ordered sales, plus derived unit session % and average selling price) for a date range, aggregated and broken out by day. Runs Amazon's report generation internally (this can take longer than one call allows) -- if the response has status 'processing', call this tool again with the same report_id to resume; do not start a new one.

Every tool name and description, machine-readable: /llms-full.txt

Access & safety

You decide what it can touch

The same model applies to every connector, and it defaults closed.

Authorize once

Connect Amazon Selling Partner API through its own consent screen. Credentials are encrypted with AES-256-GCM and never returned by any API response or tool call.

Writes off by default

A new connection switches on a read-oriented default set only. Every write tool must be enabled deliberately before any client can call it.

Roles enforced server-side

READ, WRITE and ADMIN gate tool invocation on the server, not just in the UI. A READ member's token is refused any write tool.

Setup

Connect Amazon Selling Partner API in minutes

No infrastructure to run. Copy one URL and one token into your client.

1Create a free workspace and connect Amazon Selling Partner API.
2Choose which tools to expose — writes stay off until you enable them.
3Copy your MCP endpoint URL and bearer token.
4Paste them into Claude, Cursor, or any MCP client.

claude_desktop_config.json

{
  "mcpServers": {
    "serve-mcp": {
      "url": "https://servemcp.com/api/mcp/your-workspace",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer smcp_..."
      }
    }
  }
}