Three routes connect Claude or ChatGPT to Amazon Seller Central in 2026. Amazon’s own Selling Partner plugin puts Seller Assistant inside Claude, in beta for sellers in Amazon’s US stores. Community SP-API servers run on your machine with your own developer credentials. datavessel’s MCP connector is hosted, covers nine European marketplaces from one sign-in, works in ChatGPT as well as Claude, and puts the Amazon account next to your Shopify, Shopware or WooCommerce shop and your ads. Amazon is one more source behind connect Claude to your store. If you sell on amazon.com and only use Claude, start with Amazon’s plugin. If you sell on amazon.de and its neighbours, or run the same products on Amazon and your own shop, read on.
The three routes, as of November 2026
Amazon’s Selling Partner plugin. Announced on 23 September 2026, it brings Seller Assistant, Amazon’s own agent for sellers, into Claude and into Amazon Quick. Amazon says connecting takes about a minute and no code, the plugin reads listings, inventory and sales, and every action it proposes waits for the seller’s approval. It is in beta for sellers in Amazon’s US stores; international availability has been announced as “to follow” without a date. If you qualify, it is the deepest view of Seller Central an assistant can get, because it is Amazon’s view.
Community SP-API servers. Several open-source MCP servers wrap the Selling Partner API: orders, listings, pricing, FBA data, sometimes reimbursements. They run locally, in Claude Desktop, Claude Code or Cursor, and they need your own SP-API developer registration and Login with Amazon credentials. Right for developers and for sellers who want everything under their own keys; the trade is the developer account, the hosting and no approval step unless you build one.
datavessel. A hosted MCP server with Amazon Seller Central as one of nineteen providers. You sign in with the Seller Central account once, the connection covers amazon.de, .fr, .it, .es, .nl, .com.be, .pl, .se and .co.uk, and the eleven Amazon tools appear in Claude, ChatGPT, Cursor and the Gemini CLI next to the shop, GA4, Search Console, Google Ads, Meta Ads and Merchant Center. Ten tools read. The one write, a listing patch, waits for your approval. Orders arrive without buyer names or addresses, because the app holds only Amazon’s non-restricted roles. North America is not connected, and neither is Amazon Ads, which has its own official MCP server.
What the eleven tools answer
- Read the business.
amz_list_marketplacesis the discovery call: which of the nine marketplaces the account is live on.amz_get_ordersandamz_get_order_itemsreturn orders by marketplace, status and fulfilment channel, with line items, prices, tax and promotions, and no buyer data.amz_get_sales_metricsanswers “how much did this SKU sell” by day, week or month.amz_search_catalogfinds the ASIN behind a product name and shows title, brand and sales ranks. - Watch stock and money.
amz_get_fba_inventorygives fulfillable, inbound, reserved and unfulfillable units per SKU.amz_run_reportrequests, waits for and parses the reports Amazon builds asynchronously: restock recommendations, inventory planning (age, excess), customer returns with reasons, all listings with status, estimated FBA fees per SKU, and sales and traffic per ASIN with sessions and conversion.amz_get_fees_estimateprices one ASIN at one price in one marketplace, referral plus FBA fee.amz_get_financial_eventsis what Amazon actually charged and paid per order, refund and service fee, the number to use for margin instead of an estimate. - Keep the listings.
amz_get_listing_issuesshows a SKU’s status (buyable, discoverable) and every issue Amazon reports, with severity and the affected attribute.amz_update_listingis the single write: title, bullet points, description or price, per marketplace and in its language. Amazon validates the patch immediately and applies it in the background; the tool tells you to check the issues again after a few minutes.
Eleven tools is less than Seller Central. There is no shipment creation, no buyer messaging, no labels or invoices, no advertising. The set is built for the questions an operator asks every week: what is running out, what is suppressed, what did Amazon keep, what sold where.
The pairing: the same SKU on Amazon and in your shop
This is the reason to put Amazon behind the same connector as the shop instead of using a standalone server. Three conversations that need both sides:
1. Stock. “Which of my top twenty SKUs on amazon.de have fewer than fourteen days of FBA supply, and how many units of each sit in the shop’s warehouse?” The assistant reads FBA inventory and the restock report from Amazon, stock from Shopify, Shopware or WooCommerce, and returns the list with both numbers. You decide what to send in. The reverse question works too: a product sold out in the shop while FBA still holds 300 units is a reason to point the shop’s ads at the Amazon listing, or to move stock back.
2. Money. “For SKU 4471, what did Amazon actually keep per unit last month, and what does the same unit net in the shop after payment and shipping?” Financial events give the settled Amazon side; the shop’s order data and the costs you state give the other. A fee estimate at a new price answers “what if I raise it on amazon.fr by two euros” before you do it.
3. Listings. “The bestseller is suppressed on amazon.fr. Why, and fix it.” Listing issues return the reason, say a title over the French character limit. The assistant drafts the new title, the patch waits in the approval queue, you tap approve on web or mobile, and the change lands in the ledger with the reason attached. Then it checks the same product in the shop, because the content that failed on Amazon usually drifted from the shop’s too.
Then take it out of chat. Inside datavessel the same tools run on a schedule: a weekly restock read, a suppressed-listing check per marketplace, Amazon orders in the same order queue as the shop’s. The approval step stays. Nothing on Amazon changes unattended.
Connect Amazon Seller Central to Claude: step by step
- Sign in at app.datavessel.io, open Connectors, and under Ads and Shopping choose Amazon. Sign in with Login with Amazon using the account that manages Seller Central. One connection covers all nine European marketplaces; the account’s marketplaces are listed after sign-in. Revoke the app at any time under Apps and Services in Seller Central.
- Add the connector to Claude. In Claude Desktop, Settings, then Connectors, add a custom connector with
https://mcp.datavessel.io/mcpand sign in. In Claude Code, add the same URL as an MCP server. - Ask. “List my Amazon marketplaces, then show the ten SKUs on amazon.de with the fewest fulfillable units and their restock recommendation.” Claude calls
amz_list_marketplaces,amz_get_fba_inventoryandamz_run_report, and answers with a table.
Connect Amazon Seller Central to ChatGPT
Same server, different door. In the ChatGPT desktop app enable developer mode under Settings, then Connectors, add a custom connector with the same URL, sign in, and the Amazon tools appear next to your other connectors. Steps two and three with screenshots are in connect ChatGPT to Shopify; they are identical for Amazon. Amazon’s own plugin does not run in ChatGPT today, so for ChatGPT users this is the hosted route.
Side by side
| Amazon’s Selling Partner plugin | Community SP-API server | datavessel | |
|---|---|---|---|
| Works in | Claude, Amazon Quick | Claude Desktop, Claude Code, Cursor | Claude, ChatGPT, Cursor, Gemini CLI, plus CLI and mobile |
| Marketplaces | Amazon’s US stores (beta) | Whatever your developer account covers | Nine European marketplaces, one connection; no North America |
| Setup | About a minute, no code | SP-API developer registration, credentials, self-hosted | Login with Amazon, hosted |
| Buyer data | Amazon’s own | Depends on the roles you request | None, by design |
| Reads | Listings, inventory, sales, Seller Central insights | Varies by project | Orders, sales, FBA stock, reports, fees, settlements, listing issues, catalog |
| Writes | Seller Assistant’s actions, each approved by the seller | Varies; no approval step built in | One: the listing patch, behind approval |
| Beyond Amazon | No | No | Shop, GA4, Search Console, Google Ads, Meta Ads, Merchant Center |
| Price | Not priced separately, beta | Free, open source | Free for one store; an Amazon connection does not count as a store |
Amazon plugin facts last verified on 1 November 2026 from Amazon’s announcement and Seller Central help pages; datavessel is not affiliated with Amazon.
What it does not do
No North American marketplaces. No Amazon Ads; Amazon publishes an official Ads MCP server for that, and the same account’s Google and Meta ads are already covered. No Vendor Central. No FBA shipment creation, labels, invoices or buyer messages. No automatic repricing: a price change is a listing patch, and it waits for approval like any other write. If one of these is the job, the plugin or a community server is the better fit, and the comparison above is meant to send you there honestly.
Frequently asked questions
Is there an MCP for Amazon Seller Central?
Yes, three kinds. Amazon’s Selling Partner plugin for Claude and Amazon Quick, in beta for US sellers. Community open-source servers over the Selling Partner API, self-hosted with your own developer credentials. And hosted connectors such as datavessel, which covers nine European marketplaces and works in Claude and ChatGPT.
Can I connect Claude to my Amazon Seller Central account?
Yes. In the US, through Amazon’s plugin in Claude’s plugin directory. In Europe, through datavessel: sign in with Login with Amazon, add the connector URL in Claude, and ask.
Can I connect ChatGPT to Amazon Seller Central?
Yes, through a hosted MCP connector added in ChatGPT’s developer mode. Amazon’s own plugin runs in Claude and Amazon Quick, not in ChatGPT, as of November 2026.
Does it work for amazon.de and the other European marketplaces?
Yes. One connection covers Amazon.de, .fr, .it, .es, .nl, .com.be, .pl, .se and .co.uk. Every tool takes a marketplace parameter, so “compare units sold on DE and FR last month” is one question.
Do you see my customers’ names and addresses?
No. The app is approved for Amazon’s non-restricted roles only. Orders and line items arrive without buyer names, addresses or phone numbers.
Can the assistant change my prices or listings?
Only through the listing patch: title, bullets, description and price, per marketplace, and only after you approve it. Everything else is read-only.
Does Amazon allow this?
Yes. datavessel is a registered Selling Partner API application, you authorise it with Login with Amazon, and you can revoke it in Seller Central under Apps and Services at any time. Reads respect Amazon’s rate limits; the one write is Amazon’s own listing API, validated by Amazon on submission.
What does it cost?
Free for one store, and an Amazon connection does not count toward the store limit. You bring your own AI key (Anthropic, OpenAI or Google) and pay the model provider directly.
The bottom line
Amazon has made the first-party route real for US sellers in Claude, and if that is you, use it. For European sellers, for ChatGPT users, and for anyone running the same products on Amazon and their own shop, the useful connector is the one that holds Amazon next to the shop and the ads, reads without buyer data, and asks before it touches a listing.
Amazon, the shop, analytics and ads in one connector, every change behind your approval: the datavessel MCP server →
Leave a Reply