How to Connect Amazon Seller Central to Claude

Claude connects to Amazon Seller Central through the Kuudo Amazon Selling Partner MCP server, which turns Selling Partner API operations into tools Claude can call. Add the server's signed connector URL as a custom connector in Claude, switch it on in a chat, and tell Claude which marketplace to work in. Claude then answers from your live listings, inventory and orders.

Every write stays inside the Selling Partner authorization you grant and your workspace policy, and listing changes wait for your approval. The steps cover Claude on the web and Claude Desktop; for Claude Code, use the Claude Code quick start.

Your MCP server hostname is private to your deployment. Replace {your-private-mcp-host} with the private host shown in your dashboard.

What can Claude do in Seller Central?

The Selling Partner API (SP-API) is how Amazon exposes Seller Central to software, one API per area of the business. Through it, Claude can work on:

Listings and catalog: listing content, attributes, catalog data, restrictions and listing issues.
Inventory and fulfillment: FBA (Fulfillment by Amazon) inventory, inbound shipments and fulfillment orders.
Orders and buyers: orders, shipping status and messages to buyers.
Pricing: your offers and competitive pricing data.
Reports and finances: Seller Central reports, settlements and reimbursements.

The Amazon SP-API tools reference lists every tool, and the Amazon Selling Partner MCP page covers the server.

What you need before connecting Seller Central to Claude

A Kuudo workspace with the Amazon Selling Partner MCP server deployed, and access to its dashboard.
Your seller account authorized in Kuudo. On Kuudo Pro and Kuudo Scale, the account owner consents once to Kuudo's managed Selling Partner API app with Login with Amazon, so there is no app of your own to register; an agency can send its client an authorization invitation instead. On Kuudo Community you connect your own Amazon app. See Amazon account authorization.
Claude on the web or Claude Desktop. Custom connectors work on every Claude plan, but Free allows only one. Running Seller Central beside Amazon Ads or Vendor Central needs Pro, Max, Team or Enterprise.
On Team and Enterprise, an Owner adds the connector first under Organization settings > Connectors, and members then connect to it.

Connect Seller Central to Claude

1. Copy the Selling Partner connector URL

In your Kuudo dashboard, open the Keys tab, create a key if needed, and copy the Claude connector URL for the Amazon Selling Partner MCP server. It is signed for Claude, so your API key never goes into Claude:

https://{your-private-mcp-host}/mcp/connect/{signed-token}

2. Add it as a custom connector

In Claude, open Customize > Connectors.
Click +, then Add custom connector.
Name it amazon-seller-central, so it stays distinct from an Amazon Ads connector and from Amazon's own connector.
Paste the signed URL and click Add.

Claude's form cannot attach an Authorization header, so it needs the signed URL rather than the plain /mcp endpoint.

3. Switch it on in a chat

Start a new chat, open Connectors from the composer and switch amazon-seller-central on. When Claude asks to use a tool, read the request; keep tools that change listings, prices or shipments on ask rather than Allow always.

4. Check the connection with a read-only question

Ask a question that reads your Seller Central data without changing anything:

Which marketplaces is our seller account active in? Don't change anything.

Claude should list the marketplaces your seller account participates in. An access error here usually means the seller account is not authorized yet.

Pick the Seller Central marketplace Claude works in

Amazon serves the Selling Partner API from three regional endpoints: North America, Europe and the Far East, which covers Asia-Pacific. Each marketplace belongs to one of them. Name the marketplace and Claude's calls go to the right regional endpoint:

Work in the Germany marketplace for this chat.

Every marketplace your seller account reaches is available. An agency sees each authorized client account through the same connector, so name the client as well as the marketplace.

First Seller Central tasks to try in Claude

A listing audit: "Audit the listing for SKU ABC-123 and propose fixes." The listing optimizer Skill previews each change, waits for your explicit approval in your next message, and never submits on its own.
Sales and traffic: "How did sessions, conversion and sales move by ASIN over the last 30 days?" See Analyze Amazon Sales and Traffic.
Returns: "Which ASINs have rising return rates, and for what reasons?" See Monitor Amazon Refunds and Returns.
Stockouts: "Which FBA SKUs run out before their inbound shipments arrive?" See Amazon Stockout Prevention and Restock Timing.

Troubleshooting Seller Central in Claude

Claude cannot see the seller account

The connector works, but the seller account is not authorized for your workspace yet. Authorize it in Kuudo, or send its owner an invitation, then ask again.

One area returns an access error while others work

Amazon gates each Selling Partner API area by role. An error in one area, such as finances or buyer messaging, while listings and orders work, means the authorization does not include the role Amazon requires for that area.

A listing change does not show yet

Amazon processes listing submissions before they go live. Ask Claude to check the listing's status and issues again after a while.

The custom connector will not add, or returns 401

Use the signed Claude connector URL from the Keys tab, not the plain /mcp endpoint. For a 401, create a fresh key, copy a new signed URL and replace the connector.

Frequently asked questions

Can Claude change my listings or prices?

Yes, within the Selling Partner authorization you grant and your workspace policy. With the listing Skill, Claude previews a listing change field by field, waits for your explicit approval in the next chat message, and never submits on its own, even for an obvious fix.

Is this the same as Amazon's Selling Partner connector for Claude?

No. Amazon lists its own Amazon Selling Partner connector in Claude's connector directory, made by Amazon and in beta. Kuudo's Amazon Selling Partner MCP is a separate server that runs in your own cloud, beside Kuudo's Amazon Ads and Vendor Central servers. For what each one covers, see Amazon's Seller Assistant plugin vs Kuudo and Amazon Seller Central Claude Plugin: What It Does.

Which marketplaces can Claude work in?

Every marketplace your seller account reaches, across North America, Europe and Asia-Pacific. Name the marketplace in the chat, and the server sends each call to the Amazon region that serves it.

Can an agency connect its clients' Seller Central accounts?

Yes. The agency sends each client an authorization invitation for their Selling Partner account, the client consents once without sharing a login, and the account joins the agency's authorizations, reachable from the same Claude connector.

Can Claude work on Seller Central and Amazon Ads together?

Yes. Add the Amazon Ads MCP as a second custom connector and switch both on in the same chat. Claude's Free plan allows only one custom connector, so two servers need Pro, Max, Team or Enterprise. See How to connect Amazon Ads to Claude.

Connect your Amazon accounts to Claude: the Claude setup for every Kuudo server.
How to connect Amazon Vendor Central to Claude.
How to connect Amazon Seller Central to ChatGPT.
Anthropic's guide to custom connectors using remote MCP.

<- Previous How to Connect Amazon Ads to Claude Next -> How to Connect Amazon Vendor Central to Claude