Here's something we see constantly in portals: a team has HubSpot and Asana running side by side, but the work to bridge them falls on a human. Someone checks Asana, copies a status, pastes it into a HubSpot note, and hopes nothing slips through the cracks.
That manual bridge is exactly what Breeze Agents with MCP support are built to eliminate. And with this update, that bridge just got a lot more reliable.
What This Update Actually Is
HubSpot has updated the Asana MCP (Model Context Protocol) Server that connects Breeze Agents to your Asana workspace. This is version 2 of that integration.
MCP is the standard that lets AI agents talk to third-party tools using plain language. Instead of building a rigid point-to-point integration, MCP lets your Breeze Agent ask Asana questions and take actions there, the same way a human would describe a task.
The v2 update does three specific things:
- Narrows the tool set to the actions your team actually uses, so the agent isn't wading through a bloated list of options it'll rarely touch.
- Simplifies tool names: for example, "create_task" instead of "asana_create_task." Less noise, cleaner commands.
- Reduces context window usage so your Breeze Agent can process requests faster and fit more meaningful work into a single conversation.
This is available to all HubSpot hubs and tiers, including free.
Why HubSpot Shipped This
Breeze Agents are only as useful as the context they can reach. If your project data lives in Asana and your CRM data lives in HubSpot, an agent that can only see one of those is working blind.
But there's a second, less obvious problem. AI agents have a finite context window, which is the amount of information they can hold and reason over at once. When a tool list is long and inconsistently named, the agent burns context just figuring out what it's allowed to do. That leaves less room for the actual task.
The v1 Asana MCP Server had that problem. Long prefixes, redundant tools, inconsistent naming. Humans using the agent would sometimes see slow responses or incomplete actions because the agent was burning context on scaffolding instead of work.
Version 2 fixes that. The tool set is focused, the names are clean, and the agent can spend its context budget on your actual request.
How to Use It Step by Step
The upgrade isn't automatic. You'll need to reconnect the Asana MCP server to your Breeze Agent. Here's how:
- Go to your Breeze Agent settings inside HubSpot.
- Locate the existing Asana MCP server connection and disconnect it.
- Reconnect the Asana MCP server. This pulls in the v2 tool set.
- Once reconnected, prompt your agent: "List the available Asana tools." This confirms v2 is active and shows you exactly what actions are supported right now.
- Run a test prompt. Try asking your agent to list Asana tasks for a specific project or create a task from a HubSpot deal context.
One important note from HubSpot: don't hardcode tool names or treat the interface as permanent. The Asana MCP tool set will keep evolving based on usage and feedback. Use the tools/list MCP command regularly to fetch the latest tool definitions and avoid broken workflows down the road.
What It Touches in Your HubSpot Strategy
This update is small on the surface. Under the hood, it touches more than you might expect.
If your ops team uses Asana to manage project delivery and HubSpot to manage the client relationship, a Breeze Agent with v2 Asana MCP access can sit at that intersection. It can pull task status from Asana and surface it inside a HubSpot conversation, without a human running between tabs.
Key Takeaway
The real value isn't the Asana connection itself. It's that your Breeze Agent can now hold context from both systems at once and act on that combined picture. That's the shift from a chatbot to an actual agent.
Think about where this ripples in practice. Sales reps can ask a Breeze Agent to check whether the onboarding project in Asana is on track before a renewal call. Marketing ops can prompt an agent to create Asana tasks when a campaign milestone hits in HubSpot. Service teams can connect ticket resolution in HubSpot to task completion in Asana, without building a Zap or a custom workflow.
The context window efficiency gain also matters for complex, multi-step agent tasks. If you're building agents that need to pull data from HubSpot and Asana in the same session, a leaner tool list means the agent gets further before it runs into limits. That's the difference between an agent that finishes the job and one that stalls halfway.
If you want to understand how MCP fits into HubSpot's broader agentic vision, our deep-dive pillar on the HubSpot agentic platform covers where it's been, where it is now, and where it's heading.
Key Takeaway
If you already have the Asana MCP server connected, don't assume v2 is active. The reconnect step is required. Skipping it means your agent is still running on the old, heavier tool set.
This update pairs well with other recent Breeze improvements. For example, once your agent pulls Asana project data, you might want it to visualize that alongside HubSpot CRM data. That's now possible through Breeze Assistant's new chart-building capability, which lets humans generate data visuals from plain-language requests.
Who Should Care Most
Not everyone will feel this update on day one. Here's who will:
- RevOps and operations leaders who manage both a HubSpot portal and an Asana workspace and are tired of humans manually syncing data between them.
- HubSpot admins who are already experimenting with Breeze Agents and want a more stable, efficient Asana connection.
- Agency or services teams who use Asana for project delivery and HubSpot for client management, and want an agent that can speak both languages.
- Growing companies on any HubSpot tier who want to start using Breeze Agents for cross-tool automation without enterprise-level complexity.
If your team doesn't use Asana, this specific update won't move the needle for you today. But it's worth noting that HubSpot is building this MCP pattern across multiple tools, including Gong and G2. The Asana upgrade is a signal of where the whole ecosystem is going.
George's Take
I've been watching MCP connections closely because I think most teams are underestimating them. This isn't just a convenience feature. It's HubSpot quietly building the plumbing for a world where your Breeze Agent isn't limited to what lives in HubSpot. When the tool set is clean and efficient, agents can actually finish complex, multi-system tasks. When it's bloated, they stall. The v2 Asana update is HubSpot doing the unglamorous work of making agents actually reliable, and that's the kind of update that compounds. The teams that reconnect, test, and build habits around this now will be miles ahead when MCP support expands to more tools.
“MCP connections are HubSpot quietly building the plumbing for a world where your Breeze Agent isn't limited to what lives inside HubSpot. The v2 Asana update is the unglamorous work that makes agents actually reliable, and that kind of update compounds.”
If you're building out your Breeze Agent strategy and want to see another example of agents doing real operational work, check out how Breeze now prioritizes open invoices and drafts collection emails. It's the same principle: agents with good context doing work that humans shouldn't have to do manually.
Ready to build a Breeze Agent strategy that actually connects your tools and cuts out the manual bridgework? Book a strategy call with the Sidekick team and we'll map out exactly where agents can start making a real difference in your portal.
Frequently Asked Questions
What is the Asana MCP Server for Breeze Agents?
The Asana MCP Server is a Model Context Protocol connection that lets HubSpot Breeze Agents read and take action in your Asana workspace using plain-language prompts. Version 2 ships a smaller, faster tool set with simplified naming, so agents can work more efficiently without burning through their context window.
Do I need to do anything to get the Asana MCP Server v2?
Yes. The v2 upgrade isn't automatic. You need to disconnect the existing Asana MCP server from your Breeze Agent and reconnect it to pull in the updated tool set. Once reconnected, prompt your agent to list available Asana tools to confirm v2 is active.
What can a Breeze Agent do in Asana after the v2 update?
After reconnecting, your Breeze Agent can access Asana tasks, projects, and more using plain-language prompts. Supported actions include creating tasks, listing projects, and checking task status. Ask your agent to list available Asana tools to see the full current action set, as it continues to evolve.
Who gets access to the Asana MCP Server v2?
All HubSpot hubs and tiers, including free accounts. If you have Breeze Agents enabled and an Asana MCP connection, you can reconnect and start using v2 today.
Why did HubSpot simplify the Asana MCP tool names?
AI agents have a finite context window. A bloated or inconsistently named tool list forces the agent to use context budget on figuring out its own options instead of completing your task. Simplified names like 'create_task' instead of 'asana_create_task' reduce that overhead so agents can work faster and handle more complex requests.
Can Breeze Agents connect to tools other than Asana?
Yes. HubSpot's MCP support extends to other third-party tools including Gong and G2. Asana is one of the first to receive a v2 upgrade. The pattern HubSpot is building means more tools will get refined MCP connections over time, expanding what Breeze Agents can access and act on.
