Amazon Opens Seller Central to Outside AI Agents Through an MCP Server, Claude First

TL;DR

At its Accelerate seller conference on September 23, Amazon shipped a Selling Partner plugin that lets an outside AI agent read a seller's inventory, analytics, and listings and draft price and listing changes, without the seller opening Seller Central. It launches inside Amazon Quick and in beta with Anthropic's Claude, with "more integrations to follow." Under the hood it is a hosted MCP server gated by Seller Central's OAuth consent flow, plus an Apache-2.0 skills package on GitHub with 11 skills and an approval gate on every write. Amazon says 90% of its sellers already run their businesses with third-party AI tools. The buyer side of Amazon.com, meanwhile, remains closed to agents, and Amazon spent most of this year in court keeping it that way.

What Amazon actually shipped

Three things landed together. First, Seller Assistant, the in-console agent Amazon runs on Amazon Bedrock with Claude models, gained persistent memory of a seller's pricing patterns, inventory cycles, and growth goals, plus a canvas view for planning. Second, always-on workflows: a seller writes a condition in plain language ("alert me if any of my top 10 products drop below a 4-star rating and draft a response plan") and the assistant monitors around the clock, with guardrails and an audit trail. Third, the plugin, which carries all of that into whichever agent the seller already uses.

The plugin is in beta for sellers in Amazon's US stores, with international expansion to follow. Amazon says connecting Claude takes roughly 60 seconds and no code. To sweeten the Quick route, every primary account holder can claim a free 12-month Amazon Quick Plus subscription through December 31, 2026, and hand the same deal to two co-workers.

Mary Beth Westmoreland, Amazon's VP of worldwide selling partner experience, told SiliconANGLE the goal plainly: "Our vision was that [sellers] would never have to log into Seller Central." She told GeekWire the integration was "built in a way that should be modular enough for us to continue to publish plugins."

How the plumbing works

The interesting part is not the Claude logo, it is the transport. Amazon published a public repo, amzn/selling-partner-agentic-toolkit, created on September 21 and last pushed on launch day. Its bundled .mcp.json registers one HTTP MCP server, the Amazon Selling Partner Connector at sellingpartner-ai.amazon.com/mcp. There is a Claude plugin manifest (amazon-selling-partner, version 1.0.0, "currently in beta"), three slash commands, and 11 skills, each with its own eval file. The skill frontmatter lists the target platforms as Claude desktop and Amazon Quick, and names the persona it was written for: "Maya (non-technical FBA seller)."

We poked the endpoint. An unauthenticated request gets a 401 with a WWW-Authenticate header pointing at /.well-known/oauth-protected-resource/mcp, which is the RFC 9728 protected-resource-metadata dance. Think of a locked door that, instead of just saying no, hands you a card with the address of the office that issues keys: the client reads that metadata, finds the authorization server, and walks the seller through Seller Central's standard OAuth consent screen. The resulting token can only call tools the seller's Seller Central roles allow, and an account admin has to enable the agent under the Manage Agents permissions page before any secondary user can authorize it.

Writes are where the design gets conservative. The toolkit's own rule is what it calls the inversion pattern: the LLM proposes, the human disposes. A price change is previewed with a validation-only call first, shown as a one-line diff (SKU, current price, the price the seller typed), submitted only after the seller types "approve," and never bundled with another SKU's change. The stockout skill goes further and refuses to give pricing advice in either direction, a guardrail document that reads like it was drafted by someone who has met an antitrust regulator. It will draft exactly the number you name, and it will not have an opinion about it.

The 11 skills

• seller-analytics: inventory, traffic, and sales metrics, discovering metric IDs before querying.
• stockout-prevention: days of cover per SKU from velocity, reorder quantity and timing, inbound-shipment gap.
• fba-inbound-management: the full FBA inbound plan (create, pack, place, ship, confirm) with approval gates.
• listing-troubleshooter, listing-issues, listing-buyability, listing-searchability: a router plus three specialists for suppressed, unbuyable, or unfindable listings, each fixing with preview then approval.
• listing-compliance: an advisory pre-flight gate before any compliance-sensitive write; it never writes.
• invite-secondary-users, support-case-helper, sp-api-knowledge: admin guidance, a PII-scrubbed support-case drafter that never submits on its own, and an SP-API documentation assistant.

The numbers behind it

