Skip to content
Custom Connectors

Connect Amazon Seller Central to Claude Code

Let Claude edit listings, adjust prices, and update inventory in Amazon Seller Central. From the terminal, inside the sessions where you already work.

How do you connect Amazon Seller Central to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Amazon Seller Central, you add a Amazon Seller Central MCP server: a small hosted service that exposes Amazon Seller Central's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Amazon Seller Central account. No API keys pasted into config files.

claude mcp add --transport http amazon-seller-central https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Amazon Seller Central once connected?

Full read-write access lets Claude update a listing's title and details, adjust a price within your guardrails, change inventory quantities, and confirm shipment status on an order, all after your approval. The listing maintenance and pricing work that meant tab-switching happens where your catalog already lives.

  • Update a listing's title, bullet points, or description for a given SKU
  • Adjust the price on a SKU within limits you set
  • Change available inventory quantity for a product
  • Send Amazon's templated buyer message for an order, such as a delivery or order confirmation
  • Create a new listing draft from product details you provide
  • Confirm or update shipment status on an order

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Amazon Seller Central access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Amazon Seller Central API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Amazon Seller Central changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Amazon Seller Central connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Amazon Seller Central connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Amazon Seller Central account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Amazon Seller Central's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Amazon Seller Central?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Amazon Seller Central account it signs in with. Revoking access is one click in Amazon Seller Central.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.