
Mcp Amazon
io.github.codesparPublished by GitHub account codesparv0.2.0-alpha.3Updated Oct 27, 2026
MCP server for Amazon Selling Partner API (SP-API) — orders, listings, catalog, inventory, finances
Overview
Local MCP server for the Amazon Selling Partner API, letting an assistant read and manage orders, listings, catalog, FBA inventory, reports and finances.
- What you can do
- List and inspect orders, order items and shipment status, and confirm or update shipments
- Read, create, replace, patch and delete listings by SKU, and search catalog items by ASIN or keyword
- Check FBA inventory summaries and estimate referral and FBA fees for an ASIN
- Request, list, cancel and check reports, and submit or check feeds
- List financial events overall or per order for reconciliation
- Create and list Notifications API subscriptions and list the marketplaces the seller is registered in
- When to use it
- Useful for Amazon sellers who want an assistant to answer questions about orders, inventory, listings and fees, or to draft listing and shipment changes across NA, EU or FE marketplaces, including Brazil, Mexico and the US.
- Requirements
- Runs locally via npx from the npm package (Node.js). Needs a Login with Amazon app from Seller Central: AMAZON_LWA_CLIENT_ID, AMAZON_LWA_CLIENT_SECRET and a seller-authorized AMAZON_REFRESH_TOKEN, plus AMAZON_MARKETPLACE_ID; AMAZON_REGION and AMAZON_SELLER_ID are optional. Network access to Amazon's LWA token endpoint and the regional SP-API hosts is required.
Installation
In SourceWeft
- Open Mcp Amazon in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@codespar/mcp-amazon
MCP server for the Amazon Selling Partner API (SP-API) — the biggest global marketplace, including Amazon BR, Amazon MX, Amazon US, and all EU/FE marketplaces.
For LatAm sellers, Amazon rounds out the marketplace trio already in this catalog:
- Mercado Libre (
@codespar/mcp-mercadolibre) — dominant in LatAm generally (BR, AR, MX, CO, CL). - Shopee (
@codespar/mcp-shopee) — heavy in Brazil and rapidly growing regionally. - Amazon (this package) — global reach, plus Amazon BR/MX for LatAm sellers and cross-border into Amazon US/EU/JP.
Together these three cover essentially every marketplace where a LatAm merchant transacts meaningful GMV.
Tools (24)
Install
Environment
Marketplace ids (common)
Authentication
SP-API uses a dual-step Login with Amazon (LWA) flow:
- Exchange refresh token → access token (1-hour lifetime). The server POSTs to
https://api.amazon.com/auth/o2/tokenwithgrant_type=refresh_tokenand yourclient_id/client_secret/refresh_token. The result is cached in memory until ~1 minute before expiry. - Call SP-API with the regional base URL and header
x-amz-access-token: <token>plusContent-Type: application/json.
AWS Signature v4 request signing was the historical requirement for SP-API. Amazon removed the SigV4 requirement in 2023 for most tenants, so this server uses LWA-only auth. If your seller is still flagged as requiring SigV4, you will need to wrap amazonRequest with a signer (@aws-sdk/signature-v4) — not included here.
Regional base URLs
- NA (Americas, including BR/US/MX/CA):
https://sellingpartnerapi-na.amazon.com - EU (Europe + India + MENA):
https://sellingpartnerapi-eu.amazon.com - FE (Far East — Japan, Australia, Singapore):
https://sellingpartnerapi-fe.amazon.com
Select with AMAZON_REGION. Brazil and the Americas use na.
Run
Notifications
create_subscription is webhook-equivalent for SP-API. Amazon does not push HTTP webhooks directly — instead, you create a destination (SQS queue or EventBridge bus) via POST /notifications/v1/destinations first, then attach subscriptions to that destination. This package covers subscription creation; destination provisioning is a one-time setup typically done via the AWS Console or a deploy script.
Status
0.1.0-alpha.1 — SP-API has 30+ product sections and this package covers the commerce-relevant subset (orders, listings, catalog, inventory, reports, finances, shipping, notifications). Endpoint paths and auth flow are implemented to the published spec; tool contracts should be integration-tested against real seller tokens before production use. The LWA refresh flow and x-amz-access-token header usage are confirmed against current SP-API docs.
Enterprise
Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.
License
MIT
Source: packages/ecommerce/amazon/README.md at commit d0a519a
Tools
0Version history
1- v0.2.0-alpha.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts