On this page
What HubSpot supports natively
HubSpot offers three ways to connect Claude, and they’re built for different jobs (checked October 2026):
| Route | Use it from | Set up by | Good for |
|---|---|---|---|
| HubSpot connector for Claude | Claude web and desktop | Settings → Connectors in Claude | Admins and users working in chat |
Remote HubSpot MCP server (mcp.hubspot.com) | Claude Code and other MCP clients | An MCP connector you create in HubSpot | Developers and agents |
| Developer MCP server (local) | Agentic coding tools, via the HubSpot CLI | hs mcp setup | Building HubSpot apps, not configuring a portal |
The connector is available on all HubSpot products and plans. On the Claude side it needs a paid plan: Pro, Max, Team or Enterprise.
How to connect Claude to HubSpot with the connector
- In Claude, click your profile icon and open Settings, then Connectors.
- Find HubSpot and click Connect.
- Log in to HubSpot, pick the account, choose the permissions to allow and confirm.
- If you aren’t a Super Admin or a user with App Marketplace access, a Super Admin has to approve the connector first. During approval they choose the optional data permissions and who can install it.
If a Super Admin later approves more data permissions, each user has to reconnect to get them.
How to connect Claude Code to HubSpot’s MCP server
- In HubSpot, go to Development → MCP Connectors and click Create MCP connector. Add a name and a redirect URL.
- Copy the client ID and client secret from the connector’s details page.
- Add the server to Claude Code with those credentials, for example
claude mcp add --transport http --client-id <id> --client-secret --callback-port 8080 hubspot https://mcp.hubspot.com(the redirect URL you registered must match the callback). - Run
/mcpin Claude Code and complete the HubSpot login. HubSpot requires PKCE, so the client you use must support it.
Scopes come from the tools available when you install and the permissions you grant. If HubSpot adds tools later, you reinstall to grant new scopes.
Which route to pick
- You want answers and small CRM changes in chat: the connector.
- You want scripts or an agent in your terminal: the remote MCP server in Claude Code. See building HubSpot workflows with Claude Code.
- You want Claude to configure properties, pipelines and workflows: check what the HubSpot MCP can create first. Workflows aren’t covered.
- You want new setup built and deployed with review: we recommend Jetstack AI Projects rather than a connector. See how Projects compares with Claude and the HubSpot MCP.
Where Jetstack AI fits
Jetstack AI has its own MCP server at https://mcp.jetstack.ai. Add it in Claude as a custom connector, or in Claude Code with claude mcp add --transport http jetstack https://mcp.jetstack.ai/mcp, and Claude can list your portals, browse and import HubSpot assets, deploy them with a reviewed mapping and run audits, limited to the scopes on your Jetstack token. Setup for each client is in the MCP server docs; start from the developer overview.
The MCP server is for copying setup that already exists. To build new setup, use Projects: describe the properties, pipelines and workflows you need in a brief, approve the plan Jetty (the Projects assistant) writes, review the generated assets, then approve deployment separately. You get a receipt checked by reading the assets back from HubSpot, and workflows are created switched off. Projects is currently in limited release; the quickstart shows the steps.
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)
- MCP server (Jetstack AI documentation)
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