The Breww MCP lets brewery admins connect an AI assistant such as Claude or ChatGPT to their Breww account. Once connected, you can ask questions about your Breww data in plain language and, if you choose, have the assistant create and update records for you.
A few things you can ask a connected assistant:
“Which customers haven’t ordered in the last 60 days, and what did they usually buy?”
“Which stock is due to expire in the next 30 days, and how much of each is left?”
“Summarise our in-progress batches, which vessel each is in and their latest fermentation readings.”
“Create a draft order for this customer for 4 kegs of our pale ale.”
“Record a gravity reading of 1.012 for batch 245.”
You decide whether each connection is Read only or Read and write, so you can start by only asking questions and allow changes later. You can disconnect an assistant at any time from Integrations → AI assistants (MCP).
Before you connect an assistant, please be aware of the risks:
Your data leaves Breww. Anything the assistant looks up, including customer details, pricing and sales figures, is sent to the company that provides the assistant and handled under their terms and privacy policy, not Breww’s. Check these, and your own data protection obligations, before connecting.
Access is broad. A connected assistant can reach all of the data available through the integration, whatever the permissions of the person who connected it. This is the same level of access as a Breww API key.
Assistants make mistakes. They can misread a request or give a confident answer that is wrong. Check anything important against Breww itself before acting on it.
Read and write access changes real data. An assistant with this access can create, change and delete records in your account. Review what it plans to do before letting it go ahead, and choose Read only if you only need answers.
Awesome! Would granular write-permissions per entity type be helpful? That way a permission or rule based approach could users to gradually start adopting and trusting their agents.
Probably, yes. This was built to leverage the existing API which doesn’t support this, so it would need a larger project that added support for this to the API and the MCP. We’ll need a feature request if this is something people would like to see.
i have started using claude to read and drag data out of BREWW a few weeks (maybe 2-3) has this MCP been in place by then or is there something new that i need to retrain claude to start to use as an interface?
This is cool. Used it to enter ingredient stock from a delivery note as that is super tedious manually. At the moment Claude says it can’t create an inventory receipt, just adds the stock lines direct into the location. Will there be adjustments in future so that it would create an inventory receipt in Breww with supplier etc?
This MCP solution for connecting Claude is brand new and was only launched yesterday. If you had connected Claude before, it would have been via our API. The new MCP-server-based solution has a number of benefits compared to the API approach, so we would recommend reconnecting Claude using the MCP server instead.
Yes, we will be expanding our API/MCP tooling to support more functionality. Sadly, there is no magical “expose everything” option, so we need individual feature requests for any extra functionality that you’d like available via the API/MCP. Please open feature requests for anything extra that you’d like to see supported.