Guides
What MCP means for ecommerce reporting
The Model Context Protocol turns marketplace and ad APIs into tools an assistant can call. Here is why that changes how sellers get their numbers.
Product team, SellerPort MCP · · 6 min read
Most sellers already have the data they need. It is spread across Seller Central, an advertising console or three, an analytics property, and perhaps a second marketplace. The hard part is not access — it is the hour spent exporting, cleaning, and joining before a simple question can be answered.
From APIs to tools
The Model Context Protocol (MCP) is an open standard for connecting AI assistants to external systems. Instead of the assistant learning every provider’s API, an MCP server exposes a set of tools with clear names and inputs — for example, “get sales for a marketplace and date range”. The assistant decides which tools to call, the server handles the provider details, and the answer comes back as data.
- The assistant sees business tools, not OAuth flows or pagination.
- Provider quirks — report delays, time zones, marketplace IDs — are handled once, on the server.
- The same tools work in any MCP-compatible client.
Why the server, not the assistant, should hold credentials
An assistant should never see a refresh token. Keeping credentials in an encrypted vault on the server means they are decrypted only for a single provider call, refreshed before they expire, and revocable in one place. The assistant authenticates with its own MCP token, which can be revoked without touching the underlying connection.
What changes day to day
Questions that used to wait for a weekly report — which marketplace grew fastest, which campaigns overspent, which SKUs will run out — can be asked whenever they come up. Because the data is read at question time, the answer reflects what the provider reports right now, not last Monday’s export.