Brewers Almanack
Give your coding agent authoritative homebrew context—styles, ingredients, water chemistry, and off-flavours—while you prototype a brewing app or content workflow.
Overview
Brewers Almanack is a MCP server for the Build phase that exposes brewing knowledge—styles, ingredients, off-flavours, water chemistry, and recipes—to AI coding agents over stdio.
What is this MCP server?
- Beer style and recipe knowledge surfaced as MCP tools for agent-driven Q&A
- Ingredient and off-flavour reference for troubleshooting batches in chat
- Water chemistry guidance without leaving the IDE
- stdio npm package brewers-almanack v0.1.0 for Claude Code–style hosts
- MCP integration layer, not a hosted SaaS or spreadsheet substitute
- Server version 0.1.0 per MCP server schema
- Single npm package identifier brewers-almanack with stdio transport
- Source repository: github.com/gregario/brewers-almanack
Community signal: 1 GitHub stars.
What problem does it solve?
Homebrew and beverage side-project builders waste time correcting agent guesses about styles, water salts, and fault flavours when they could use a dedicated knowledge MCP.
Who is it for?
Indie builders making brewing companions, educational content, or agent workflows where beer chemistry and style rules must stay consistent.
Skip if: Teams shipping generic B2B SaaS, commercial brewery ERP, or anyone who does not need beer-specific reference data in the agent.
What do I get? / Deliverables
After you register brewers-almanack, your agent can pull structured brewing answers during app prototyping, recipe tooling, or educational content drafts.
- Registered stdio MCP server exposing brewing knowledge tools to your agent
- Agent-accessible lookups for styles, ingredients, faults, and water chemistry during builds
- Repeatable local dev setup without a separate brewing SaaS account
Recommended MCP Servers
Journey fit
Canonical shelf is Build because solo builders wire this MCP into agents or apps that need structured brewing reference data, not because beer knowledge only matters during implementation. Integrations fits npm stdio MCP servers that extend Claude Code or Cursor with domain tools rather than shipping a standalone product.
How it compares
Domain knowledge MCP over stdio, not a full recipe manager app or Shopify-style commerce stack.
Common Questions / FAQ
Who is brewers-almanack for?
Solo builders and hobbyist developers who use Claude Code or Cursor and want agent-accessible brewing reference data while building apps or content around beer.
When should I use brewers-almanack?
Use it during Build when you are integrating an MCP client and need styles, ingredients, off-flavours, water chemistry, or recipe-oriented tools in the agent loop.
How do I add brewers-almanack to my agent?
Add the npm stdio server brewers-almanack (v0.1.0) to your MCP client config pointing at the published package or repo install, then restart the host so tools load.