Skip to content
Book a build

Claude HubSpot integration: the three routes, set up and compared

Claude HubSpot integration compared: HubSpot's Claude connector, its MCP server and the Jetstack AI MCP server, with setup steps and what each can change.

Jetstack AI / Working guides

The Claude connection

Pick the right route

Route comparison
Route 1HubSpot's Claude connectorRecords, some setup · in claude.ai
Route 2HubSpot's remote MCP serverClaude Code and other clients
Route 3Jetstack AI MCP serverBrowse, import and deploy setup
To build new setupJetstack AI ProjectsPlan → approve → deploy → receipt
On this page

Updated October 29, 2026. Checked against HubSpot’s Knowledge Base, HubSpot’s developer docs and the live connector on that date.

There are three ways to connect Claude to HubSpot, and they do different jobs. HubSpot’s Claude connector and HubSpot’s remote MCP server work on records, some CRM settings and marketing content. The Jetstack AI MCP server works on portal setup: browsing it, copying it between portals and auditing it. None of the three builds new HubSpot workflows from a prompt.

How does the Claude HubSpot integration work?

Claude talks to HubSpot through the Model Context Protocol (MCP): a server exposes tools, and Claude calls them with your permission. Which server you connect decides what Claude can do. HubSpot runs two of them (a hosted one for portal data and a local one for app developers), and Jetstack AI runs a third for portal setup.

RouteUse it fromWhat it works onSet up in
HubSpot connector for ClaudeClaude on web, desktop and mobileCRM records, activities, pipelines, properties, segments, marketing contentClaude: Settings → Connectors
Remote HubSpot MCP server (mcp.hubspot.com)Claude Code, Cursor and other MCP clientsThe same kinds of data, through 32 documented toolsHubSpot: Development → MCP Connectors
Jetstack AI MCP server (mcp.jetstack.ai)Claude, Claude Code, ChatGPT, CursorPortal setup: browse, import, deploy to other portals, auditsJetstack app: Settings → Access Tokens

HubSpot also has a local developer MCP server, installed with hs mcp setup in the HubSpot CLI. It helps coding tools build HubSpot apps. It doesn’t configure a portal, so it isn’t covered here.

1. Set up HubSpot’s Claude connector

This is the shortest route if you work in Claude’s chat app. HubSpot lists it on all HubSpot products and plans. On the Claude side you need a paid plan: Pro, Max, Team or Enterprise.

  1. In Claude, click your profile icon, then open Settings → Connectors.
  2. Click Browse, select HubSpot, then Connect.
  3. Log in to HubSpot, choose the account and select the permissions to allow.
  4. Click Connect app. In a chat, turn the connector on from + → Connectors.

Super Admins and users with App Marketplace access can connect straight away. Everyone else needs a Super Admin to approve the connector first, and that Super Admin picks its optional data permissions and who can install it. When a Super Admin later approves more data permissions, each user has to reconnect to get them.

Only one HubSpot account can be connected to a Claude account at a time. Agencies switch client portals by disconnecting and reconnecting.

2. Set up HubSpot’s remote MCP server

Use this route for Claude Code, Cursor or an agent of your own. HubSpot hosts the server at https://mcp.hubspot.com, and your client signs in with OAuth. PKCE is required.

  1. In HubSpot, go to Development → MCP Connectors and click Create MCP connector.
  2. Enter a name and a redirect URL. For Claude Code, use http://localhost:8080/callback.
  3. Copy the client ID and client secret from the connector’s details page.
  4. Add the server to Claude Code:
Terminal window
claude mcp add --transport http \
--client-id <your-client-id> --client-secret --callback-port 8080 \
hubspot https://mcp.hubspot.com
  1. Claude Code prompts for the secret. Start Claude Code, run /mcp, select hubspot and complete the HubSpot login.

You don’t pick scopes directly. They come from the tools available when you install and the permissions you grant, and every action respects the connecting user’s HubSpot permissions. When HubSpot adds tools, users reinstall to grant the new scopes.

3. Set up the Jetstack AI MCP server