Amazon's favorite number this week is 90. Per the announcement, Seller Assistant has rolled out to over 90% of selling partners worldwide in their own language, has hundreds of thousands of active users, and sees its recommendations accepted over 90% of the time. And 90% of selling partners already use third-party AI tools to run their businesses, which is the real reason the plugin exists: the sellers were already pasting Amazon data into other people's agents by hand.

The money makes the priority obvious. Amazon's Q2 2026 10-Q puts third-party seller services (referral commissions, FBA and shipping fees) at $46.8 billion for the quarter, up from $40.3 billion a year earlier. That is more than AWS ($42.2 billion) and more than double advertising ($19.8 billion). GeekWire notes independent sellers move over 60% of units sold on Amazon. Anything that makes those sellers restock faster, fix suppressed listings sooner, and spend more on ads is worth an OAuth server.

Sellers in, shoppers out

Notice what did not open. API Evangelist points out that Amazon now runs two hosted MCP servers, this one and the Amazon Ads MCP Server that has been in open beta since February 2, while publishing no agentic-commerce contract, no bot-identity signal, and no consent mechanism for the buyer side of Amazon.com.

That is not an oversight. Amazon sued Perplexity last November over its Comet browser's shopping agent, won a preliminary injunction in March, and then watched the Ninth Circuit vacate it on August 4, on the reasoning that "it is the user who 'accesses' Amazon's computers" when an agent acts on their instruction. So the policy reads: agents that help you pay Amazon fees get a documented OAuth flow and a skills repo; agents that help you spend less time on Amazon.com get a CFAA complaint. Both are rational. Only one of them ships a .well-known endpoint.

What this means if you build for sellers

Look at the skill list again. Stockout alerts, listing-suppression repair, search-content optimization, inbound planning, analytics that explain a sales drop: that is the feature list of the third-party seller-tools industry, the layer of SaaS that has sat between sellers and the SP-API for a decade. Amazon has now published a first-party version of it as prompts, wired it to a first-party MCP server, and made it free inside the two agents it prefers. The moat for a seller tool is no longer "we integrated SP-API." It is proprietary data (competitor tracking, cross-marketplace inventory, supplier terms) that Amazon's connector does not return, or the pricing opinion Amazon has explicitly decided not to have.

There is a reusable pattern here for anyone who owns an API, too. Amazon did not ship a chatbot; it shipped a hosted MCP server, a metadata document so any compliant client can discover the auth server, role-scoped tools, and a versioned skills package with evals per skill, then let the model vendor supply the model. That is the shape a platform integration takes when the platform wants to be agent-agnostic and still control the write path.

Caveats

• The plugin is a US-only beta and, today, only Quick and Claude are supported. "More integrations to follow" is a promise, not a date.
• All adoption figures (the three 90s, "hundreds of thousands" of users) are Amazon's own and were not broken out further.
• The repo had 4 GitHub stars when we checked, two days after creation. The interesting artifact is the hosted connector, not the star count.
• The connector currently exposes only what Seller Central roles allow. There is no public list of the underlying tools beyond what the skills reference, and no published rate limits.
• Amazon's own Seller Assistant runs on Claude via Bedrock, so "Claude first" partly describes a partner Amazon already pays.

Key Takeaways

• Amazon's Selling Partner plugin lets outside agents manage a seller account through a hosted MCP server, in beta with Claude and live in Amazon Quick, US sellers first.
• Auth is Seller Central's OAuth consent flow with RFC 9728 discovery; tool access follows Seller Central roles, and every write is drafted for human approval.
• The Apache-2.0 toolkit ships 11 skills with evals and three commands, and deliberately gives no pricing advice.
• Amazon says 90% of sellers already use third-party AI tools; seller services brought in $46.8 billion in Q2, more than AWS.
• The shopper side stays closed: two MCP servers for people who pay Amazon, a lawsuit for the agent that shopped on it.
• For seller-tool builders, SP-API integration is no longer a moat; proprietary data and opinions Amazon will not give are.

Sources: Amazon announcement (Sept 23, 2026), amzn/selling-partner-agentic-toolkit on GitHub, GeekWire, SiliconANGLE, API Evangelist, Amazon Ads MCP Server open beta, Amazon Q2 2026 Form 10-Q, Courthouse News on Amazon v. Perplexity, RFC 9728.