Amazon Seller Central (SP-API)
Query your Amazon Seller Central account through the official Selling Partner API: orders, order items, product catalog, FBA inventory, buy-box offers, fee estimates, financial events and reports. Read-focused v1 across all Amazon marketplaces (US, EU, FE).
7 Tage gratis · keine Kreditkarte · EU-Hosting
Frag Amazon alles
Teste einen echten Prompt gegen Amazon Seller Central (SP-API) via AnythingMCP — Claude ruft die Tools auf, liefert die Antwort. Drück Enter auf deine eigene Nachricht, um auf Cloud zu installieren.
Amazon auf Cloud installierenClaude ist KI und kann Fehler machen. Bitte Antworten gegenprüfen.
Setup in 2 Minuten
- 1Free Trial auf cloud.anythingmcp.com starten.
- 2Im Connector-Store auf Amazon Seller Central (SP-API) klicken. Credentials einfügen.
- 3MCP-API-Key generieren und KI-Client auf die MCP-URL zeigen.
Anleitungen für Amazon
Schritt-für-Schritt-Setup für die wichtigsten KI-Clients.
- Vollständige Amazon Seller Central (SP-API)-Use-Case-Anleitung lesen
- Amazon Seller Central (SP-API) mit Claude verbinden
- Amazon Seller Central (SP-API) mit ChatGPT verbinden
- Amazon Seller Central (SP-API) mit Cursor verbinden
- Amazon Seller Central (SP-API) mit Gemini verbinden
- Amazon Seller Central (SP-API) mit Meta Muse verbinden
Amazon Seller Central (SP-API) einrichten
Direkt aus der Connector-Definition: wo du die Credentials findest, welche Rechte sie brauchen und mit welcher API dieser Adapter spricht. Vom Connector-Autor auf Englisch bereitgestellt.
This connector wraps Amazon's Selling Partner API (SP-API) — the official successor of MWS — using Login-with-Amazon (LWA) OAuth2. No AWS keys or SigV4 signing are needed (Amazon removed that requirement).
Setup (one-time, ~15 min + Amazon approval)
- Register as a developer: Seller Central → Apps & Services → Develop Apps (you may first need to complete the developer profile in the Solution Provider Portal; Amazon reviews it manually, allow a few days).
- Create a private app: Develop Apps → Add new app client → type Sellers → select the roles you need (e.g. "Inventory and Order Tracking", "Pricing", "Amazon Fulfillment", "Finance and Accounting", "Selling Partner Insights"). PII roles (buyer names/addresses) are restricted and NOT required for this connector.
- Get LWA credentials: on the app row choose View → copy Client ID (
amzn1.application-oa2-client.…) and Client Secret (amzn1.oa2-cs.v1.…). - Self-authorize: on the app row choose Authorize → Amazon shows the Refresh Token (
Atzr|…). This token is long-lived; the connector exchanges it automatically for 1-hour access tokens (sent in thex-amz-access-tokenheader — handled for you). - Fill the env vars:
SPAPI_CLIENT_ID,SPAPI_CLIENT_SECRET,SPAPI_REFRESH_TOKEN— from steps 3-4.SPAPI_ENDPOINT— your region's API host:- Europe (DE/UK/IT/FR/ES/NL/SE/PL/TR/AE/IN/…):
https://sellingpartnerapi-eu.amazon.com - North America (US/CA/MX/BR):
https://sellingpartnerapi-na.amazon.com - Far East (JP/AU/SG):
https://sellingpartnerapi-fe.amazon.com
- Europe (DE/UK/IT/FR/ES/NL/SE/PL/TR/AE/IN/…):
SPAPI_MARKETPLACE_ID— the marketplace you sell in (callamazon_marketplace_idsfor the full table; e.g. DEA1PA6795UKMFR9, USATVPDKIKX0DER, ITAPJ6JRA9NG5V4).SPAPI_SELLER_ID— your merchant token (Seller Central → Account Info → Merchant Token). Only needed foramazon_get_listings_item; set any placeholder otherwise.
First call: run amazon_marketplace_participations — it needs no parameters and confirms auth + region are correct.
Sandbox
Set SPAPI_ENDPOINT to https://sandbox.sellingpartnerapi-eu.amazon.com (or -na/-fe) to hit the static sandbox: it returns canned responses when requests match predefined parameter patterns (e.g. Orders requires CreatedAfter=TEST_CASE_200). Same LWA credentials work; a draft app's refresh token may be sandbox-only (production returns 403 until the authorization is production-grade).
Marketplace scoping
All tools are pinned to SPAPI_MARKETPLACE_ID. To work across multiple marketplaces of the same region, create one connector per marketplace (cheap) — the underlying seller account and credentials can be identical.
What v1 deliberately does NOT do
- Buyer PII (names, shipping addresses, phone numbers): requires a Restricted Data Token and an Amazon-approved restricted role. Order data returned here is the non-PII view (IDs, status, totals, SKUs, quantities).
- Writes (price updates, listings edits, feeds): planned for a later version once the read workflows are proven.
Pagination & rate limits
List endpoints return a NextToken/pageToken — pass it back to fetch the next page. SP-API rate limits are per-endpoint (typically 0.0055–2 req/s with small bursts); on 429 the connector retries automatically with backoff, but space out heavy report loops.
Reports flow (3 steps)
amazon_create_report(e.g.reportType: "GET_FLAT_FILE_OPEN_LISTINGS_DATA") → returnsreportId.- Poll
amazon_get_reportuntilprocessingStatus=DONE→ givesreportDocumentId. amazon_get_report_document→ returns a pre-signed downloadurl(valid ~5 min; document may be gzip). Fetch that URL yourself to read the content.
Deine KI ist zwei Klicks von Amazon Seller Central (SP-API) entfernt.
Connector installieren, Credentials einfügen, KI fragen. 7 Tage gratis, keine Kreditkarte.