Use this route when the job is portal setup rather than records: finding the workflows, forms, lists and properties in a portal, copying them to another portal with their dependencies, or running an audit.

  1. In the Jetstack app, go to Settings → Access Tokens and create a token. Pick only the scopes the assistant needs. The token starts with jsai_ and is shown once.
  2. In Claude, open Settings → Connectors, choose Add custom connector, name it Jetstack AI and enter https://mcp.jetstack.ai. In Claude Code, run claude mcp add --transport http jetstack https://mcp.jetstack.ai/mcp, then /mcp and Authenticate.
  3. On the Jetstack sign-in page, enter default as the Instance ID (or your dedicated instance’s ID) and paste the token.

Your token is never shown to the assistant: the client holds a session Jetstack issues, which lasts 30 days. Revoking the token ends access. Setup for ChatGPT, Cursor and other clients is in the MCP server docs.

What each route can read and change in HubSpot

HubSpot documents its connector and its MCP server in two places, and they mostly agree. This table follows HubSpot’s connector article and MCP tool reference as of October 29, 2026.

AssetHubSpot connector for ClaudeRemote HubSpot MCP serverJetstack AI MCP server
CRM records and activitiesRead, create and update, up to 10 records at a timeRead, create and update; SQL-style queries for counts and trendsDoesn’t read or change records
PropertiesRead and create. HubSpot lists no update, so a wrong option value is fixed by handRead and create custom properties. Editing isn’t documentedBrowse, import, and deploy to another portal; a same-named property in the target is reused, never overwritten
Pipelines and stagesRead, create and updateCreate and manage. Free accounts can edit only the default pipelineBrowse, import, and deploy with stage mapping
WorkflowsNot supported. HubSpot says Claude drafts the workflow for you to buildNo workflow toolBrowse, draw as a diagram, and copy to another portal, switched off
FormsNot listedNo forms toolBrowse, import and deploy
Lists (segments)Read, create and updateCreate static and dynamic segments; add or remove records in static onesBrowse, import and deploy
Marketing emailsRead, create and updateRead; create and edit draftsBrowse, and copy as drafts
Custom objectsRecords only; object definitions aren’t listedRecords, plus schema discovery. Creating object definitions isn’t documentedBrowse; created in the target before the assets that use them

Deletes. HubSpot’s connector article lists no delete actions for any object, and its MCP reference documents no delete tool. When we checked the live connector on October 29, 2026, though, its segment tool offered to delete and restore lists. Don’t assume nothing can be removed.

Announced but not yet in the reference. HubSpot’s Fall 2026 developer changelog says the MCP server can “create and manage” custom properties and schedule and publish marketing emails. The tool reference still describes creating properties and editing drafts, so test those actions in a sandbox before you rely on them.

Some HubSpot tools have their own conditions: AEO tools need Marketing Hub Professional or Enterprise, quotes need Revenue Hub Professional or Enterprise (beta), and the website page and blog post tools are only for select AI clients (Claude, ChatGPT and Gemini).

Tiers, plans and permissions

HubSpot connector for ClaudeRemote HubSpot MCP serverJetstack AI MCP server
HubSpot planAll products and plansAny account; some tools need Professional or EnterpriseAny portal connected to your Jetstack AI organization
ClientPaid Claude plan: Pro, Max, Team or EnterpriseAny MCP client that supports OAuth with PKCEClaude (custom connector), Claude Code, ChatGPT (developer mode), Cursor, others
Who approvesSuper Admin, for anyone without App Marketplace accessThe connecting user authorizesWhoever creates the Jetstack token picks its scopes
Acts asThe connected HubSpot userThe connected HubSpot userThe token’s scopes, never more than its creator
AccountsOne HubSpot account per Claude accountChosen when you sign inEvery portal connected to your organization

On Jetstack’s side, the Read-only preset lists portals, library assets, tasks and audits but can’t browse HubSpot. The Operator preset adds browsing, importing, deploying and audits. The scope that deploys Projects work, projects:deploy, is never part of a preset; you add it on purpose.

Safety: scopes, approvals and what gets logged

