--- title: Amazon Seller Central MCP Server for Claude | SourceMedium description: Amazon's Selling Partner MCP connector, rolling out to US sellers, reads sales, inventory, and listings in Claude or Quick and drafts changes. url: "https://sourcemedium.com/mcp-directory/amazon-seller-central/" type: static generatedAt: "2026-09-29T01:21:01.000Z" --- [MCP Directory](https://sourcemedium.com/mcp-directory/) Storefronts and marketplaces Official SourceMedium integration # Amazon Seller Central MCP server Remote endpoint sellingpartner-ai.amazon.com/mcp. Checked September 2026. Amazon's Selling Partner connector, in beta and rolling out to US sellers, reads a Seller Central account's sales, traffic, and inventory metrics, listing status, Featured Offer pricing, fee estimates, and FBA prep requirements. Any price, listing, or FBA inbound change it drafts runs only after the seller approves it. ## Amazon Seller Central MCP options Every fact in a row comes from the publisher's own documentation. | Option | Audience | Reads or changes | Sign-in | Setup | | --- | --- | --- | --- | --- | | Amazon Selling Partner connector `https://sellingpartner-ai.amazon.com/mcp` Amazon | Merchants | Reads sales, traffic, and inventory metrics, listing status, Featured Offer pricing, fee estimates, and FBA prep requirements for a Seller Central account, and drafts price, listing, and FBA inbound changes that run only after the seller approves them; access is rolling out to sellers over time. Can write | OAuth sign-in | [Setup guide →](https://sellercentral.amazon.com/help/hub/reference/external/GAFFEKSK9UR4MGTF) | | SP-API Developer MCP server, sample Amazon | Developers | Runs locally to search SP-API docs, browse the endpoint catalog, and generate and review integration code with no credentials; executing live SP-API requests, including POST, PUT, and DELETE, uses the developer's own SP-API credentials. Can write Developer sample | API key or token | [Setup guide →](https://github.com/amzn/selling-partner-api-samples/tree/main/use-cases/sp-api-dev-mcp) | | Amazon Seller Central data through SourceMedium's MCP `https://mcp.sourcemedium.com/mcp` SourceMedium Ours | Merchants | Reads Amazon Seller Central data from modeled SourceMedium tables, next to your other connected sources, with canonical metric definitions. Read only | OAuth sign-in | [Setup guide →](https://sourcemedium.com/docs/ai-analyst/connect-an-ai-assistant) | ## Connect Amazon Seller Central to your assistant Each card lists the servers whose setup guide covers that assistant. ### Connect Amazon Seller Central to Claude - [Amazon Selling Partner connector →](https://sellercentral.amazon.com/help/hub/reference/external/GAFFEKSK9UR4MGTF) [Add from Claude's connector directory](https://claude.com/marketplace/connectors/amazon-selling-partner) - [SP-API Developer MCP server, sample →](https://github.com/amzn/selling-partner-api-samples/tree/main/use-cases/sp-api-dev-mcp) Guide covers Claude Desktop ### Connect Amazon Seller Central to Cursor or VS Code - [SP-API Developer MCP server, sample →](https://github.com/amzn/selling-partner-api-samples/tree/main/use-cases/sp-api-dev-mcp) Amazon Seller Central's setup guides also name Amazon Quick and Kiro. ## Other ways to reach Amazon Seller Central data - [Amazon's announcement of the Selling Partner plugin (September 23, 2026) →](https://www.aboutamazon.com/news/innovation-at-amazon/seller-assistant-plugin-amazon-quick-claude) - [Selling Partner agentic toolkit (tool reference) →](https://github.com/amzn/selling-partner-agentic-toolkit) - [SP-API seller use cases (Selling Partner API docs) →](https://developer-docs.amazon/sp-api/docs/sp-api-seller-use-cases) - [Data Kiosk API for sales and traffic data →](https://developer-docs.amazon/sp-api/docs/data-kiosk-api) - [Seller Assistant, Amazon's AI assistant in Seller Central →](https://www.aboutamazon.com/news/innovation-at-amazon/seller-assistant-agentic-ai) ## What “Amazon MCP” can mean The answer depends on which side of Amazon you work on. - **A seller** on Amazon’s US stores uses Amazon’s Selling Partner connector, in beta. - **An advertiser or agency** with Amazon Ads API access uses the Amazon Ads MCP server, in open beta. - **A developer** can run Amazon’s sample MCP servers for the Selling Partner API on their own credentials. - **A vendor** selling wholesale through Vendor Central has no official server. - **A team on AWS** will find AWS’s MCP servers, which cover cloud infrastructure rather than Amazon retail or advertising data. ## Amazon Selling Partner connector [Amazon announced it](https://www.aboutamazon.com/news/innovation-at-amazon/seller-assistant-plugin-amazon-quick-claude) on September 23, 2026, for sellers in its US stores: in Amazon Quick, and in beta with Claude. Access is rolling out to sellers over time, so it may not appear in your account yet. You authorize it through Seller Central’s OAuth consent screen, it can use only the tools your Seller Central roles allow, and a secondary user needs an admin to grant access under Manage Agents. Amazon’s materials describe Seller Central accounts only. Setup: [Amazon’s help page for the plugin](https://sellercentral.amazon.com/help/hub/reference/external/GAFFEKSK9UR4MGTF) walks through connecting Amazon Quick or Claude. The [Selling Partner toolkit](https://github.com/amzn/selling-partner-agentic-toolkit) documents its tools. ## Amazon Ads MCP server The server has been in open beta since February 2, 2026, and Amazon describes it as available “to Amazon Ads partners with active API credentials”. Connecting takes an approved Amazon Ads API application and a Login with Amazon client ID, then an OAuth 2.1 sign-in. It runs reports and reads account and billing data, and it can create, update, and delete campaigns and ads, so switch off any delete tools you do not want an assistant to hold. See the [Amazon Ads MCP server](https://sourcemedium.com/mcp-directory/amazon-ads/) entry for its row. Setup: [OAuth for the Amazon Ads MCP server](https://advertising.amazon.com/API/docs/en-us/mcp/oauth). ## Developer samples for the Selling Partner API Amazon’s samples repository includes an SP-API developer MCP server that searches the API documentation, generates integration code, and runs live SP-API requests, including POST, PUT, and DELETE. Its documentation and code tools need no credentials; live requests use your own developer credentials. Amazon describes its samples as “not supported products in their own right, but educational examples”. Setup: [SP-API developer MCP sample](https://github.com/amzn/selling-partner-api-samples/tree/main/use-cases/sp-api-dev-mcp). ## Vendor Central No official MCP server covers Vendor Central, and none of Amazon’s sources for the Selling Partner connector mention vendors. Vendors reach purchase orders and retail analytics through the Selling Partner API’s vendor endpoints. Amazon also publishes a Data Kiosk MCP sample for vendor analytics, which runs on developer credentials. ## AWS MCP servers AWS publishes a [suite of MCP servers](https://github.com/awslabs/mcp) for its cloud: documentation, infrastructure and deployment, databases, and cost. None of them reads Seller Central or Amazon Ads data. ## A first safe read Once the Selling Partner connector reaches your account, ask: “Summarize last week’s sales and units for my ten best-selling products, compared with the week before, and name the marketplace and dates you used.” A good answer names the US marketplace and both date ranges, gives sales and units per product, and says whether the latest days may still change. Approve nothing it drafts until those numbers match Seller Central. ## When one source is enough, and when it is not Operational questions that stay inside Seller Central, such as a listing’s status, stock on hand, or last week’s units, fit Amazon’s own connector. Questions that cross sources do not: Amazon revenue beside Shopify on one net revenue definition, marketplace sales against Amazon Ads spend, or Subscribe & Save orders next to a subscription platform’s. Amazon figures also keep changing after the order date as refunds and returns post. Through SourceMedium’s MCP, an assistant reads Amazon from settled windows, with the Subscribe & Save and FBA return boundaries already applied, next to Shopify and the rest of your store data. [Amazon Seller Central on SourceMedium](https://sourcemedium.com/integrations/amazon-seller-central/) lists those windows and boundaries. ## One MCP server per tool still can't answer a cross-channel question. Each server brings its own sign-in, its own definition of revenue, and data your assistant can't join to the rest. SourceMedium joins Amazon Seller Central with the rest of your store, ad, subscription, and returns data, keeps one set of maintained definitions, and gives ChatGPT, Claude, and other assistants a single connection to all of it. ## More in Storefronts and marketplaces - [BigCommerce MCP server →](https://sourcemedium.com/mcp-directory/bigcommerce/) - [commercetools MCP server →](https://sourcemedium.com/mcp-directory/commercetools/) - [eBay MCP server →](https://sourcemedium.com/mcp-directory/ebay/)