Amazon has published a plugin under its own GitHub organization, amzn/selling-partner-agentic-toolkit. It connects an AI assistant to a seller account through a remote MCP server that Amazon runs, and ships twelve Skills on top of it.
That changes one practical thing. Reading your own seller data from an assistant no longer requires building an SP-API integration yourself. It does not change what the Selling Partner API is for. This post goes through both halves.
Everything below comes from reading the repository at commit 8d90d3b on 2026-10-12. We have not connected a seller account to it.
What the connector is
The plugin's .mcp.json registers one server: https://sellingpartner-ai.amazon.com/mcp. You authorize it through the normal Seller Central OAuth consent screen, and the assistant can only use the tools your Seller Central roles allow.
The plugin manifest calls the product a beta. The Skill metadata names Claude Desktop, Claude Code and AWS Quick as platforms, and two of the twelve Skills leave Claude Code off their list.
What the twelve Skills do
| Area | Skills | What you get |
|---|---|---|
| Performance | seller-analytics | Inventory, traffic and sales metrics for your account |
| Inventory | stockout-prevention, fba-inbound-management | Days of cover per SKU, the gap before the next shipment, an inbound plan walked through step by step |
| Listings | listing-troubleshooter, listing-issues, listing-buyability, listing-searchability, listing-compliance | Why a listing is suppressed, not buyable or not found, with fixes drafted for approval |
| Finance | finance-month-end-closer | A reconciliation of a completed month against its settlements |
| Account | support-case-helper, invite-secondary-users | A case summary with personal data removed, and a walkthrough for granting access |
| Developers | sp-api-knowledge | Answers to SP-API integration questions |
Three slash commands sit on top: /sp-stockout-check, /sp-fix-listing and /sp-sales-drop.
How writes are gated
Every write is drafted for your approval. The stockout Skill, for example, has one write tool, a listings patch, and the source requires it to run in a validation preview mode until you type an approval.
Two design choices stand out:
- No pricing advice. The stockout Skill is told not to suggest raising or lowering a price, and not to comment on a price you name. Its source gives the reason: pricing advice coming from Amazon carries implications the Skill must not create.
- Finance is read-only. The month-end Skill posts no entries and moves no money. It also has no bank integration, so it asks you to paste deposit amounts, and it says outright that a payout Amazon marks as paid does not prove the money reached your bank.
These limits are deliberate. They are also a reminder that once you approve a preview, the change is live.
What it does not cover
The connector sees one account: yours. It has no view of other sellers. That boundary is the same one the Selling Partner API has always had, and an MCP layer does not move it.
| Question | Official connector | Market data API |
|---|---|---|
| Which of my SKUs will run out first? | Yes | No |
| Why is my listing suppressed? | Yes | No |
| Do last month's settlements reconcile? | Yes | No |
| What is a competitor's price and coupon history? | No | Yes |
| How large is this category and how concentrated is it? | No | Yes |
| What is the search volume for a keyword I do not rank for? | No | Yes |
| Which keywords send traffic to a competing ASIN? | No | Yes |
The right-hand column is estimates built from public marketplace data. The left-hand column is your own exact records. Neither can stand in for the other. The four kinds of Amazon API covers that split in more detail.
Using both in one client
MCP clients can hold several servers at once, so the two can sit side by side.
The stockout Skill shows where they meet. After it lists your options, it offers to look at demand, seasonality and competing offers before you decide. Its own velocity figure is a trailing 30-day average, which cannot show a seasonal ramp that has not started yet. A category demand trend from a market data source can.
A workable sequence:
- Ask the official connector for days of cover on your SKUs
- For a SKU in the warning band, ask the market data server for the category's demand trend and the sales trend of two or three competing ASINs
- Decide on the reorder yourself, with both in front of you
Keep the sources labelled in the conversation. A model that mixes your order counts with a market estimate will produce a number that is neither.
Remote MCP setupConnect the market data side to the same client over browser OAuthOur connection steps are in Remote MCP without pasting a key. Entries for the official plugin and its stockout Skill, with pinned sources, are in the directory: Amazon Selling Partner Agentic Toolkit and Amazon Stockout Prevention.
What we have not verified
- Availability. We did not install the plugin or complete the OAuth flow, so we cannot say which regions or account types can use it today.
- Nine of the twelve Skills. We read three in full (
listing-troubleshooter,stockout-prevention,finance-month-end-closer). The rest are described from the README and their metadata. - One inconsistency. The README and the
/sp-stockout-checkcommand say the stockout Skill recommends how much to reorder. The Skill file we read computes days of cover and defines no reorder-quantity formula.
A beta repository changes quickly. Check the current commit before relying on any detail here.
Questions
Does this replace an SP-API integration? For asking questions in an assistant, it removes the need to build one. For scheduled jobs and anything that feeds your own systems, a direct integration is still the consistent route.
Can it look up a competitor's ASIN? Not their private data. Nothing in the files we read gives access to another seller's sales, inventory or advertising.
Is my data sent anywhere besides Amazon? The README says the Skills send tool calls only to Amazon's endpoint. Your prompt text is still processed by whichever assistant you use, under that assistant's terms.
Does it cost anything? The repository states no price and is licensed Apache-2.0. Your assistant's own plan still applies.