Write access through any of these routes is a permission you’re handing to a model. These are the controls each one gives you, and the gaps they leave.

  • Approvals before writes. HubSpot’s write tools tell Claude to summarize the change and wait for a yes. HubSpot recommends setting the connector’s write tools to Needs Approval in Claude; on Always allow, edits can happen without a prompt. When we checked, the tools also let a user waive confirmations for the rest of a chat. Don’t do that on a production portal.
  • Permissions. Claude sees and changes only what the connected HubSpot user can. Connect with a dedicated, least-privilege user where you can, not a Super Admin.
  • Batch size. The connector creates or updates at most 10 records at a time. That limits the damage, but 10 wrong lifecycle stages still trigger every workflow that watches the property.
  • Skipped validations. HubSpot says association label validations aren’t applied to records the connector creates or updates.
  • Audit Log. Creates and updates show in HubSpot’s Audit Log under both the user and the connector, and Super Admins can see who connected it and when.
  • Sensitive Data. With Sensitive Data turned on, the connector can’t reach engagement data and the MCP server blocks activity and conversation data. Custom Sensitive Data properties are never available.
  • Jetstack tokens. Create a separate token for each assistant so you can tell which one made a change and revoke one without the others. Keep your client’s tool-approval prompts on: import, deploy and audit tools start real work, and deploys write to the target portal.

Can Claude build HubSpot workflows?

Not through HubSpot’s connector or its MCP server. Neither has a workflow tool, and HubSpot’s connector FAQ says Claude drafts the workflow for you to build in HubSpot. Claude can build workflows only by going around them:

RouteBuilds workflows?What you take on
HubSpot connector for ClaudeNoYou build Claude’s draft by hand
Remote HubSpot MCP serverNoNo workflow tool is documented
Claude Code calling HubSpot’s Automation API (beta)YesA credential with the automation scope, the portal’s real IDs, and the update rule: anything left out of an update is removed. Deleted workflows can’t be restored through the API
Jetstack AI MCP serverCopies existing onesIt moves a workflow that already exists to another portal, switched off. It doesn’t write new ones

Even when Claude can write a workflow, a working workflow needs more than the workflow. The properties, lists and emails it references have to exist first, with the right internal values, and someone has to check what HubSpot actually saved.

That’s why we recommend Jetstack AI Projects for building HubSpot setup. You describe the work in a brief and chat. Jetty, the Projects assistant, turns it into a plan you review, and approving the plan starts generation. You review the generated assets and approve deployment separately. A Project is bound to one portal and builds in dependency order: properties before the workflows that use them. Workflows are created switched off, and some assets go live through the Chrome extension. After the run, you get a receipt of what was created, checked by reading it back from HubSpot.

Projects can change only assets it built. For a workflow built elsewhere, it builds a corrected replacement, created switched off, and you retire the old one in HubSpot. It doesn’t build CMS pages, themes or custom-code actions, and it doesn’t import data, manage users or set up integrations. Projects is currently in limited release. See what Projects can build, Projects, and how it compares with Claude and the HubSpot MCP.

What HubSpot does natively, and what Jetstack AI adds

JobHubSpot’s Claude connector and MCP serverJetstack AI
Answer questions about recordsYes, with SQL-style queriesNot its job
Create or update recordsYes, 10 at a time, after you confirmNo
Create a property or pipelineYesYes, in a Project, together with what uses it
Build a workflow, form or lead scoreNoYes, in a Project (workflows switched off)
Copy setup to another portal with its dependenciesNoYes, with a mapping you review, to one portal or many
Audit a portal’s setupNoYes, over MCP or in the app
Proof of what landedAudit Log entriesA receipt read back from HubSpot

Questions people ask

Is the HubSpot connector for Claude free?

HubSpot doesn’t list a separate price, and it’s available on all HubSpot plans. You need a paid Claude plan, and the connector’s activity counts against HubSpot’s API usage limits.

Does the Claude connector run on HubSpot’s MCP server?

HubSpot doesn’t say so in its connector article. When we checked on October 29, 2026, most of the connector’s tool names matched tools in HubSpot’s MCP reference, and that reference names Claude, ChatGPT and Gemini as the clients some tools are limited to. Treat the overlap as an observation and check each article for the tool you need.

Can I use more than one route at once?

Yes. A common setup is HubSpot’s connector for questions and record updates, and the Jetstack AI MCP server for browsing, copying and auditing setup. Use Projects when something new has to be built. For the wider picture, including ChatGPT and Breeze, read what Claude, ChatGPT and Breeze can configure in HubSpot.

Before you let Claude write to HubSpot

A reading checklist. Selections stay on this page only and are not saved.

Sources

The implementation workflow

Pick the right route.

The right route for the job, with writes kept behind approvals.

Explore Projects