The remote HubSpot MCP server is graduating from beta and is now generally available to all HubSpot accounts. This release adds write capabilities, Activity history, marketing content objects, and organizational context — so any MCP-compatible AI tool can now read from and write to your CRM through natural conversation, with your existing HubSpot permissions respected throughout.
What's changing
The HubSpot MCP server connects any MCP-compatible AI tool to your CRM over a secure, HubSpot-hosted connection authenticated via OAuth 2.1 with PKCE. This release significantly expands what's accessible through that connection.
CRM data, organizational context, and Activity history are now available with expanded read and write capabilities, with some objects remaining read-only:
Read access:
- CRM records: contacts, companies, deals, tickets, line items, quotes, invoices, orders, carts, products, subscriptions, and segments (lists)
- Marketing and content: campaigns, landing pages, blog posts, site pages, and marketing events
- Activities: calls, meetings, notes, tasks, and emails — so you can query full Activity history alongside CRM records (for example, summarize the last three calls with a prospect or review recent email activity).
Create/update access:
- CRM records: contacts, companies, deals, tickets, line items, and products
- Activities: calls, meetings, notes, tasks, and emails — so your AI tool can not only summarize past activity but also log new calls, create follow-up tasks, schedule meetings, and draft or log emails directly from the conversation.
A few things to keep in mind:
- OAuth 2.1 with PKCE is required for all connections.
- If your HubSpot account has sensitive data turned on, Activity objects (calls, emails, meetings, notes, and tasks) will be blocked from access through the MCP server. This restriction is specific to the MCP server and doesn't apply to the standard CRM APIs.
- All actions respect your existing HubSpot user permissions — users can only access or modify records they already have permission to view or edit.
If you already have the MCP server installed, your app may show a REQUIRES_REAUTHORIZATION status for newly added object types. To access the new scopes, disconnect and reconnect the app through your settings. You can check which objects and tools are available for your account by calling the get_user_details tool at the start of a session.
New to the MCP server? Getting connected takes three steps:
- Create an MCP auth app. In your HubSpot account, go to Development > MCP Auth Apps and create a new app. HubSpot generates OAuth credentials automatically.
- Create a managed OAuth connection. Connect any MCP client that supports OAuth with PKCE to
https://mcp.hubspot.comusing your app's client ID and secret. - Start prompting. Your AI tool can now query, create, and update HubSpot data using natural language.
For full setup instructions, including available tools and troubleshooting guidance, see the remote HubSpot MCP server documentation. Note that this server is separate from the developer MCP server, which is used for building apps and CMS content locally.
When is it happening?
This change goes into effect on April 13, 2026.
Questions or comments? Join us in the developer forums.
This changelog was updated on April 15, 2026 to correct information on read/write access.