October 2026
Historical note · October 2026 · Describes Brew MCP 3.0 as of October
2026. For current behavior, see MCP Authentication and
Scoping.
What Shipped
An assistant connected to Brew can send email and change contact data. Before October, only a campaign send or an audience run stopped for your approval. Firing a trigger or deleting contacts ran as soon as the agent called it. Through early October, Brew prepared its MCP server for Claude’s connector directory. The changes landed in stages and were complete with version 3.0.0 on October 12. Together they put a person in the loop for anything that reaches other people.Approval on More Actions
On OAuth and organization connections, these now return an approval request before they run:- firing a trigger;
- deleting contacts or a contact field;
- publishing an automation, resuming one, or stopping contacts mid-flow;
- resuming a paused send or audience run;
- testing to anyone but yourself.
confirmation_id.
Contacts Come From Your Systems
An agent no longer creates contacts. It updates people who are already in Brew, and a send from chat goes only to subscribed contacts. New contacts come from the app, a connected integration, or your own signup flow over the API.Clearer Tools
- One action per tool.
control_email_sendsplit intopause_email_send,resume_email_send, andcancel_email_send, and audience runs split the same way. - Names that say what they do.
save_contactbecameupdate_contact,import_contacts_csvbecameupdate_contacts_csv, andsend_flarebecamereport_tool_issue. - Safety hints on every tool. Each one says whether it reads, writes, overwrites, or reaches outside Brew, so your client can ask before the risky ones.
- New guided workflows.
configure_brandandrun_audience_automationwalk an agent through brand setup and a one-off automation run.
Get Started
Reconnect your assistant from the MCP Quickstart. MCP Tools lists all 89 tools, pluscreate_brand
on organization connections.