Most AI tools give you answers. Then you go act on them somewhere else.
That gap, between where the insight happens and where the work gets done, has been the defining friction of using AI in a business context. You ask Claude what your pipeline looks like. Claude tells you. You open HubSpot and update a record. The AI did the thinking; you did the manual work.
The HubSpot connector for Claude, powered by our MCP server, was built to close that gap.
Recent updates aren’t about adding features to a list. They’re about expanding how much of a team’s actual working day can happen inside a single Claude conversation, powered by real HubSpot data, with real actions taken in HubSpot at the end of it. For GTM teams, the before and after looks meaningfully different.
Here’s what that looks like in practice.
For sales: From signal to sent, in one session
Before these updates, a rep starting their day in Claude could ask about open deals and get a useful summary. What they couldn’t do was turn that summary into a working session without bouncing between tools.
Now they can.
With intent signals, a rep can open Claude and ask it to look across every account they own, pull the signals detected in the last seven days (research activity, job changes, news, visitor behavior), and return a ranked shortlist of who to reach out to today. That’s the prioritization sorted.
In the same conversation, they can ask Claude to draft a personalized email for each account, informed by that contact’s full engagement history in HubSpot: every email, call, note, and deal interaction on record.
When a conversation results in an action (a follow-up to schedule, a deal stage to update, a note to log), Claude can do that for you, too. No tab-switch. The record in HubSpot updates. Every write is attributed in the Audit Log. The rep’s day moves forward without the workflow ever breaking.
The full session: surface the right accounts, understand why they matter right now, write the outreach, take the action. Previously, that required a dashboard, a spreadsheet, a CRM, and a draft. Now it’s a single, simple conversation.
For marketers: From brief to published, without opening HubSpot
Marketing’s relationship with HubSpot has always been execution-heavy. The ideas happen in one place, and the building happens in HubSpot. The analysis comes back, and the next campaign gets built in HubSpot again. It’s a constant back-and-forth that the HubSpot connector has mostly eliminated.
A marketer can now run a full campaign cycle inside Claude. Ask which campaigns drove the most pipeline last quarter, understand what those campaigns had in common, build the next one: create the campaign, associate assets, configure tracking. Draft the email, using a previous email or template as a starting point. Schedule it. Publish it. Then ask Claude how it performed.
The same is true for content. A marketer can create a new website page or landing page using an existing template, publish it, check how other published pages have been performing, make copy edits, and republish, all in conversation. Blog posts follow the same pattern: create, edit, tag, set metadata, publish, or unpublish existing posts without opening HubSpot.
For teams managing AEO, that analysis is now part of the same workflow. Check performance, review brand recommendations, monitor tracked prompts, and pair those findings with any saved HubSpot report, all without switching context.
The full session: audit what worked, build what’s next, publish it, and start measuring it. The content calendar moves forward; HubSpot stays current. No copy-paste required.
For RevOps: From analysis to configuration, in the same tool
RevOps has always straddled two modes of work: analysis and configuration. Those two modes typically live in different places, processes, and workflows.
The connector now supports both, in the same Claude conversation.
On the analysis side, any saved HubSpot report can be pulled directly into Claude for discussion and follow-up. A RevOps manager can run an analysis that previously required a manual export: pull win/loss data, run churn-risk detection against custom product usage objects, or surface which intent signal clusters are showing up most on deals that progressed to opportunity stage.
On the configuration side, that analysis can now lead directly to action. Set up a new pipeline. Define stages. Add a custom property to any object. All from Claude, without opening HubSpot’s settings. The connection between “here’s what the data is telling us” and “here’s how we adjust the system” is no longer a multi-session, multi-tool process.
Custom objects made this meaningfully more powerful. The data RevOps teams rely on most is often the data their team built: domain-specific objects, custom fields, proprietary pipeline stages. That data is now readable and writable through the connector, which means the analyses Claude can run are no longer limited to HubSpot’s default object model. Claude knows the HubSpot your team actually built.
The full session: pull the reports that matter, interrogate them conversationally, adjust the data model to reflect what you learned. One workflow, no context-switching.
For service and commerce: Managing the full customer lifecycle
Service and commerce teams work across a high volume of distinct objects (appointments, projects, deliveries, courses, orders, listings, renewals), and the overhead of managing those objects across different views inside HubSpot is real.
The connector now supports read and write access across all of them.
A service rep preparing for a call can ask Claude to pull a full communications history for a customer across every connected channel: live chat, email, WhatsApp, SMS, Facebook Messenger. They can see all upcoming appointments, book a follow-up, check the status of active deliveries, create a project from a call transcript, and enroll a contact in an onboarding course. The full service context is in one conversation before the call starts.
For commerce teams, the same principle applies to operational workflows. Query abandoned carts. Convert them to orders. Check which listings are expiring. Update listing status. Manage service renewals. These have always been possible inside HubSpot; what’s changed is that they’re now possible without navigating to HubSpot, which means they fit more naturally into whatever working context the team is already in.
What connects all of it
The through-line across all of these updates is the same: the scope of a single conversation has expanded from answering a question to completing a workflow.
Early on, the connector was powerful for lookup. You could ask about a contact, a deal, a campaign. You got useful information. But the action that followed still happened somewhere else. The manual step of carrying the insight back to HubSpot, doing the thing, and coming back was still there.
What’s changed is that the action now happens in the conversation. Write access expanded. Custom objects opened up. Configuration became possible. Intent signals, reports, AEO analysis, and content publishing all arrived. The gap between “Claude told me what to do” and “it’s done in HubSpot” got small enough that, for most daily workflows, it’s effectively closed.
Your AI tools used to advise you about HubSpot. Now they operate it.
If you already have the HubSpot connector for Claude enabled, reauthenticate to access the latest features. New to the connector? Visit the HubSpot Knowledge Base to get started.
Read the monthly HubSpot MCP server changelog to see more details about individual feature releases: July, August, and September editions available in your account notifications.