If you sell in Amazon’s US stores and work in Claude or Amazon Quick, start with Amazon’s Selling Partner plugin, in beta since 23 September 2026. A custom Amazon seller MCP server on the SP-API still fits if you sell outside the US, sell through Vendor Central, use other AI tools, or need Odoo data in the same answer.
This is correct as of 7 November 2026. The plugin is in beta and will change, so we link Amazon’s own sources throughout.
What Amazon launched, in plain terms
There are now two official Amazon MCP options, and they do different jobs. One is for running a seller account. The other is for advertising.
The Amazon Selling Partner plugin for Claude and Quick
Amazon announced the plugin on 23 September 2026, as part of its Seller Assistant update. It launched in Amazon Quick, Amazon’s AI assistant for work, and in beta in Anthropic’s Claude, with “more integrations to follow”.
The plugin brings Seller Assistant into those tools. Amazon says it connects a seller’s listing contributions, real-time performance metrics, inventory levels and sales analytics. It can also act on the account, not just read it. Amazon names three safeguards: clear limits on what the plugin can access, human approval on actions, and complete audit trails.
Two more details matter. It is available “in beta for sellers in Amazon’s U.S. stores, with international expansion to follow”. And Amazon says connecting it to Claude takes roughly 60 seconds, with no coding. Separately, every primary account holder can sign up for a free 12-month Amazon Quick Plus subscription until 31 December 2026, and add two co-workers.
The toolkit behind it: connector, skills and commands
Amazon publishes the Selling Partner agentic toolkit on GitHub. It registers the Amazon Selling Partner Connector, an MCP server at sellingpartner-ai.amazon.com/mcp. You sign in through the normal Seller Central consent flow, and the assistant can only use the tools your Seller Central roles allow. Write actions are drafted for your approval. They never run on their own.
On top of the connector sit skills for seller analytics, stockout prevention, FBA inbound shipments, listing problems, Seller Support cases and SP-API questions. There are also three ready-made commands: /sp-stockout-check, /sp-fix-listing and /sp-sales-drop.
The Amazon Ads MCP Server is a different product
On 2 February 2026 Amazon Ads put its Amazon Ads MCP Server into open beta. It connects AI agents to the Amazon Ads API: creating, updating or deleting campaigns, running performance reports, managing account settings, and reading billing data. It works with Claude, ChatGPT, Gemini or your own agents, and it is available globally to Amazon Ads partners with active API credentials.
So if your question is about campaigns and spend, that is the Ads server’s job. If it is about orders, stock and listings, it is the Selling Partner plugin’s job.
When Amazon’s plugin is the right choice
For a lot of sellers, the honest answer is to use Amazon’s plugin and stop there. It fits well when all of these are true:
- You sell in Amazon’s US stores through Seller Central.
- You already work in Claude or Amazon Quick.
- Your questions are about Amazon itself: sales, stock, listings, inbound shipments, account issues.
Amazon builds and maintains it. Permissions follow the Seller Central roles you already manage. Approvals and audit trails are built in. And the skills come from the company that runs the marketplace. A custom server has to earn its place against that.
It also does not have to be your only connector. Amazon notes that many sellers already connect accounting and supplier data to Claude, and the plugin sits alongside those connections. A US seller on Odoo could add the plugin next to an Odoo connector and ask about both.
Where a custom Amazon seller MCP still fits
A custom server is built on Amazon’s Selling Partner API (SP-API) and scoped to one business. It earns its keep in the gaps the plugin does not cover yet.
Amazon seller MCP for marketplaces outside the US
If you sell on Amazon.ae, Amazon.sa, Amazon.in, Amazon.co.uk or the EU stores, the plugin is not open to you today. Amazon has said international expansion will follow, but it has not given a date. The SP-API already serves those marketplaces. Our own Amazon Connector for Odoo runs on it for marketplaces including the UAE, Saudi Arabia, India and the UK. If you can wait and only need Amazon’s own data, waiting is a reasonable choice. If you need it now, a custom server is the route.
Vendor Central brands
Amazon’s announcement and toolkit talk about sellers and Seller Central. Vendor Central, where a brand sells wholesale to Amazon as a first-party vendor, is not mentioned. The SP-API does have vendor APIs for purchase orders, shipment notices and invoices. So a custom server can let an assistant answer “which Amazon POs ship this week, and which are short?”. That is the same document flow our Amazon Vendor Central Odoo Connector handles inside Odoo.
AI tools other than Claude and Quick
Today the plugin works in two places, and Amazon says it will add more AI tools over time. MCP is an open standard, so a custom server can connect to any assistant that supports it, including ChatGPT or an agent your own team builds.
Several accounts in one place
If you run many seller accounts, as an agency does, check how the plugin handles switching between them. With a custom build, each account gets its own scoped server, so data never mixes.
Your ERP data in the same answer
Amazon’s plugin knows Amazon. It does not know what is in your ERP: stock in your own warehouse, open purchase orders with suppliers, landed cost per unit, or how your accounts record each settlement.
Many useful questions need both sides. “Am I making money on this SKU after landed cost and Amazon fees?” “Can my warehouse cover the next FBA restock, or do I need to reorder from the supplier?” Amazon has the fees and the sales. Odoo has the cost and the stock.
There are two ways to get there. If you are a US seller in Claude, use Amazon’s plugin plus a separate Odoo connector. Or build one custom server that joins both sources and applies your own rules, such as how you spread freight and duty into landed cost.
Not sure which side of the line you are on?
Tell us your marketplaces, whether you use Seller Central or Vendor Central, and which AI tool your team works in. We will tell you plainly whether Amazon’s plugin covers it or a custom server is worth building.
Talk About an Amazon MCP ServerAmazon Selling Partner plugin vs custom Amazon MCP at a glance
| Amazon Selling Partner plugin | Custom Amazon MCP server | |
|---|---|---|
| Built and maintained by | Amazon | You, with a developer of your choice |
| Marketplaces | Amazon’s US stores (beta); international “to follow” | Any marketplace the SP-API serves, such as the US, UAE, Saudi Arabia, India, UK and EU |
| Seller Central | Yes | Yes |
| Vendor Central | Not mentioned by Amazon | Yes, through the SP-API vendor APIs |
| Advertising | No; that is the Amazon Ads MCP Server | Possible if you have Ads API access |
| AI tools | Amazon Quick and Claude (beta); more over time | Any MCP client, such as Claude, ChatGPT or your own agent |
| ERP and Odoo data | Not in the plugin; add a separate connector alongside it | Can be joined in the same server, with your rules |
| Ready-made skills | Yes: stockouts, listing fixes, FBA inbound, sales drops | No; you define the tools you need |
| Safeguards | Seller Central roles, approval on actions, audit trails | Scoped SP-API access, approval-gated writes, tool-call logs |
| Setup | About 60 seconds in Claude, no coding (Amazon’s figure) | A scoped project, quoted after discovery |
| Where it runs | Amazon’s service | Your cloud or your own servers |
Plugin details are from Amazon’s announcement and its GitHub toolkit, checked on 7 November 2026.
Which one do you need?
Work through these in order and stop at the first one that fits.
- Only advertising? Look at the Amazon Ads MCP Server. You need Amazon Ads API credentials.
- US stores, Seller Central, Claude or Quick, Amazon data only? Use Amazon’s Selling Partner plugin.
- A US seller who also wants Odoo data? Try the plugin next to an Odoo connector first. Build custom only if you need one place that applies your own rules across both.
- Selling outside the US? If Amazon data is all you need and timing is not urgent, wait for Amazon’s expansion. Otherwise, build a custom server on the SP-API.
- Vendor Central, another AI tool, many accounts, or a need to host it yourself? A custom server.
Third-party Amazon MCP tools also exist as subscriptions. For standard reporting on a simple account, they are worth a look before you commission anything.
What a careful custom build involves
If a custom server is the right fit, it should be built in small, safe steps:
- Scope first. Agree your marketplaces and exactly which SP-API roles and data the server may touch.
- Approval on writes. Reads can be broad. Any price or listing change waits for a person to approve it.
- Built for Amazon’s limits. SP-API rate limits and report queues are normal, not edge cases.
- Logged. Every tool call is recorded and reviewable.
- Read-only pilot. Your team asks real questions against live data before any write access is switched on.
Our guide to connecting Claude to Amazon Seller Central goes deeper into that setup. We made the same comparison for a CRM in HubSpot’s official MCP vs a custom server, and the pattern holds: use the official one where it fits, and build only where it does not.
Where we stand
Inwizards builds custom MCP servers as a service, including custom Amazon seller MCP servers on the SP-API. We do not sell a hosted Amazon MCP product, and we are not affiliated with Amazon. So we have an interest in this question. Weigh what we say with that in mind.
What we can point to is the SP-API work we already ship: our Seller Central and Vendor Central connectors for Odoo. We have been building software since 2009, with teams in the US, the UAE and India. See the other systems we connect on our MCP servers page.
If you are a US seller in Claude, try Amazon’s plugin this week. By Amazon’s estimate, setup takes about a minute. Then write down the questions it could not answer. If that list is about other marketplaces, Vendor Central or your Odoo numbers, that list is the scope of a custom build.