Espresso Steals MCP Server

Search the espresso gear this site tracks. `products` have a live Amazon price and, when at a genuine low, a BUY call computed from their own price history; otherwise no call. Filter by slot (the role a product plays in a setup), free-text words (brand and model names, partial words and small typos are fine), a price band, a brand, or on-sale only. Products we know but cannot price (sold direct by the maker, e.g. Niche, Lelit, Decent) come back in `known_unpriced` with no price and the reason: say so, quote the note, and link the url. When nothing in `products` matches, `alternatives` lists the closest tracked products with live prices and `note` says what was and was not found. Never tell the user the site has nothing; tell them what it has.

Full detail for one product by slug: community sentiment, reference price and basis, date of the latest price observation, portafilter size (machines) or accessory size (sized accessories), superautomatic / manual-lever / hand-grinder flags, product URL and Amazon link. A known product with no price returns price null, the reason, and priced alternatives. An unknown slug returns did_you_mean.

The slots an espresso setup is built from (machine, grinder, scale, tamper…), with what each is for. Use the ids as search_catalog's `slot`.

Email the user when a product is at a good price (a verified low), or at or under a target price they name. Use after search_catalog/get_product when the user wants to be told when to buy. Ask the user for their email; never invent or reuse one. One watch per email per product; calling again updates the target. The first time an address is used it receives a confirmation email and the watch arms when they click it — tell the user to check their inbox. Each alert links to the product page and carries an unsubscribe link.