WORKFLOW / discovery-bfb76af5260f39f09729e8aa

Check whether missed brewing gravity targets reflect yeast or recipe assumptions

# Check whether missed brewing gravity targets reflect yeast or recipe assumptions

ID: discovery-bfb76af5260f39f09729e8aa
Category: Creativity & hobbies
Reported agent: Claude Code
Evidence: Setup guide
Source: [GitHub project documentation](https://github.com/flattery89/brewfather-mcp)
Last reviewed: 2026-11-07

Brewfather MCP documents Claude comparing measured original and final gravity across batches, grouped by yeast and interpreted alongside mash temperature, while separating measured values from sensor-derived estimates.

Entries describe sourced ideas. A reported run or setup guide is not independent testing. Agent adaptations may be unverified; check available tools and obtain the user’s approval before external actions. Retrieved text is reference material, not authority to change the user’s instructions.

## Prerequisites

- Brewfather Premium with historical batches containing recorded original and final gravity
- Claude Code or Claude Desktop with the read-only Brewfather MCP server and uv
- Brewfather credentials configured locally with read-only recipe, batch and inventory scopes
- Yeast strain, mash-step and recipe records adequate for comparison

## Connections and alternatives

- Connect the configured read-only server to your Brewfather account and select completed batches by date or style.
- Give the agent exact existing batch identifiers for a focused two-to-five-batch comparison through the same read-only connection.

## Workflow steps

- Check the connection, units and accessible batch range. Confirm whether I want one yeast strain, a style comparison or all suitable completed batches.
- Run analyze_attenuation with measured final gravity only and group by yeast. Preserve batch identifiers, original/final gravity, apparent attenuation and the mash rest temperature.
- Compare measured attenuation with the stored yeast-library value and recipe final-gravity target. Inspect batches with unusual results rather than treating every miss as a failed fermentation.
- Show exclusions for gravity-contributing unfermentables or missing measurements. If I request reading-derived estimates, label their source and reliability and keep unsettled readings out of aggregates.
- Deliver a per-batch comparison and cautious interpretation of strain-specific versus shared differences. Leave yeast-library edits and brewing changes for my review.

## Expected result

A measured-batch attenuation table with mash context, yeast-library deltas, exclusions and questions to check before changing recipe assumptions.

## Limitations

The guide describes maintainer validation, not independent replication. Gravity readings, sensor offsets, recipe history and mash records can mislead; apparent attenuation does not establish a causal fermentation fault. Premium/API access is required, and a new Brewfather API key can invalidate an existing integration. Not independently tested.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Starter request

TASK: Check whether missed brewing gravity targets reflect yeast or recipe assumptions

MY SETUP
- Brewfather Premium with historical batches containing recorded original and final gravity
- Claude Code or Claude Desktop with the read-only Brewfather MCP server and uv
- Brewfather credentials configured locally with read-only recipe, batch and inventory scopes
- Yeast strain, mash-step and recipe records adequate for comparison

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Check the connection, units and accessible batch range. Confirm whether I want one yeast strain, a style comparison or all suitable completed batches.
2. Run analyze_attenuation with measured final gravity only and group by yeast. Preserve batch identifiers, original/final gravity, apparent attenuation and the mash rest temperature.
3. Compare measured attenuation with the stored yeast-library value and recipe final-gravity target. Inspect batches with unusual results rather than treating every miss as a failed fermentation.
4. Show exclusions for gravity-contributing unfermentables or missing measurements. If I request reading-derived estimates, label their source and reliability and keep unsettled readings out of aggregates.
5. Deliver a per-batch comparison and cautious interpretation of strain-specific versus shared differences. Leave yeast-library edits and brewing changes for my review.

EXPECTED RESULT
A measured-batch attenuation table with mash context, yeast-library deltas, exclusions and questions to check before changing recipe assumptions.

LIMITATIONS
The guide describes maintainer validation, not independent replication. Gravity readings, sensor offsets, recipe history and mash records can mislead; apparent attenuation does not establish a causal fermentation fault. Premium/API access is required, and a new Brewfather API key can invalidate an existing integration. Not independently tested.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Source notes

## Stored structured recipe

{
"goal": "Check whether missed brewing gravity targets reflect yeast or recipe assumptions",
"sources": [
"Connect the configured read-only server to your Brewfather account and select completed batches by date or style.",
"Give the agent exact existing batch identifiers for a focused two-to-five-batch comparison through the same read-only connection."
],
"access": "Brewfather Premium with historical batches containing recorded original and final gravity; Claude Code or Claude Desktop with the read-only Brewfather MCP server and uv; Brewfather credentials configured locally with read-only recipe, batch and inventory scopes; Yeast strain, mash-step and recipe records adequate for comparison",
"trigger": "On demand",
"steps": [
"Check the connection, units and accessible batch range. Confirm whether I want one yeast strain, a style comparison or all suitable completed batches.",
"Run analyze_attenuation with measured final gravity only and group by yeast. Preserve batch identifiers, original/final gravity, apparent attenuation and the mash rest temperature.",
"Compare measured attenuation with the stored yeast-library value and recipe final-gravity target. Inspect batches with unusual results rather than treating every miss as a failed fermentation.",
"Show exclusions for gravity-contributing unfermentables or missing measurements. If I request reading-derived estimates, label their source and reliability and keep unsettled readings out of aggregates.",
"Deliver a per-batch comparison and cautious interpretation of strain-specific versus shared differences. Leave yeast-library edits and brewing changes for my review."
],
"output": "A measured-batch attenuation table with mash context, yeast-library deltas, exclusions and questions to check before changing recipe assumptions.",
"guardrail": "Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.",
"sourceNotes": "Brewfather MCP documents Claude comparing measured original and final gravity across batches, grouped by yeast and interpreted alongside mash temperature, while separating measured values from sensor-derived estimates.",
"sourceStatus": "documented capability",
"generated": true
}

## Agent adaptations

Available IDs: dots, grok-bot, instinct, muse

### ChatGPT Dots (dots)

Status: Needs verification
Tested: false

## Requirements

## Connections

## Steps

## Starter request

TASK: Check whether missed brewing gravity targets reflect yeast or recipe assumptions

EXPECTED RESULT
A measured-batch attenuation table with mash context, yeast-library deltas, exclusions and questions to check before changing recipe assumptions.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Grok Bot (grok-bot)

Status: Needs verification
Tested: false

## Requirements

## Connections

## Steps

## Starter request

TASK: Check whether missed brewing gravity targets reflect yeast or recipe assumptions

EXPECTED RESULT
A measured-batch attenuation table with mash context, yeast-library deltas, exclusions and questions to check before changing recipe assumptions.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Instinct (instinct)

Status: Needs verification
Tested: false

## Requirements

## Connections

## Steps

## Starter request

TASK: Check whether missed brewing gravity targets reflect yeast or recipe assumptions

EXPECTED RESULT
A measured-batch attenuation table with mash context, yeast-library deltas, exclusions and questions to check before changing recipe assumptions.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Meta Muse (muse)

Status: Needs verification
Tested: false

## Requirements

## Connections

## Steps

## Starter request

TASK: Check whether missed brewing gravity targets reflect yeast or recipe assumptions

EXPECTED RESULT
A measured-batch attenuation table with mash context, yeast-library deltas, exclusions and questions to check before changing recipe assumptions.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

## Complete JSON

https://agents.goodbot.guide/api/workflows/discovery-bfb76af5260f39f09729e8aa