Summary
Saved preferences plus a checkout link rather than a charge is the right shape for a small commerce server.
Stored brewing preferences turn a catalogue into a recommendation without any modelling — knowing someone uses a moka pot excludes most of the list immediately. And returning a checkout URL rather than completing the purchase keeps the payment decision with the person while the agent does the tedious part. That boundary is what makes it safe to leave connected, and it is the same choice the better commerce servers make.
What it is
A coffee shop client with five tools: store and read your brewing preferences, browse and open products, and create an order returning a checkout URL.
What you get
- set_preferences and get_preferences hold the brewing method and taste defaults, so recommendations are filtered rather than generic.
- list_coffees supports filtering and get_coffee_detail opens one in full.
- create_order takes one or more coffees and returns a checkout URL — the payment happens where you complete it, not in the tool.
Requirements
Nothing to supply.
Setup effort
One command — npx -y doppio-coffee-mcp