Orders, change history, and API logs, now in MCP
Your AI assistant can now see which Hello Retail solution drove each sale, who changed a configuration and when, and which API calls are failing. Feed setup and reference guides for the assistant are new too.
PlatformMCP
The Hello Retail MCP server can now answer questions about your whole account. Ask what drove each sale, who changed what, and where your integration is failing.
Why it matters
“Which orders came through Search?” and “Who changed my search setup?” now have direct answers. Your AI assistant reads them from your Hello Retail order data and change history.
What you can ask for
- Orders. See what was bought and which Hello Retail solution drove each product, down to the search config, Recommendations box, or campaign.
- Audit log. Who changed a configuration, when, and which fields, with the changes that mattered highlighted.
- API log. Failed calls and response times for your integration. Recording is off by default, and runs for seven days once you switch it on.
- Feeds and content. Create and update product feeds as well as monitor them, and check whether a content re-index has finished.
- Reference guides. Guides the assistant reads before it writes a feed, an algorithm, or a campaign, so it gets the format right the first time.
A good first request:
Which of yesterday’s orders came through Search, and which search configs drove them?
Every tool, with ready-to-paste prompts, is in the developer docs.
