What This Update Actually Is
HubSpot has added G2 as a supported MCP Server inside Breeze Studio. MCP stands for Model Context Protocol. It's an open standard that lets AI agents pull live data from external systems without custom code or a data engineering project.
Once connected, your Breeze Agents can access three G2 data streams:
- Buyer Intent: identifies which companies are actively researching specific products right now, so your reps know who's in-market before outreach.
- Review Analysis: surfaces verified customer language and competitive sentiment from G2 reviews, so reps can mirror the words real buyers use.
- Product and Category Intelligence: retrieves product listings, category data, and competitor comparison activity with advanced filtering, so you can see exactly who a prospect is stacking you against.
This is different from the existing G2 app for HubSpot, which pushed static data into the CRM. The MCP connection gives Breeze Agents access to real-time signals inside a live agent workflow.
Why HubSpot Shipped This
Here's the real problem this solves. Reps have always gone into outreach conversations without knowing what a prospect actually cares about. They'd guess at the right message or wait on a data analyst to pull intent reports. By the time the signal arrived, the buying window had often moved on.
That delay creates a quieter internal frustration too. Reps know they're leaving relevance on the table. They know a better-timed, better-framed message would land differently. But the workflow to get that context was too slow or too fragmented to be practical.
HubSpot's answer is to put the signal at the moment of action, inside the agent workflow, so the research and the outreach happen in the same motion. This fits the broader pattern HubSpot is building: Breeze Agents as the connective tissue between CRM context and live third-party data.
How to Use It Step by Step
You'll need Breeze Studio permissions to do this. The G2 connection uses an OAuth-based flow, which is the standard authorization method for most MCP Servers in HubSpot.
Connect G2 to your Breeze Agent:
- In HubSpot, navigate to Breeze, then open Breeze Studio.
- Go to the Agents tab and click the name of the agent you want to configure.
- Click Configure next to the agent name.
- In the What this agent can do section, click Add tool.
- Click the MCP Servers tab in the right panel.
- Scroll to find the G2 MCP listing, then click Connect and add.
- In the pop-up, click Connect to G2 MCP and log in to your G2 account.
Add custom instructions for better output:
- Return to Configure for the same agent.
- Scroll to Extra instructions.
- Type your instructions. Be specific. Tell the agent which products to track, which competitors to watch, and what language to surface from reviews.
Run the agent:
- In Breeze Studio, click Open on the configured agent.
- Enter the account or prospect information you want the agent to research.
- Click Run agent. The agent will pull live G2 data and surface it alongside your CRM context.
One practical note: the Knowledge Base confirms that each MCP Server has its own configuration requirements. Review G2's documentation for any specific setup steps on their side before connecting.
What It Touches in Your HubSpot Strategy
This update lives inside Breeze Studio, but its ripple effects touch your entire sales motion. Let's walk through where this shows up.
Sales Hub and Prospecting Workflows
Reps can run a G2-connected agent against any account in their pipeline before outreach. The agent surfaces which products the prospect is researching, which competitors they're evaluating, and what language real buyers use in reviews. That context flows directly into the conversation prep without switching tabs or waiting on reports.
Key Takeaway
The biggest practical win here is re-engagement timing. When an account that went cold shows renewed G2 activity, a Breeze Agent can flag it before your rep would ever catch it manually. That's pipeline recovery on autopilot.
RevOps and Prioritization Logic
For RevOps, this changes how you score and prioritize accounts. Right now, most teams use CRM activity data and lead scores built from form fills and email opens. G2 intent adds a third-party behavioral signal that's independent of what the prospect has done inside your own funnel.
Pair this with tools like Notetaker with Smart Deal Progression and you start building a sales motion where both pre-call research and post-call CRM updates are handled by AI. That's meaningful time returned to your reps.
Competitive Intelligence Across the Portal
The Product and Category Intelligence stream gives your team a running view of how G2 visitors compare you to competitors. This isn't just useful for reps. Marketing teams can use this to identify which competitor comparisons to build content around. RevOps can track shifts in competitive pressure over time.
Key Takeaway
G2 review language pulled through this connection is verified buyer voice. Using it in outreach messaging means your emails and calls reflect the exact words real buyers use when they describe problems you solve. That's not a small thing.
If you're thinking about where G2 intent fits inside a broader account-based strategy, our article on the B2B customer journey in 2026 covers how dark funnel signals like this are reshaping how smart teams build buyer maps.
MCP Ecosystem in Breeze Studio
G2 joins Notion, Atlassian, Asana, Zapier, Linear, Gong, and Amplitude as supported MCP Servers in Breeze Studio. The pattern here matters. HubSpot is positioning Breeze Studio as the orchestration layer for AI workflows across your entire stack. The more MCP Servers connect, the more context your agents carry.
For teams that want to push this even further, the HubSpot Agent CLI opens another layer, letting AI agents run scheduled and bulk tasks against your CRM data outside the browser entirely.
Who Should Care Most
Not every team will get equal value from this on day one. Here's where the biggest impact lands.
- B2B SaaS sales teams that compete in crowded G2 categories: this is purpose-built for you. Your prospects are already on G2 comparing you. Now you can see it.
- RevOps and sales ops leaders who manage pipeline prioritization: G2 intent gives you a third-party signal that sits outside your own tracking bias.
- Account-based marketing teams running re-engagement plays: the ability to detect when a dormant account returns to market is the exact trigger most ABM plays are missing.
- Smaller sales teams without dedicated data or market intelligence functions: this removes the gap between wanting intent data and having the resources to operationalize it.
One honest caveat: the value here is proportional to your G2 presence. If your category is thin on G2 or your product doesn't have meaningful review volume, the review analysis stream won't give you much to work with yet. Build that review base first.
George's Take
I've been inside enough HubSpot portals to know that most sales teams have intent data somewhere and CRM context somewhere else, and the gap between those two places costs them deals they never even knew they lost. What I like about this update is that it's not asking humans to be the bridge anymore. The agent does that. But here's the thing I keep reminding teams: the instruction layer matters enormously. A Breeze Agent connected to G2 with no custom instructions is like handing a rep a firehose and calling it a briefing. Spend time on those Extra instructions. Tell the agent exactly what to look for, which competitors matter, and what output format your reps can actually act on. That's where this goes from interesting to powerful.
“Intent data without instruction is just noise. The real leverage isn't connecting G2 to your Breeze Agent. It's telling that agent precisely what to do with what it finds.”
If you're on HubSpot Professional or Enterprise and you're not sure how to build Breeze Agent workflows that actually change your sales motion, that's exactly what we help with at Sidekick Strategies. Book a strategy call and we'll show you how to connect tools like this to a repeatable system that helps your humans flourish.
Frequently Asked Questions
What is the G2 MCP for HubSpot?
The G2 MCP for HubSpot connects Breeze Agents in Breeze Studio to live G2 data, including buyer intent signals, verified review analysis, and competitor comparison activity. It uses the Model Context Protocol (MCP) so agents can access real-time G2 data without custom code or a data engineering project.
Who can use the G2 MCP for HubSpot?
Breeze Studio Agents are available on HubSpot Professional and Enterprise subscriptions. G2 Buyer Intent data requires a G2 Professional or Enterprise subscription with the Buyer Intent add-on. Both subscriptions must be active to use the full feature set.
How do I connect the G2 MCP to a Breeze Agent?
Navigate to Breeze Studio, open the agent you want to configure, click Configure, then Add tool in the What this agent can do section. Select the MCP Servers tab, find the G2 listing, and click Connect and add. You'll authorize the connection using your G2 account credentials through an OAuth flow.
What's the difference between the G2 MCP and the existing G2 app for HubSpot?
The existing G2 app pushes data into HubSpot CRM as a static integration. The G2 MCP gives Breeze Agents access to real-time signals, including live buyer intent and current competitor research activity. The MCP connection works inside active agent workflows, not just as a data display in the CRM.
Can the G2 MCP help with re-engaging cold accounts?
Yes. One of the three G2 data streams is Buyer Intent, which identifies when accounts return to active research on G2. A Breeze Agent connected to this stream can flag accounts that go back in-market, giving sales teams a timely, behavior-based trigger for re-engagement instead of relying on manual monitoring.
Does the G2 MCP work with other Breeze Studio integrations?
Yes. G2 is one of eight MCP Servers now supported in Breeze Studio, alongside Notion, Atlassian, Asana, Zapier, Linear, Gong, and Amplitude. You can connect multiple MCP Servers to the same agent, letting it pull context from several systems in a single workflow run.
