June 18, 2026. The CRM that many agencies run for clients is turning its AI assistant into an agent that operates tools, and it is putting a deadline on the old way of doing things. HubSpot's June updates push Breeze, its AI layer, toward agent-native operation through the Model Context Protocol, while setting a clock on custom assistants. If you manage HubSpot portals for clients, both halves of this matter.
What changed in Breeze
- Breeze Agents can now use additional MCP servers to pull context and take actions in G2, Linear, Gong, and Amplitude, all through plain-language prompts.
- Breeze Assistant is now available on mobile, with synced chat history and CRM-aware answers.
- A new "Create report with AI" option lets Breeze Assistant define and generate single-object or multi-object reports.
- Data Agent prompts can use multiple tokens with explicit required or optional flags, so a prompt skips cleanly, and does not burn credits, when required data is missing.
- The deadline: from June 19, 2026, accounts that have never created custom assistants can no longer create them, and on July 13, 2026, existing custom assistants become read-only and are automatically migrated to Breeze projects. Welcome messages and conversation starters must be moved over by hand.
What it means for operators
Strip away the brand names and the pattern is the one we keep flagging in 2026: the CRM's AI is becoming an agent that operates other tools through MCP, the same open standard reshaping the outbound stack we wrote about in our agent-native outbound guide. Whether a client runs HubSpot or GoHighLevel, the work shifts from clicking through menus to designing what the agent is allowed to pull and do.
Two concrete actions. First, if you manage HubSpot portals, audit every custom assistant before July 13 and plan the move to Breeze projects, because the migration is automatic but the welcome messages and starters are not. Second, treat the MCP direction as a chance to consolidate: let one CRM agent reach G2, Gong, Linear, and Amplitude instead of bolting on disconnected point tools. And before you let any of these agents act on live client data, test them the same way you would any agent, against real cases, not a demo. That setup and governance work is exactly what our AI automation agency and automation teams handle. The deadline is the forcing function, but the MCP shift is the real story: in 2026 the CRM stops being a place you click and becomes a place an agent works on your behalf, which is exactly why what it is allowed to do has to be designed, not left to chance.
Frequently Asked Questions
Breeze Agents can now use additional MCP servers to pull context and act in G2, Linear, Gong, and Amplitude through plain-language prompts. Breeze Assistant arrived on mobile with synced history, a Create report with AI option was added, and Data Agent prompts gained required or optional token flags.
From June 19, 2026, accounts that have never created custom assistants can no longer create them. On July 13, 2026, existing custom assistants become read-only and are automatically migrated to Breeze projects, though welcome messages and conversation starters must be moved manually.
Audit every custom assistant before July 13 and plan the Breeze projects migration, since the move is automatic but the welcome messages and conversation starters are not. Then use the MCP direction to consolidate context from tools like Gong and Amplitude into one governed CRM agent.
No. Whether a client runs HubSpot or GoHighLevel, the CRM's AI is becoming an agent that operates other tools through MCP, the same standard reshaping outbound and automation stacks. The skill shifts from clicking menus to designing and testing what an agent is allowed to pull and do.