HubSpot used Unbound week to ship the biggest expansion yet of its MCP server, the connection layer that lets Claude work inside your CRM. Announced September 15, 2026, the update turns the HubSpot connector for Claude from a read-mostly assistant into a read-write operator across sales, marketing, RevOps, service, and commerce objects.
This post covers what is new, who is affected, and the governance checklist admins should run before enabling it. For background on what the MCP server is, start with our earlier explainer, HubSpot MCP Server: What AI CRM Integration Means for Your Business.
Quick Answer
The HubSpot MCP server update announced September 15, 2026 expands the HubSpot connector for Claude from looking up CRM data to completing full workflows inside a Claude conversation: drafting and publishing campaigns and content, updating pipelines and properties, and reading and writing custom objects plus service and commerce records. It matters most for HubSpot admins and RevOps leaders, because every write is now possible through an AI conversation — and HubSpot requires existing connector users to reauthenticate before the new features activate. This post helps you decide how to enable the expansion safely: what changed, what reauthentication does, and which governance questions to settle first. Vantage Point helps teams roll out AI-connected CRM workflows with the right permissions and audit controls through our HubSpot technology services.
TL;DR
- What changed: The HubSpot MCP server now supports expanded write access, custom object read/write, pipeline and property configuration, content publishing, and AEO analysis — all from inside a Claude conversation.
- Who's affected: Any HubSpot portal using the Claude connector, plus sales, marketing, RevOps, service, and commerce teams whose objects are now in scope.
- Required action: Existing connector users must reauthenticate to access the new features; new users set up through HubSpot's Knowledge Base flow.
- Governance first: Writes are attributed in HubSpot's Audit Log, but admins should decide who gets write scope and how changes are reviewed before rolling it out.
- How Vantage Point helps: We assess connector readiness, permissions, and audit processes as part of our HubSpot implementation services.
What Changed in the September 15 HubSpot MCP Server Update
HubSpot's framing is direct: your AI tools used to advise you about HubSpot; now they operate it. The expansion is organized around four teams, and each gained new reads and — the significant part — new writes.
Sales: from signal to sent in one session
A rep can now ask Claude to scan every account they own, pull intent signals detected in the last seven days (research activity, job changes, news, visitor behavior), and return a ranked shortlist of who to contact today. In the same conversation, Claude drafts personalized outreach informed by each contact's full engagement history, then takes the follow-up actions: scheduling a follow-up, updating a deal stage, logging a note. The record updates in HubSpot without the rep ever leaving the conversation.
Marketing: from brief to published without opening HubSpot
Marketers can run a full campaign cycle in Claude: ask which campaigns drove the most pipeline last quarter, build the next campaign, associate assets, and configure tracking. Claude can draft an email from a previous send or template, schedule it, and publish it. The same pattern applies to content — create a website or landing page from an existing template, publish it, edit copy, and republish. Blog posts can be created, edited, tagged, given metadata, published, or unpublished in conversation. AEO analysis is also part of the workflow: check performance, review brand recommendations, monitor tracked prompts, and pair findings with any saved HubSpot report.
RevOps: from analysis to configuration in the same tool
Any saved HubSpot report can now be pulled into Claude for discussion — win/loss analysis, churn-risk detection against custom product usage objects, or intent signal clusters on deals that reached opportunity stage. The bigger change is on the configuration side: admins can create a new pipeline, define stages, and add a custom property to any object from the conversation. Custom objects are now readable and writable through the connector, which means Claude can work with the data model your team actually built, not just HubSpot's default objects.
Service and commerce: the full customer lifecycle
The connector now has read and write access across appointments, projects, deliveries, courses, orders, listings, and renewals. A service rep can pull a customer's full communications history across live chat, email, WhatsApp, SMS, and Facebook Messenger, book a follow-up appointment, check delivery status, create a project from a call transcript, or enroll a contact in an onboarding course. Commerce teams can query abandoned carts, convert them to orders, check expiring listings, update listing status, and manage renewals.
Before and after, at a glance
| Workflow | Before September 15 | After September 15 |
|---|---|---|
| Sales outreach | Claude summarized deals; rep acted in HubSpot | Claude prioritizes accounts, drafts outreach, updates records |
| Campaigns and email | Analysis in Claude, building in HubSpot | Create, schedule, and publish campaigns and emails in conversation |
| Content | Drafting help only | Create, edit, tag, publish, and unpublish pages and posts |
| RevOps configuration | Manual work in HubSpot settings | Create pipelines, stages, and properties from Claude |
| Custom objects | Not accessible | Full read/write access |
| Service and commerce objects | Out of scope | Read/write across appointments, orders, listings, renewals, and more |
Who's Affected
Any HubSpot portal with the Claude connector enabled is affected immediately, because the new capabilities arrive with the same connector — nothing new to install. New users see the expanded scope at first setup. Practically, the change touches five roles: sales reps, marketers running campaigns and content, RevOps managers who own configuration, service and commerce teams, and the admins responsible for who is allowed to do any of this.
Why Reauthentication Is Required
HubSpot's announcement is explicit: if you already have the HubSpot connector for Claude enabled, you need to reauthenticate to access the latest features. New users follow the setup flow in the HubSpot Knowledge Base. Reauthentication is how the connector picks up the expanded permissions behind the new write capabilities — the old grant covered a narrower set of actions, and HubSpot is asking each portal to consciously approve the broader one. Treat that prompt as a decision point, not a click-through: whoever completes it is granting write access on behalf of the portal.
Governance Questions to Answer Before Enabling Write Access
The update is safe to adopt, but only deliberately. Before reauthenticating, work through these questions:
- Who completes the reauthentication? The person who reconnects the connector approves the expanded scopes. That should be an admin acting on a documented decision, not whichever power user sees the prompt first.
- Which users should have write-level access through Claude? Map connector usage to existing HubSpot roles. A rep updating deal stages is different from a marketer unpublishing blog posts or an admin creating pipelines.
- How will you review AI-driven writes? HubSpot attributes every write in the Audit Log. Decide now how often someone reviews that log and what a rollback looks like for a bad bulk change.
- What is your policy for publishing actions? Claude can now publish emails, pages, and posts. If your content has an approval step, keep it — the connector does not replace editorial review.
- Which custom objects contain sensitive data? Custom object write access is powerful and new. Identify objects with financial, contractual, or personal data and decide whether they belong in scope.
- How does this fit your broader compliance posture? If your organization already runs formal CRM change controls, extend them to AI-initiated changes. Our compliance and security solutions work often starts with exactly this mapping.
What to Do Now: Admin and RevOps Checklist
- Confirm your connector status. Check whether the HubSpot connector for Claude is already enabled and who uses it today.
- Read the September 15 announcement and the monthly changelog. HubSpot publishes July, August, and September MCP server changelog editions in account notifications; review them alongside the official announcement.
- Decide the governance answers above before anyone reauthenticates.
- Reauthenticate deliberately using the prompt in your portal, or set up fresh via the HubSpot connector for Claude setup guide.
- Pilot with one team. Sales prioritization or report analysis are lower-risk starting points than content publishing or pipeline configuration.
- Review the Audit Log weekly during the pilot. Verify that writes are attributed as expected and match what users intended.
- Expand scope in stages, adding publishing and configuration workflows only after the review habit exists.
Timeline
- September 15, 2026: HubSpot announced the MCP server expansion during Unbound week. The capabilities are live for portals that complete reauthentication.
- Effective immediately: Existing connector users see the reauthentication requirement; new users get the full scope at setup.
- Ongoing: HubSpot ships monthly MCP server changelogs (July, August, and September editions are already available in account notifications), so treat this as a continuing release train rather than a one-time event.
There is no announced end-of-life or forced migration date. The practical deadline is self-imposed: reauthenticate without a governance conversation and AI write access runs without an owner.
How Vantage Point Helps
Vantage Point implements HubSpot for organizations that want AI-connected workflows without governance surprises. For the MCP server expansion specifically, we help you audit current connector usage, map write scope to HubSpot roles, design an Audit Log review process, and sequence a safe rollout across sales, marketing, and service teams — as part of our HubSpot implementation and managed services and ongoing support work. If your team is weighing what the September 15 update means for your portal, we can assess your setup and build a practical enablement plan.
FAQ
What is the HubSpot MCP server?
The HubSpot MCP server is the connection layer that powers the HubSpot connector for Claude, letting the AI read HubSpot CRM data and, after the September 15, 2026 update, take write actions across sales, marketing, RevOps, service, and commerce objects. It is an expansion of an existing integration, not a new product.
What is new in the September 15, 2026 HubSpot MCP server update?
The update adds expanded write access, custom object read/write, pipeline and property configuration, campaign and content publishing, intent-signal prioritization for sales, saved-report and AEO analysis, and read/write for service and commerce objects such as appointments, orders, listings, deliveries, and renewals.
Do I need to reauthenticate the HubSpot connector for Claude?
Yes, if your portal already has the connector enabled. HubSpot states that existing users must reauthenticate to access the latest features, because the new capabilities require expanded permissions. New users can skip this by setting up through the HubSpot Knowledge Base flow, which grants the current scope from the start.
How do I audit what Claude changes in HubSpot?
Every write Claude makes through the connector is attributed in HubSpot's Audit Log, according to HubSpot's announcement. Admins should assign an owner to review the Audit Log regularly, especially during the first weeks after enabling write access, and define how to reverse unintended changes.
Can Claude really publish HubSpot content now?
Yes. Claude can now create, edit, tag, set metadata on, publish, and unpublish blog posts, website pages, and landing pages, plus schedule and publish marketing emails. Keep your editorial approval steps in place — the connector executes whatever the conversation instructs.
Which HubSpot objects can Claude read and write after the update?
Beyond standard CRM objects, the connector now supports custom objects with full read/write access, plus service and commerce objects: appointments, projects, deliveries, courses, orders, listings, and renewals. RevOps teams can also create pipelines, define stages, and add custom properties to any object.
Is this update safe for regulated or sensitive data?
The capabilities are permission-based and writes are logged, but safety depends on your configuration. Identify custom objects containing financial, contractual, or personal data before enabling write scope, and extend your existing CRM change controls to AI-initiated actions. A partner like Vantage Point can help map scope to your compliance requirements.
