On this page
What HubSpot supports natively
| HubSpot connector for Claude | Remote HubSpot MCP server | |
|---|---|---|
| Works in | Claude web and desktop | Any MCP client with OAuth and PKCE: Claude Code, Cursor, custom agents |
| Setup | Claude Settings → Connectors → HubSpot → Connect | Create an MCP connector under Development → MCP Connectors, then configure the client |
| Credentials | Handled for you | Client ID, client secret and redirect URL from the MCP connector |
| Approval | Super Admin approves for non-admins and picks data permissions | The connecting user authorizes; scopes follow the tools and their permissions |
| Requirements | Any HubSpot plan; paid Claude plan (Pro, Max, Team, Enterprise) | An account slot: 100 project-based apps, service keys and MCP connectors combined |
| Accounts | One HubSpot account per Claude account | Chosen when you sign in |
| Best for | People working in chat | Developers, scripts, agents |
Both act within the connecting user’s HubSpot permissions, and both block engagement data when Sensitive Data is on.
What each can change
HubSpot documents capabilities in two places, and they line up closely as of October 2026: create custom properties (not edit them), create and manage pipelines, create and update CRM records and activities, create segments, and work on marketing emails, pages and blog posts. They aren’t identical: the connector has also exposed tools the MCP reference doesn’t list, such as manage_saved_reports and query_segments. Neither documents a workflow or forms tool, and HubSpot’s connector article lists no delete actions. HubSpot’s Fall 2026 developer changelog announced more for the MCP server than its reference documents (managing custom properties, and scheduling and publishing marketing emails); the reference still describes creating properties and editing email drafts. To build workflows and the setup around them, we recommend Jetstack AI Projects; see how it compares with Claude and the HubSpot MCP. The details are in what the HubSpot MCP can create and what the Claude connector can do.
How to choose between HubSpot MCP and the Claude connector
- You live in Claude’s chat app: use the connector. It’s the shortest path and the admin controls are built in.
- You work in Claude Code or Cursor: use the MCP server. Add it with your connector’s client ID and secret, then authenticate with
/mcpin Claude Code. - You’re building an agent for your team: use the MCP server with a dedicated HubSpot user, so its permissions and Audit Log entries are separate from any person’s.
- You need to switch portals often: the connector holds one HubSpot account at a time, so you disconnect and reconnect; with the MCP server you pick the account when you authorize.
Where Jetstack AI fits
Jetstack AI’s MCP server is a third, separate option. It connects to the same clients (Claude as a custom connector, Claude Code, ChatGPT, Cursor) and works on portal setup across your connected portals: browsing workflows, lists, forms and properties, importing them with dependencies, deploying with a reviewed mapping, and running audits. See the MCP server docs and the developer overview.
For building new setup rather than copying it, use Projects: describe the properties, pipelines and workflows in a brief, approve the plan, then approve deployment separately. Workflows are created switched off, and the receipt confirms each asset by reading it back from HubSpot. Projects is currently in limited release; see the quickstart.
Sources
- Set up and use the HubSpot connector for Claude (HubSpot Knowledge Base)
- Integrate with the remote HubSpot MCP server (HubSpot Developers)
- Connect Claude Code to tools via MCP (Claude Code docs)
Checked October 29, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
AI, Claude & MCP
Do it from your own code or AI agent.
The Jetstack AI REST API, MCP server and CLI share API keys and scopes. Create and manage those keys in the app.
Read the developer docs