Connecting Claude to your Amazon data
Sales fell. Was it traffic, conversion, ad spend, or a stockout? Claude can help you work through that question, but only if it can see the right numbers from the right account.
MCP connects the assistant to tools, not to a pasted spreadsheet.
You already have the data. It just lives in different places: Seller Central, Vendor Central, advertising reports, and the spreadsheet somebody exported on Monday. The hard part is getting the right slice into the conversation without losing its source.
01 / THE PROBLEM
The missing link is context
Paste an advertising export into a chat and Claude can summarize it. Ask why sales dropped, though, and the answer may need orders, inventory, and ads from the same time period. A single CSV cannot tell you whether a product was out of stock while its campaign kept spending.
It also matters which business the numbers belong to. A vendor account and a seller account are not interchangeable. An answer without an account, marketplace, and date range is easy to read and hard to trust.
A useful question is not just “what happened?” It is “what happened in this account, in this period, and what evidence supports it?”
02 / THE CONNECTION
Give Claude a path to the data
Model Context Protocol (MCP) lets an assistant call tools from an external service. Instead of uploading last week’s file, you connect your authorized Amazon accounts to 1stPage and make the relevant, account-scoped tools available to Claude. Then you ask a question in the place where you already work.
Authorize your accounts
Choose the Amazon accounts you want 1stPage to read. The available data depends on the account and its permissions.
Connect the data tools
Add the 1stPage MCP connection in a supported Claude environment. Follow the current setup flow rather than sharing credentials in chat.
Ask, then check the scope
Start with one account and a clear time window. Confirm the source and period before acting on an answer.
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.
03 / START HERE
Ask questions you would give an analyst
Keep the first question narrow. Include the account, the marketplace, and the dates. If an answer sounds too neat, ask which inputs it used.
Why were sales down last week?
Compare the same account and marketplace across periods before deciding what changed.
Did spend rise because of more clicks or a higher cost per click?
Separate traffic from efficiency instead of treating the total spend line as the story.
Which products need attention before we run out?
Put stock and demand in the same conversation, scoped to the products you sell.
Are we talking about vendor or seller sales?
Name the account and data source so a plausible answer does not become the wrong answer.
“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
Keep the scope clear
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.
The goal is not to make every answer sound confident. It is to make it easier to follow a business question back to the data that can actually answer it.