v0.3.3 - deal rows that inherit your site's CSS

New output format, and the first release properly listed in the MCP registry.

html-deals

The existing HTML formats render a self-contained card with its styling baked in. That is right for a one-off embed and wrong the moment it lands in a post that already has house styling - you end up with somebody else design sitting in the middle of your article.

html-deals emits structure instead: .amazon-deals-section wrapping one .amazon-deal-row per product. If your theme already styles those classes, the output inherits them and there is nothing to restyle. If it does not, pass includeCss: true for a sensible default.

Rows are a fixed 70px, so ten products read as a scannable list rather than ten screens of scrolling. Feature bullets are off by default for the same reason - featureCount opts back in.

Find me three burr coffee grinders and give me deal rows for the post

Two things it will not print

• A Prime badge. Nothing in the Creators API response says whether an item is Prime-eligible. Printing it anyway would be inventing a delivery promise on a page someone may buy from.
• Empty stars. customerReviews.starRating and .count are requested on every call, but Amazon only returns them for eligible Associates accounts. Where there is no rating, the block is dropped rather than rendered as zero. If your rows have no stars, that is the account rather than the tool.

Restraint about claims is the point here, not a gap.

Also

• Listed in the official MCP registry for the first time - the repo had no server.json or mcpName, so it could not be registered at all.
• The README logo used a relative path, which never renders on npmjs.com.
• The Snyk badge pointed at a repo that is not this one.
• The disclosure prints a readable date instead of an ISO timestamp. The Associates terms want the time prices were checked, not second precision.

103 tests pass, lint clean.

npx @houtini/amazon-creators-mcp@latest