Skip to content
Book a build

HubSpot MCP vs the Claude connector: what's the difference?

The Claude connector is HubSpot's ready-made integration inside Claude's web and desktop apps: click Connect, approve, and chat. The HubSpot MCP server is the general route for any MCP client, such as Claude Code, Cursor or your own agent, and needs an MCP connector you create in HubSpot for OAuth credentials. As of October 2026 they expose largely the same kinds of tools; the difference is setup and client.

On this page

What HubSpot supports natively

HubSpot connector for ClaudeRemote HubSpot MCP server
Works inClaude web and desktopAny MCP client with OAuth and PKCE: Claude Code, Cursor, custom agents
SetupClaude Settings → Connectors → HubSpot → ConnectCreate an MCP connector under Development → MCP Connectors, then configure the client
CredentialsHandled for youClient ID, client secret and redirect URL from the MCP connector
ApprovalSuper Admin approves for non-admins and picks data permissionsThe connecting user authorizes; scopes follow the tools and their permissions
RequirementsAny HubSpot plan; paid Claude plan (Pro, Max, Team, Enterprise)An account slot: 100 project-based apps, service keys and MCP connectors combined
AccountsOne HubSpot account per Claude accountChosen when you sign in
Best forPeople working in chatDevelopers, 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

  1. You live in Claude’s chat app: use the connector. It’s the shortest path and the admin controls are built in.
  2. You work in Claude Code or Cursor: use the MCP server. Add it with your connector’s client ID and secret, then authenticate with /mcp in Claude Code.
  3. 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.
  4. 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

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

AI, Claude & MCP

Related questions.

HubSpot MCP vs the Claude connector: what's the difference?

The Claude connector is HubSpot's ready-made integration inside Claude's web and desktop apps: click Connect, approve, and chat. The HubSpot MCP server is the general route for any MCP client, such as Claude Code, Cursor or your own agent, and needs an MCP connector you create in HubSpot for OAuth credentials. As of October 2026 they expose largely the same kinds of tools; the difference is setup and client.

Does the Claude connector use the HubSpot MCP server?

HubSpot's documentation doesn't say. When we checked in October 2026, most tool names the Claude connector exposes (for example manage_custom_properties and manage_custom_pipelines) matched tools HubSpot documents for its remote MCP server, but not all: the connector also exposed manage_saved_reports, query_segments, show_feedback_form and import-claude-design-from-url, which the MCP reference doesn't list. Treat the overlap as an observation, not a guarantee.

Which one should an agency use?

The connector for day-to-day chat in one client portal at a time (it connects one HubSpot account per Claude account). The MCP server when you need scripted or repeatable access from Claude Code or another client.

Can admins restrict who connects Claude to HubSpot?

Yes. A Super Admin approves the connector and chooses who can install it. HubSpot also notes that Claude Enterprise admins can restrict connector access to company-provisioned accounts through verified domain restrictions.