
Brewers Almanack
io.github.gregarioPublished by GitHub account gregariov0.1.0Updated Oct 24, 2026
Brewing knowledge MCP — beer styles, ingredients, off-flavours, water chemistry, recipes
The publisher's own server: Almanack
Overview
A local MCP server that gives an AI assistant embedded brewing knowledge: beer styles, ingredients, off-flavour diagnosis, water profiles, recipes and food pair
- What you can do
- Search 85 BJCP beer styles by name, category or characteristics, with vital statistics and commercial examples. Look up hops, malts, yeasts and adjuncts by name, type or characteristic. Diagnose off-flavours from taste or aroma descriptions, with likely compound, causes and prevention. Match brewing water profiles by city or beer style, with mineral composition. Generate recipes for a target style, including grain bill, hop schedule, yeast and water profile. Suggest beer and food pairings by style or dish.
- When to use it
- Useful for homebrewers and beer enthusiasts who want an assistant to answer style, ingredient, water chemistry, recipe and pairing questions from a fixed embedded dataset rather than general model knowledge. Also handy for diagnosing a fault in a batch from a taste or aroma description.
- Requirements
- Runs as a local process via npx (Node.js required). No API keys, no environment variables and no network access; all data is embedded. Configured through the MCP settings of the chosen client.
Installation
In SourceWeft
- Open Brewers Almanack in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Brewers Almanack
A brewing knowledge MCP server: beer styles, ingredients, off-flavour diagnosis, water chemistry, and recipe guidance for AI assistants.
[npm version] [npm downloads] [MIT Licence] [Node.js 18+] [MCP Compatible] [brewers-almanack MCP server]
Ask your AI assistant about beer styles, diagnose off-flavours, build recipes, match water profiles, and pair food (all backed by real brewing data, not hallucinations).
6 tools. Zero config. Works with every MCP-compatible IDE.
Install
No API keys, no network dependencies. All brewing data is embedded.
Add to your IDE
Claude Code
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows):
Cursor
Add to .cursor/mcp.json:
VS Code (Copilot)
Add to .vscode/mcp.json:
Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
Zed
Add to settings.json:
Tools
Example Conversations
"What hops work in a Belgian Dubbel?"
Searches ingredients for hops that complement Belgian styles, returning varieties like Styrian Goldings and Saaz with alpha acid ranges, aromas, and substitutes.
"My beer tastes like butter, what went wrong?"
Diagnoses diacetyl: identifies the compound, explains causes (incomplete fermentation, premature racking), and gives prevention steps (diacetyl rest, healthy yeast pitch).
"Suggest a recipe for a West Coast IPA"
Builds a complete recipe: pale malt base with crystal malt, Centennial/Cascade hop schedule with dry hop additions, American ale yeast, and a Burton-style water profile.
"What food pairs well with a stout?"
Returns pairing suggestions (oysters, chocolate desserts, grilled meats) with principles explaining why each pairing works (complement, contrast, or cleanse).
Data Sources
Roadmap
See ROADMAP.md for planned features: brewing calculators, recipe intelligence, BeerXML/BeerJSON integration, and a brewing journal.
Contributing
Contributions are welcome, especially data contributions. More hop varieties, yeast strains, regional water profiles, and food pairings make the server more useful for everyone.
Running locally
See ROADMAP.md for areas where contributions are most needed.
Licence
Source: README.md at commit cc12713
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts