Categories › Software Development › Converters, validators, encoders & small utilities
Grind settings for 200+ home coffee grinders, conversion between them, and help choosing one.
Remote server: your requests and data go to brewmark.io. Claude Code: claude mcp add --transport http brewmark https://brewmark.io/api/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
convert_grind_setting — Translate a grind setting from one coffee grinder to another. Use whenever a recipe quotes a setting for a grinder the user does not own — "get_grinder_chart — Grind settings for one grinder across every brew method. Use this for any question of the form "what grind should I use for my <grinder>", "dial_in — The next grind setting to try after the user brewed and tasted: "I used 18 on my Encore and it was sour", "my espresso is bitter at 4.5 on tfind_grinder — Shortlist coffee grinders for someone deciding which one to buy: "which grinder should I get for pour over under $200?", "a quiet grinder fotranslate_recipe — Turn a recipe written in the open BrewMark Protocol into a setting on the user's own grinder. Use when a coffee bag or roaster gives a BrewMlist_grinders — Every grinder BrewMark supports. Use this to check whether a grinder is covered, or to disambiguate when another tool reports more than one Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.