Connecting Claude to HubSpot no longer requires building a custom API integration from scratch. With the Claude HubSpot MCP connection, Claude can securely work with supported HubSpot CRM data through HubSpot’s official Model Context Protocol infrastructure.
In this guide, you’ll learn the simplest way to connect Claude to HubSpot, what Claude can read and update, how permissions work, current limitations, and when developers should use HubSpot’s Remote MCP Server directly.
TL;DR
- HubSpot provides an official connector for Claude powered by its remote MCP infrastructure.
- For most users, the official Claude connector is easier than building a custom MCP integration.
- HubSpot permissions and the permissions approved during connection determine what Claude can access.
- Claude can read many HubSpot objects and create or update supported CRM records and activities.
- For write actions, HubSpot recommends configuring Claude’s Write tools setting to Needs Approval.
What Is MCP?
Model Context Protocol (MCP) is an open standard that allows AI applications such as Claude to securely connect to external systems, data sources, and tools through a standardized interface. Instead of building a different custom AI integration for every platform, an MCP-compatible AI client can communicate with an MCP server that exposes approved data and actions.
For HubSpot, the architecture is simple:
User → Claude → HubSpot MCP Server → HubSpot CRM → Claude Response
The MCP server acts as the controlled bridge. Claude does not need to randomly call different HubSpot APIs or know how every CRM endpoint works.
How Do Claude and HubSpot MCP Work Together?
HubSpot’s Remote MCP Server connects MCP-compatible AI tools with HubSpot CRM data. HubSpot announced the server as generally available in April 2026, with expanded read and write capabilities.
When you use the official HubSpot connector for Claude, the connection combines several pieces:
- Claude interprets your natural-language request.
- MCP provides the standard communication layer.
- HubSpot exposes supported CRM data and actions through its MCP tools.
- OAuth authenticates the connection.
- HubSpot user permissions determine which records the user is allowed to access or modify.
This is important for businesses: connecting Claude does not automatically give every user unrestricted access to the entire CRM.
How to Connect Claude to HubSpot Using MCP
The easiest approach in 2026 is to use the official HubSpot connector available in Claude’s Connectors directory. You do not need to create a HubSpot private app or manually configure the MCP endpoint for the standard connection.
HubSpot currently requires an active HubSpot user account and a paid Claude subscription: Pro, Max, Team, or Enterprise.
Step 1: Open Claude Connectors
In Claude, open Customize → Connectors or access the Connectors directory from the connector menu in a chat.
For Team and Enterprise organizations, a Claude Owner or Primary Owner may first need to enable the connector for the organization.
Step 2: Find HubSpot
Browse the available web connectors and select HubSpot. Review its capabilities and add or connect the service.
Step 3: Authenticate with HubSpot
Click Connect next to HubSpot and sign in to the HubSpot account you want Claude to use.
For the first connection in a HubSpot account, HubSpot requires either a Super Admin or a user with App Marketplace permissions to connect the connector and select the permissions it is allowed to use.
Step 4: Review Permissions
HubSpot displays the permissions requested by the Claude connector. Select the permissions appropriate for your organization and complete the connection.
A good implementation should follow least privilege: enable the capabilities your team actually needs rather than granting write access simply because it is available.
Step 5: Enable HubSpot in a Claude Conversation
After authentication, return to Claude. In a conversation, open the connector/tools menu and enable HubSpot.
Claude can then use HubSpot when your request requires CRM information or a supported CRM action.
Step 6: Configure Write Approval
For organizations allowing CRM changes, HubSpot recommends opening the HubSpot connector’s tool settings and setting Write tools → Needs Approval.
This allows Claude to prepare the action while requiring human confirmation before the CRM change is executed.
Consultant recommendation: Start with read access and one-record write tests. Once your team understands the behavior, expand write permissions only for workflows where Claude genuinely saves time.
How to Test the HubSpot Connection
Start with simple prompts where the expected result is easy to verify inside HubSpot.
- “Show me deals currently in the negotiation stage.”
- “Summarize the recent engagement history for Acme Inc.”
- “Find contacts created during the last 30 days.”
- “Create a follow-up task for this contact for next Tuesday.”
- “Show me deals that have not had activity in the last 14 days.”
For a first write test, use a single record and verify the result directly in HubSpot before attempting additional updates.
What Can Claude Access in HubSpot?
HubSpot’s current documentation lists the following capabilities for the official Claude connector. The table below reflects the documented status as of July 2026.
| HubSpot Data | Read | Create | Update |
|---|---|---|---|
| Contacts | Yes | Yes | Yes |
| Companies | Yes | Yes | Yes |
| Deals | Yes | Yes | Yes |
| Tickets | Yes | Yes | Yes |
| Line items | Yes | Yes | Yes |
| Products | Yes | Yes | Yes |
| Quotes / Quote Templates | Yes | Beta | Beta |
| Invoices, Orders, Carts | Yes | No | No |
| Payments / Payment Links | Yes | No | No |
| Subscriptions / Segments | Yes | No | No |
| Campaigns | Yes | Yes | No |
| Landing Pages | Yes | Yes | No |
| Website Pages / Blog Posts | Yes | No | No |
| Marketing Events | Yes | Yes | No |
| Calls, Meetings, Notes, Tasks, Emails | Yes | Yes | Yes |
| Users / Teams | Yes | No | No |
| Inbox / Help Desk Conversations | Yes | No | No |
Important: This table describes HubSpot’s managed Claude connector. HubSpot’s generic Remote MCP Server continues to add tools independently, so developers should check the latest Remote MCP documentation before assuming every MCP capability is surfaced identically through Claude’s managed connector.
Permissions and Security
HubSpot’s remote MCP connection uses OAuth-based authentication, and HubSpot’s GA documentation describes the remote server connection as OAuth 2.1 with PKCE. PKCE helps protect the authorization-code flow from interception.
More importantly for day-to-day CRM governance, Claude respects existing HubSpot user permissions. If a sales rep can only access specific deals in HubSpot, connecting Claude does not give that rep permission to access every other deal.
For create and update actions performed through the Claude connector, HubSpot records attribution in its Audit Log to both the user and the Claude connector.
Businesses should use a least-privilege approach:
- Enable only the required HubSpot permissions.
- Use Needs Approval for write tools where practical.
- Test changes on individual records first.
- Review HubSpot audit logs for important CRM changes.
- Avoid enabling unnecessary write capabilities for users who only need analysis.
HubSpot also states that the Claude connector cannot access custom properties classified as Sensitive Data. If Sensitive Data is enabled for the HubSpot account, engagement data such as calls, emails, meetings, notes, and tasks is blocked from the connector.
Advanced Option: Connect Directly to HubSpot’s Remote MCP Server
Most Claude users do not need this route. It is intended for developers building their own MCP client, AI application, agent, or custom integration.
HubSpot’s current developer flow is:
- Open your HubSpot account.
- Navigate to Development.
- Open MCP Auth Apps.
- Click Create MCP auth app.
- Enter the app name, description, redirect URL, and optional icon.
- HubSpot generates the OAuth client credentials.
- Configure your MCP client with the client ID, client secret, and matching redirect URL.
- Connect the client to
https://mcp.hubspot.com. - Complete the OAuth flow with PKCE and authorize the correct HubSpot account.
- Test the available tools and user permissions.
HubSpot recommends the MCP Inspector as one option for testing because it can handle the PKCE flow and display the tools available to the authenticated user.
HubSpot Remote MCP Server vs Developer MCP Server
These are separate HubSpot products and should not be confused.
| Area | Remote HubSpot MCP Server | Developer MCP Server |
|---|---|---|
| Purpose | Interact with HubSpot CRM/account data | Build and manage HubSpot development projects |
| Runs | HubSpot-hosted remote server | Locally through HubSpot CLI |
| Main Users | AI clients, business tools, custom integrations | HubSpot developers |
| Typical Use | Query or update CRM data | Create projects, CMS assets, validate code, inspect builds and deploy |
| Setup | MCP Auth App + OAuth/PKCE | hs mcp setup |
Common Claude HubSpot MCP Problems and Troubleshooting
HubSpot does not appear in Claude connectors
Confirm that you have a supported paid Claude plan. On Team or Enterprise, an Owner or Primary Owner may also need to enable HubSpot for the organization before individual users can connect it.
Claude cannot access a specific HubSpot record
Check the user’s HubSpot record permissions. The connector cannot bypass HubSpot permissions, team restrictions, or record-level access.
Claude can read data but cannot update it
The object may be read-only, the required HubSpot permission may not have been granted, or Claude’s write tools may be set to Blocked. Review both HubSpot permissions and Claude’s connector tool permissions.
New MCP capabilities are unavailable
Reconnect or reauthorize the connection. HubSpot notes that when new MCP scopes or capabilities are introduced, existing connections may need to be reinstalled or reauthenticated before the new access becomes available.
Authentication fails
For the official connector, disconnect and reconnect the HubSpot account. For a custom MCP client, verify PKCE support, the OAuth credentials, token refresh handling, and that the redirect URL exactly matches the URL configured in the HubSpot MCP Auth App.
The wrong HubSpot account is connected
Disconnect HubSpot from Claude and reconnect using the correct account. HubSpot currently documents that one Claude account can connect to only one HubSpot account at a time.
Claude cannot access activities
If Sensitive Data is enabled for your HubSpot account, HubSpot blocks engagement data from the Claude connector. This includes calls, emails, meetings, notes, and tasks.
When Should You Use Claude + HubSpot MCP?
The integration is most useful when Claude can reduce repetitive CRM analysis or turn conversational instructions into controlled CRM actions.
- Reviewing sales pipeline health.
- Finding stale or inactive opportunities.
- Summarizing a contact or company’s engagement history.
- Preparing context before sales meetings.
- Researching groups of contacts or deals.
- Creating follow-up tasks and notes.
- Updating supported CRM properties.
- Analyzing campaign or marketing data where supported.
- Reviewing support tickets and customer conversations.
For most HubSpot teams, the official Claude connector is the right starting point because it removes the need to build and maintain your own MCP client.
Current Limitations to Know
The Claude HubSpot integration is useful, but it is not a replacement for every HubSpot API or automation workflow.
- No delete operations: the Claude connector currently supports view, create, and update actions but not deletion.
- Bulk write limit: create and update requests are limited to 10 records at a time.
- Custom objects: general custom objects are not currently available through the managed connector. HubSpot separately documents read access for the Partner Client Object.
- Sensitive Data: custom Sensitive Data properties are unavailable, and enabling Sensitive Data blocks engagement access.
- User permissions still apply: Claude cannot bypass normal HubSpot access controls.
- Custom validation warning: HubSpot states that custom validation rules, including pipeline-stage and association-label validations, are not applied when records are created or updated through the connector.
- Content limitations: for website, landing page, and blog content, published content is available while drafts may provide only metadata.
- API limits apply: connector functionality remains subject to HubSpot API usage limits and guidelines.
Important for RevOps teams: The custom-validation limitation matters. If your CRM relies heavily on required stage fields or custom validation to protect data quality, test Claude-driven writes carefully before enabling them broadly.
Conclusion
Claude HubSpot MCP gives HubSpot teams a practical way to analyze CRM information and perform supported actions through natural-language conversations. In 2026, the simplest setup is the official HubSpot connector for Claude rather than a custom API or MCP implementation.
Use HubSpot’s existing permissions, keep write actions approval-based where appropriate, and start with controlled use cases such as pipeline analysis, engagement summaries, follow-up tasks, and individual CRM updates. Developers only need the direct Remote MCP Server route when building a custom MCP client, agent, or AI application around HubSpot.
Frequently Asked Questions
What is HubSpot MCP?
HubSpot MCP is HubSpot’s implementation of the Model Context Protocol for connecting compatible AI tools with HubSpot. Its Remote MCP Server provides controlled access to supported CRM records, activities, marketing information, and actions while respecting HubSpot user permissions. HubSpot also has a separate local Developer MCP Server for building HubSpot apps and CMS projects.
Can Claude connect directly to HubSpot?
Yes. Claude can connect to HubSpot through the official HubSpot connector available in Claude’s Connectors directory. The connector uses HubSpot’s MCP infrastructure to give Claude access to supported CRM information and actions. For most users, this managed connector is simpler than manually configuring HubSpot’s Remote MCP Server.
Is there an official HubSpot connector for Claude?
Yes. HubSpot provides an official HubSpot connector for Claude, and HubSpot maintains dedicated setup documentation for it. The connector supports CRM analysis as well as selected create and update actions. A paid Claude subscription such as Pro, Max, Team, or Enterprise is currently required.
Do I need to create a HubSpot private app?
No. You do not need a HubSpot private app when using the official Claude connector. Authentication is handled through the connector’s authorization flow. Developers connecting a custom MCP client directly to HubSpot instead create an MCP Auth App under HubSpot’s Development section and use its OAuth credentials.
Can Claude update HubSpot contacts and deals?
Yes. HubSpot currently documents read, create, and update support for contacts and deals through the Claude connector. Claude can also update supported properties such as contact information or deal stages, subject to the user’s HubSpot permissions and the connector’s enabled write-tool settings.
Can Claude create HubSpot records?
Yes. The Claude connector can create supported records including contacts, companies, deals, tickets, line items, and products. It can also create supported activities such as tasks, notes, meetings, calls, and emails. Creation support varies by object, so read-only objects should not be assumed to support writes.
Can Claude delete HubSpot records?
No. HubSpot’s current documentation states that the Claude connector does not support delete operations. It can view, create, and update supported data, but deletion must be performed through HubSpot or another appropriately authorized tool. This restriction provides an additional boundary around destructive CRM actions.
Is the Claude HubSpot MCP connection secure and does it respect permissions?
The connection uses authenticated HubSpot access and respects existing HubSpot user permissions. Users can only access or modify records they are allowed to work with in HubSpot. HubSpot also records supported Claude create and update actions in its Audit Log, and organizations can restrict or require approval for write tools.
Is coding required to connect Claude to HubSpot?
No coding is required for the standard HubSpot connector for Claude. Users can connect it through Claude’s Connectors interface and complete the HubSpot authentication flow. Coding and MCP Auth App configuration are only necessary when developers want to connect a custom MCP client or build their own AI integration.
What is the difference between HubSpot MCP Server and Developer MCP Server?
The Remote HubSpot MCP Server connects AI clients with actual HubSpot CRM data and supported actions. The Developer MCP Server is a separate local tool that works through the HubSpot CLI and helps developers create, validate, upload, and deploy HubSpot apps and CMS assets. They serve different purposes and should not be treated as the same server.
Can I use HubSpot MCP with Claude Desktop or Claude Code?
Yes. HubSpot documents the managed Claude connector as available on Claude web, desktop, and mobile. Anthropic’s current connector documentation also states that remote connectors can work across Claude surfaces including Claude Code. Developers can additionally configure remote MCP servers directly in Claude Code when a custom setup is required.
Quick Answer: How Do You Connect Claude to HubSpot Using MCP?
To connect Claude to HubSpot using MCP, open Claude’s Connectors settings, select the official HubSpot connector, authenticate your HubSpot account, approve the required permissions, and enable HubSpot in your conversation. Claude can then read supported CRM data and perform permitted create or update actions through HubSpot’s MCP infrastructure.
References / Sources
- HubSpot Knowledge Base — Set up and use the HubSpot connector for Claude
- HubSpot Developers — Integrate AI tools with the HubSpot MCP server
- HubSpot Developer Changelog — Remote HubSpot MCP server is now generally available
- HubSpot Developers — Set up the Developer MCP server
- Anthropic — Use connectors to extend Claude’s capabilities
- Anthropic — When to use desktop and web connectors
- Model Context Protocol — Introduction to MCP
- Model Context Protocol — Authorization specification
Leave a Reply