I Fed Brewfather's API to Claude and Built My Own MCP Server
Last updated: 31.05.2026
I Fed Brewfather's API to Claude and Built My Own MCP Server
Audio Narration
Brewfather is a comprehensive app for homebrewers that manages recipe design, batch tracking, fermentation logs, water chemistry, and ingredient inventory, making it a central hub for homebrew recipes. An MCP (Model Context Protocol) server acts like a plugin that exposes local tools and data to an AI such as Claude, letting it call a locally run server without any cloud intermediary or custom UI. Using Brewfather’s REST API, the author fed the documentation to Claude and quickly generated a local MCP server that connects Brewfather to Claude Code. This setup enables three key capabilities: browsing and inspecting real Brewfather recipes, checking the brew schedule and batch stages, and verifying whether the ingredient inventory is sufficient for an upcoming brew day. The main benefit is turning brewing data into a conversational interface, so users can simply ask questions like whether they are ready to brew on a given day. Future extensions could include logging fermentation readings, auto-creating batches from recipes, and sending notifications as batches progress through stages.
What is Brewfather?
Brewfather is the go-to app for homebrewers. It handles everything — recipe design, batch tracking, fermentation logs, water chemistry, and ingredient inventory. If you brew beer at home, there is a good chance your recipes already live there.
What is an MCP Server?
MCP stands for Model Context Protocol. It is a standard that lets you expose tools and data to an AI like Claude. Think of it as a plugin — you run a local server, and Claude can call into it during a conversation. No cloud middleman, no custom UI. Just your data, your rules.
How I Built It
Brewfather has a solid REST API. I pulled up the API documentation and fed it straight to Claude. I described what I wanted — a local MCP server that could talk to Brewfather on my behalf — and Claude generated the server code. A few tweaks later it was running locally and connected to Claude Code. The whole thing took an afternoon.
What It Can Do
Three things immediately became useful:
Browse my recipes. I can ask Claude to pull up any recipe by name, show me the grain bill, hop schedule, or yeast selection — all from my actual Brewfather library.
Check my brew schedule. The MCP can look up my batches and tell me when my next brew day is planned, what recipe it is, and what stage I am at.
Verify ingredient inventory. Before brew day I can ask Claude to check whether I have enough of everything for the recipe. It reads my inventory from Brewfather and flags anything that is running low or missing.
Why This Is Cool
The shift here is that your brewing data becomes conversational. Instead of opening the app, navigating to inventory, and cross-referencing a recipe manually — you just ask. "Am I ready to brew this Saturday?" and get a straight answer. That is the kind of practical AI utility that actually changes how you work.
What's Next
There is plenty of room to extend this. Logging fermentation readings, automatically creating new batches from a recipe, getting notified when a batch moves to the next stage. The API supports all of it. If you are a developer who also homebrews, or just curious about what you can build with MCP servers, this is a great weekend project to try.
6 Claude Power Prompts That Change How You Build
Most people use Claude as a smarter search engine, but it can be a disciplined collaborator if you structure your prompts. The article outlines six patterns to unlock this mode. First, launch subagents to split work: one checks brand tone, another reviews code, a third drafts copy, each operating independently to avoid context bleed. Second, write a spec before coding, clarifying purpose, scope, and key decisions while changes are still cheap. Third, have Claude interview you first to surface hidden assumptions, co-create a spec, and get approval before implementation. Fourth, define how success will be verified upfront, then actually run that check afterward, especially for sensitive systems like payments or auth. Fifth, convert productive sessions into a reusable SKILL.md, including gotchas so lessons persist beyond the chat. Sixth, once a workflow is proven through manual runs, automate it via scripts, cron jobs, or CI. All six follow a meta-pattern: plan → build → verify → learn → automate, shifting you from just prompting Claude to designing how it works with you.
Read post
How I Used My Own Blog to Research My Presentation About It
The author needed a fast way to collect 14 blog posts for a presentation without manually copy-pasting from the browser. Fortunately, the blog already exposed each post as clean markdown at /md/posts/[slug], originally built for AI tools. This endpoint strips away HTML, navigation, and cookie banners, returning only the core content, which the author then fed into Claude for rapid reading and summarisation. Before working with individual posts, the author used /llms.txt, a structured, machine-readable index of the site similar to robots.txt but designed for AI discovery. Claude used this index to understand the site’s structure and locate relevant posts. For the presentation itself, the author used Slidev, a markdown-based slide tool, allowing Claude to generate and refine slides directly in markdown. The experience highlighted a “meta” benefit: infrastructure built for AI and other developers ended up being most useful to the author, demonstrating that investing in AI-friendly content formats can pay off immediately for the site owner.
Read post