Amazon’s official Claude plugin, in beta since 23 September 2026, covers Seller Central only. To connect Amazon Vendor Central to Claude, you need a custom MCP server built on the vendor endpoints of the Selling Partner API: purchase orders, shipments, invoices, remittances and Direct Fulfillment. Start read-only, then add writes that a person approves.
This guide is for brands that sell to Amazon as a first-party (1P) vendor. If you sell through Seller Central, read how to connect Claude to Amazon Seller Central instead.
Amazon’s own plugin stops at Seller Central
On 23 September 2026 Amazon announced the Amazon Selling Partner plugin. It launched in Amazon Quick and in beta in Claude, for sellers in Amazon’s US stores. It brings listings, performance metrics, inventory and sales analytics into the assistant, with human approval on actions and an audit trail.
It is built on Seller Central. Neither the announcement nor Amazon’s public toolkit mentions Vendor Central. A vendor’s day is about purchase orders, acknowledgment windows, shipment notices, invoices, remittances and chargebacks. None of that is in the plugin today.
So a vendor who wants to ask Claude “which POs still need an answer today?” needs an MCP server of its own, built on the vendor side of the Selling Partner API (SP-API). MCP, the Model Context Protocol, is the open standard Claude uses to reach outside systems. Third-party tools exist too. This guide explains what a good server looks like, whoever builds it.
What the SP-API gives a vendor to work with
Amazon marks a set of APIs “Vendors only” in its SP-API documentation. An MCP server wraps a few of them as named tools that Claude can call.
Purchase orders and acknowledgments
The Vendor Orders API returns purchase orders with line items, quantities and cost. It carries the ship window for Amazon-paid freight or the delivery window for vendor-paid freight. It also returns PO status and accepts acknowledgments, line by line: accepted, backordered or rejected. One limit: Amazon says changing an order after it is placed is a manual process in Vendor Central, not something the API does.
Shipments and ASNs
The Vendor Shipments API takes shipment confirmations, which are your advance shipment notices (ASNs). It also returns shipment status and pickup details, in North America and Europe.
Invoices, payments and remittances
The Vendor Invoices API submits invoices and credit notes. A separate Invoices API, added for vendors in 2026, reads invoices back with their payment status. The Finance Remittance API, also new, returns what Amazon paid or deducted and which invoices each payment covers. Amazon says it is the same data as the Payments > Remittance view in Vendor Central. The Vendor Transaction Status API tells you whether a document you submitted was accepted or failed.
Direct Fulfillment
Drop-ship vendors get their own Direct Fulfillment APIs: orders and acknowledgments, shipping labels, shipment confirmations, inventory updates, invoices and transaction status.
What is not in the API
We did not find an SP-API operation that lists chargebacks with their defect detail, or one that lets you dispute a chargeback. Deductions show up in remittance data. The defect detail and the dispute itself still live in Vendor Central.
The tools a Vendor Central MCP server should expose
A good server does not hand Claude the whole API. It exposes a short list of tools named after the questions your team actually asks.
Read-only tools for the first weeks
- Open purchase orders: new and unacknowledged POs, with ship-to, windows, lines and cost.
- Acknowledgment deadlines: which POs need an answer, and by when. Your vendor terms set the deadline, so the server works it out from a rule you give it, not from a field Amazon sends.
- ASN status: shipments confirmed, shipments still missing a notice, and what Amazon returned for each one.
- Invoice status: submitted, accepted, rejected or paid.
- Remittances and deductions: what each payment covered and what was held back.
- Direct Fulfillment orders: open drop-ship orders and where each one stands.
Run read-only for a few weeks. Nothing on the Amazon side can change by mistake.
Approval-gated writes
Writes come later, one at a time. Good first candidates are acknowledging a PO, submitting an ASN and submitting an invoice. The pattern is the same for each. Claude drafts the document. A named person sees exactly what will be sent and approves it. The server submits it, checks the transaction status and records the result. Claude never sends anything to Amazon on its own.
Want Claude to answer from your Vendor Central account?
Tell us your vendor codes, your regions and whether you run Direct Fulfillment. We will map the SP-API access and the first read-only tools before any build work starts.
Scope a Custom Amazon MCP ServerCredentials, roles and the restricted data token
A private vendor application
A vendor building for itself registers a private SP-API application. Amazon describes private vendor applications as available only to your own organization and self-authorized, whether your own IT team or an agency builds it. Registration starts in Vendor Central under Integration, then API Integration, where you complete a developer profile that Amazon reviews. The credentials stay on the server. Claude never sees them.
Roles decide what the server can reach
Every SP-API operation needs a role. Vendor orders, shipments and invoice submission use roles such as Amazon Fulfillment or Inventory and Order Tracking. Reading remittances and invoices needs Finance and Accounting. Ask only for the roles your tools need.
Restricted data for Direct Fulfillment
Direct Fulfillment orders sit behind a restricted role, Direct to Consumer Shipping (Restricted), because some can include a consumer’s name and address. Amazon asks for extra detail on data use and security before it grants that role. Restricted operations use a Restricted Data Token (RDT) instead of the normal access token. A sensible server keeps that data out of the chat.
Audit logs
Log every tool call: who asked, what Claude requested, what the server sent to Amazon and what came back. When someone asks why an ASN went out late, the answer should be in a log.
Claude Code or Claude on the web and desktop
MCP works in both, and one server can serve both. In Claude on the web and in the desktop app, a remote MCP server is added as a custom connector in Claude’s settings. On Team and Enterprise plans an owner adds it for the organization, and each person then connects. In Claude Code, the terminal tool, you add a remote server with claude mcp add --transport http, followed by a name and the server’s URL.
Operations and finance staff usually work in the app. Claude Code suits developers who want to script checks, such as a morning list of open POs. Because MCP is an open standard, the same server works with other MCP-compatible assistants too. Our MCP servers page covers the wider picture.
Why Vendor Central is only half the answer
An assistant that sees only Amazon can tell you what Amazon thinks happened. What actually happened lives in your ERP.
The order, the shipment and the invoice live in your ERP
Amazon holds the PO. Your ERP holds the stock you could confirm against, the pick that became the pallet, the carrier reference and the invoice. A question like “can we accept this PO in full?” needs both sides. So does “why was this payment short?”
A chargeback can only be disputed next to the evidence
To contest a chargeback you need proof: when the ASN went, what was in each carton, which carrier reference was used. That proof sits in your delivery orders and logs, not in Vendor Central. Our Vendor Central chargebacks reference sets out what triggers each type and the ERP data that prevents it.
Where Odoo fits
If you run Odoo, our Amazon Vendor Central Odoo connector already moves the documents. Purchase orders come in. Acknowledgments, ASNs and invoices go out. Remittances and chargebacks are recorded in Odoo Accounting, and Direct Fulfillment is covered too. With that in place, an MCP server can read Amazon and Odoo side by side, and Claude can answer across both. If you are still deciding how the documents should travel, EDI vs API for Vendor Central covers that choice first.
Where we stand
We are a software company, building since 2009, with teams in the US, the UAE and India. We build the Vendor Central connector for Odoo. We also build custom MCP servers for clients as a service, including on the SP-API. We do not sell a ready-made Vendor Central MCP product, and we are not an Amazon partner. If Amazon extends its plugin to Vendor Central, use it for what it covers.
Where to start
Write down the five questions your team asks about Amazon every morning. Check which SP-API roles your developer profile holds today. Then pick two or three read-only tools that answer those questions, and run them for a few weeks before you allow any write.