Connecting AI assistants to Breww (Breww MCP)

The Breww MCP lets you connect an AI assistant, such as Claude or ChatGPT, to your Breww account. Once connected, you can ask the assistant questions about your Breww data and, if you allow it, have it create and change records for you.

MCP (Model Context Protocol) is the standard that AI assistants use to connect to other software. Any assistant that supports remote MCP servers can connect to Breww.

Who can connect an assistant

Only users with the Admin permission can connect an AI assistant or see the Breww MCP page, because a connected assistant has broad access to your account's data.

Each person connects an assistant for themselves. If three admins all want to use Claude with Breww, each of them connects it from their own Claude account, and each connection is listed separately.

Before you connect: risks to be aware of

Connecting an AI assistant gives another company's software access to your Breww data. Make sure you are comfortable with the following before you connect one.

• 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.

Connecting an assistant

1. Go to Integrations -> AI assistants (MCP). This opens the Breww MCP (AI assistant connections) page. The same page is listed in Settings as Breww MCP (AI assistant connections), under Account & data.
2. In the Connect an AI assistant card, copy the server URL.
3. Choose the tab for your assistant and follow the steps shown. The steps for the most common assistants are also below.
4. When the assistant sends you to Breww, sign in and approve access. See "Approving access" below.

Claude

1. In Claude, open Customize, then Connectors, and choose Add custom connector.
2. Paste the server URL and choose Add.
3. Choose Connect, sign in to Breww and approve access.

On a Claude Team or Enterprise plan, an Owner adds the connector first under Organization settings, then Connectors. Each person then connects it themselves.

ChatGPT

1. In ChatGPT on the web, open Settings, then Security and login, and enable Developer mode.
2. Go to chatgpt.com/plugins, choose the plus button, then Create App, followed by Create MCP App.
3. Enter Breww as the name. The icon and description are optional.
4. Under Connection, keep Server URL selected and paste the server URL.
5. Set Authentication to OAuth. You don't need to change the Advanced OAuth settings.
6. Select I understand and want to continue, then choose Create.
7. Sign in to Breww when asked and approve access.
8. To use it, start a new chat and add Breww from the tools menu.

This is available on ChatGPT Plus, Pro, Business, Enterprise and Education plans. On a Business, Enterprise or Education plan, a workspace admin may need to allow Developer mode first.

Claude Code, Cursor and VS Code

The Claude Code, Cursor and VS Code tabs each show a command or configuration snippet with your server URL already filled in. Copy it from the tab, then sign in to Breww when the tool asks.

Other assistants

Any assistant that supports remote MCP servers over Streamable HTTP with OAuth can connect. Paste the server URL into the assistant, sign in to Breww and approve access.

Approving access

When an assistant connects, Breww shows a page naming the assistant, with the website it connects from in brackets, and the Breww account it is asking to connect to. If you have access to more than one Breww account, check that the right one is named before you continue.

Choose the level of access to give:

• Read and write - the assistant can see, create, change and delete data.
• Read only - the assistant can see data, but can't create, change or delete anything.

Then press Authorize to connect, or Deny to cancel.

What a connected assistant can do

An assistant works with the same data as the Breww public API. It can look up records, and with Read and write access it can also create, update and delete records and run actions.

Anything the public API doesn't cover isn't available to an assistant either.

Viewing and disconnecting assistants

The table on the Breww MCP page lists every assistant connected to your account:

• Assistant - the assistant's name, followed by the website it connects from in brackets.
• Connected by - the person who connected it.
• Access - Read and write or Read only.
• Connected - the date it was connected.
• Last used - the date and time the assistant last used the connection, or Never.

To remove a connection, press the red disconnect button in the Actions column of its row (hover over it to see Disconnect) and confirm. The assistant loses access straight away. Any admin can disconnect any connection on the account, not only their own.

A connection also stops working straight away if the person who connected it stops being an admin, loses access to the account or is deactivated.

Usage limits

Each assistant has a usage allowance per Breww account, with the same limits as the Breww public API. Everyone on your account who uses the same assistant shares that allowance. If an assistant reports that it has been rate limited, wait a little and try again.

Troubleshooting

• "Only brewery admins can connect AI assistants." Your user doesn't have the Admin permission. Ask an admin on your account to connect the assistant.
• "This AI assistant sent an invalid sign-in request." Start the connection again from the assistant. If it keeps happening, the assistant may not fully support remote MCP servers.
• The assistant stops working. Check that the connection is still listed on the Breww MCP page and that the person who connected it is still an admin. If it isn't listed, connect it again.