Connecting Claude to your Amazon data
Sales fell last week. The seller report shows orders; the ad report shows spend. To understand what changed, Claude needs the same account, marketplace and dates in both.
MCP connects the assistant to tools, not to a pasted spreadsheet.
A Monday export can answer a Monday question. By Friday, it is already a snapshot. Seller Central, Vendor Central and Amazon Ads keep different records, and a conversation that loses the report name or date range can make them sound like one set of numbers.
01 / THE PROBLEM
A sales file is not a sales diagnosis
An advertising export can show what a campaign spent. It cannot tell you how many units were available to buy. If sales dropped while ads kept running, check the seller report and the stock snapshot before treating campaign spend as the cause.
It also matters which business the numbers belong to. A vendor’s shipped-sales figure and a seller’s ordered-sales figure are not two versions of the same measure. Name the account, marketplace, report and week before asking for a comparison.
If one report ends Sunday and another ends Monday, stop there. The weeks do not match.
02 / THE CONNECTION
Give Claude a path to the data
Model Context Protocol (MCP) lets Claude call tools on 1stPage’s remote server. Add 1stPage as a connector, sign in through its OAuth flow, and ask about an Amazon account your 1stPage user can access. The tool call names an account and marketplace; Claude does not gain every Amazon report just because it is connected.
Get the 1stPage connection URL
Sign in to Connect MCP and copy the remote server URL. No API key belongs in a chat prompt.
Add it in Claude
Use the custom connector flow in your supported Claude client. Sign in to 1stPage through the OAuth window and review the access request.
Specify the account
Check which accounts your 1stPage user can see. Name one account, marketplace and period in your question; consent is not a per-account picker.
Connection steps and available reports depend on your account permissions and the Claude client you use. Confirm what your connection can access before relying on an answer.
Amazon announced a separate Selling Partner plugin in beta with Claude for sellers in its US stores on September 23, 2026. That route brings Seller Assistant into Claude. It does not establish access to every report discussed here. Check eligibility in your own seller account and read Amazon’s announcement.
03 / START HERE
Start with a question the report can settle
Begin with one account and two complete weeks. Ask which ASINs explain the difference. If the answer names an ad campaign or a stockout, ask for the separate report that supports it.
Why were sales down last week?
Find the ASINs behind the drop, then check whether visits or orders per visit moved.
Did spend rise because of more clicks or a higher cost per click?
Reconcile spend to clicks and CPC for the same campaigns and dates.
Which products need attention before we run out?
Check sellable units, inbound stock and recent demand for the same SKU.
Are we talking about vendor or seller sales?
Seller sessions cannot explain a vendor's shipped-sales report.
“For my US seller account, compare last week with the week before. Which products explain the change in sales, and what happened to their ads and inventory? Show the dates and sources you used.”
EXAMPLE QUESTION · NOT A LIVE PRODUCT RESPONSE04 / A FINAL CHECK
The answer stops where the data stops
A connected assistant is only as useful as the access behind it. Check which account and marketplace are selected. Do not paste API keys or Amazon credentials into a prompt. And if a report is unavailable, say so rather than asking the model to fill in the gap.
When an inventory report is missing, “we cannot test the stockout theory” is useful. A confident guess about the missing report is not.
Start with the report, not the prompt. The field guide separates seller, vendor, Ads and search-query questions into their own workflows.
Read the full field guide ↗