Grind settings for 200+ home coffee grinders, conversion between them, and help choosing one. Connect the official Brewmark MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.
Free to start · No credit card · No hosting needed
Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.
claude mcp add --transport http brewmark https://brewmark.io/api/mcpRun in your terminal, then restart Claude Code.
Brewmark · https://brewmark.io/api/mcp
Real prompts you can type the moment it's connected — no setup, no docs to read.
“Use “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 — ".”
“Use “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>", ".”
“Use “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 t.”
“Use “find_grinder”: Shortlist coffee grinders for someone deciding which one to buy: "which grinder should I get for pour over under $200?", "a quiet grinder fo.”
Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how Brewmark holds up.
Operated by Brewmark (brewmark.io) at its documented MCP endpoint — not a third-party mirror or community re-host.
This server only exposes public data — no account and no credentials are involved when you connect.
gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.
If Brewmark adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.
Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.
Choose Brewmark in the gate directory. No sign-in needed.
Brewmark's tools are live in every AI client you've connected — with rules and logging built in.
Free to start · No credit card · No hosting needed
Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.
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 t
find_grinder — Shortlist coffee grinders for someone deciding which one to buy: "which grinder should I get for pour over under $200?", "a quiet grinder fo
list_grinders — Every grinder BrewMark supports. Use this to check whether a grinder is covered, or to disambiguate when another tool reports more than one
https://brewmark.io/api/mcpYes — Brewmark operates its own remote MCP server at brewmark.io. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.
Add gate's gateway URL to your AI client once, then pick Brewmark in the directory. No account or sign-in is needed. From then on, Brewmark's tools are available in every client you've connected to gate.
No. Brewmark runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.
It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.
Yes — you can get started with gate for free and connect Brewmark in minutes. No credit card required.
Every server below works through the same gateway URL — connect once, add tools anytime.
Set up Brewmark in: Claude · Claude Code · ChatGPT · Cursor · VS Code