Amazon MCP Server - Product Data for AI Agents
Pricing
from $3.00 / 1,000 read operations
Amazon MCP server for Claude, ChatGPT and Cursor. Search products and read live prices, buy-box offers, public reviews and bestseller rankings across US, UK, French and German stores, with no Amazon API key. Not affiliated with Amazon. By MrBridge (mr-bridge.com)
All notable changes to this Actor. Dates are the build date. Versions are Apify build numbers, so they advance on every deploy and skip the ones that failed to build.
task-results dataset view showing what a run fetched, alongside the existing
receipts view used by Standby..actor/actor.json. apify push
never wrote them to the live Actor, so the manifest was a second source of truth
that only ever disagreed with the first.tool-action and would additionally fire the synthetic dataset event.products. prefix.query, category, page and maxResults are hidden rather than removed. They
remain in the schema, in the parser and in every saved Example, and an API caller
can still send them: only the form stopped showing them.A best sellers category that does not resolve now returns NOT_FOUND instead of
PARSE_ERROR. The extractor always told the two apart, grid rendered with no
cards being an unknown category rather than a layout change, but the fetch ladder
converted every extractor exception into PARSE_ERROR and that judgement never
reached the caller. Two costs: a caller was told their well-formed slug had hit a
layout change, and the alarm that means "go read the extractor" fired on every
typo. Measured on /gp/bestsellers/computers and /gp/bestsellers/toys, which
Amazon answers with 200, no redirect, the page frame rendered, and the word
undefined where the department name belongs.
On the vendor tier, that same verdict now stops the chain instead of failing over. A category that does not exist will not exist for the next vendor, and the second call buys the same answer at the same price.
The propagated NOT_FOUND carries the ladder's facts: tier, outbound attempts,
ladder duration, queue and token waits, and the vendors actually tried. Passing
the extractor's error through untouched had dropped all of them, so tool_call
could no longer show that nothing escalated.
Only NOT_FOUND is propagated. Every other extractor exception, taxonomy or native,
still reports PARSE_ERROR. The enrichment builds a new error rather than mutating
the original, and inherits none of its details: the best sellers extractor throws
with the caller's own slug in there, and telemetry outlives the run.
GET /mcp is used. The server supports
Streamable HTTP through POST /mcp, but does not expose a standalone GET event
stream.Promise.race against a timer, which bounded the wait
and left the request on the wire until the ladder's global abort fired up to
twenty seconds later, still billed by the vendor and still holding its rate-limit
slot. Each attempt now carries its own AbortController, combined with the
ladder's, and the socket dies at its own 7 s deadline.asin accepts up to 2048 characters instead of 512. It doubles as a full product
URL and Amazon's tracking tail grows without warning, so a legitimate URL was
refusable for a reason the caller could not see. 2048 is what browsers and
proxies already treat as safe.buildTag: "canary". apify push uploads the manifest and it
overwrites the remote value, so a manifest saying latest promoted straight to
production on a bare push. Every build now lands on canary and production moves
only by an explicit tag move.tools/list now describes every field of every result,
including the objects inside products, reviews and offers, which were
previously published as opaque objects. A client can plan against the schema
instead of calling the tool to find out what comes back.## Quick Start at the top of this README and on the Actor's Input tab, with the
real endpoint and the two ways to authenticate.coverage in the amazon://marketplaces resource, stating per tool which
storefronts it serves.amazon_bestsellers accepted a category containing path
separators, which let a caller steer the request to another Amazon path. The
category is now a single slug of letters, digits and hyphens, and the handler
encodes it as well. Refused calls cost nothing: no fetch, no charge.-32602 instead of being dropped in silence, which previously meant
a caller could be billed for a call whose argument was never read.query (256), category (100), marketplace (8) and asin
(512), published in tools/list.error.message is capped at 400 characters.eventId in error.data, so the identifier
in the server log is one the caller can actually quote.amazon_search withdrawn on FR. Five spaced searches on amazon.fr all came back
as challenges, on both fetch tiers, while the product and best-seller pages
answered normally through the same proxy country. The call now returns
UNSUPPORTED_MARKETPLACE before any request is made, so it costs nothing.