Claude to HubSpot: Connect Claude and Build Your Website
"Claude to HubSpot" usually means one of two things. Either you want Claude to work inside HubSpot: look up deals, summarise campaigns, draft emails, update records. Or you've built something with Claude, in Claude Design, Claude Code or a chat, and it needs to become a HubSpot website your marketing team can run.
This guide covers both: first how to connect Claude to HubSpot and what the connector can do, then the routes from a Claude build to a HubSpot theme.
Part 1: Connect Claude to HubSpot
HubSpot has two official ways to connect to Claude, for two different jobs.
The HubSpot connector for Claude (for everyone)
HubSpot launched its connector for Claude in July 2025, the first CRM connector for Claude. It has grown a lot since. According to HubSpot's documentation, last updated in September 2026, Claude can now read and write:
- CRM records: contacts, companies, deals, tickets and custom objects
- Marketing emails, landing pages, blog posts and website pages
- Calls, meetings, notes, tasks and emails
- Products, quotes, invoices and orders
What you need: a paid Claude plan (Pro, Max, Team or Enterprise) and a HubSpot account on any tier, including the free CRM. A Super Admin has to approve the connector and choose which data it can access.
How to set it up: in Claude, open Settings → Connectors, find HubSpot, add it and connect your account.
Limits worth knowing: bulk changes are capped at 10 records per operation, Claude can't delete anything, and sensitive data stays out of reach. Every action is logged in HubSpot's audit log under both the user and the connector. HubSpot recommends setting write tools to ask for approval before they run, and we agree.
The developer MCP server (for developers)
For building on HubSpot, there's a separate, local developer MCP server, generally available since February 2026. You install it through the HubSpot CLI with hs mcp setup, and it gives Claude Code tools to create and manage CMS themes, templates and modules, plus apps and serverless functions.
That's the connection a developer uses to build a HubSpot theme with Claude Code. It still expects someone who knows HubL, HubSpot's templating language, to review the result.
Part 2: Turn a Claude build into a HubSpot website
Whether you designed a site in Claude Design, had Claude Code build a frontend or got a page in a chat, the result is code: HTML, CSS and JavaScript. A HubSpot website runs on a theme: templates, modules your marketing team can add, move and edit in the drag-and-drop editor, a shared header and footer, a blog and forms.
There are three routes from one to the other.
1. Import a single page with the connector
The HubSpot connector can import a design from Claude Design as a new HubSpot landing page. It takes the design as one self-contained HTML file and creates the page, and re-importing the same project updates that page instead of creating a copy. The same import also handles emails, social graphics and blog layouts.
Good for: a campaign landing page, fast.
The catch: you get one imported page, not a website. There are no reusable modules shared across pages, no common header and footer, and no blog templates. Changing the design later means changing it in Claude Design and importing again.
2. Build a theme with Claude Code and the HubSpot CLI
How: hand the project to Claude Code, connect the HubSpot developer MCP server, and have Claude Code write a theme: HubL templates, modules with fields, a theme.json and CSS. Upload and test it with the HubSpot CLI. We describe this refinement loop in migrating to HubSpot CMS with AI and Claude Code.
Good for: HubSpot developers who want full control.
The catch: someone has to know HubL and review every module. Getting the fields right, so marketers can actually edit a section without breaking it, is the slow part. Each iteration also uses your Claude allowance.
3. Convert it into a native HubSpot theme with transjt
This is the route we built transjt for: a design or a repository goes in, and a native HubSpot theme comes out, with real HubL modules your marketing team edits in the drag-and-drop editor.
From Claude Code or Claude Design:
- If you started in Claude Design, hand the project to Claude Code.
- Ask Claude Code to build the frontend in React with Vite, without server-side rendering. That's the one constraint that matters for conversion, and Claude Code follows it if you say so up front.
- Push the project to a GitHub repository.
- Connect the repository to transjt, choose HubSpot and review the preview.
Through Figma: if your team reviews designs in Figma, bring the design there first, with Claude Code and Figma's MCP server or an HTML import tool such as html.to.design, and export it with the transjt Figma plugin to HubSpot.
What you get:
- A native HubSpot theme with HubL modules your marketing team rearranges without a developer.
- Text, images and section order that change in the HubSpot editor.
- A native blog and native forms.
- Desktop, tablet and mobile layouts included.
- Ready within a few hours, not weeks.
Good for: agencies and marketing teams who want a whole website in HubSpot, not a single page.
The catch: it's a paid product. You can start free and see the preview before you pay; see pricing for the current plans.
The three routes compared
| Connector import | Claude Code + HubSpot CLI | transjt | |
|---|---|---|---|
| Result | One landing page (or email, blog layout) | A custom theme | A native HubSpot theme |
| Effort | Minutes | Days | A few hours |
| Skills needed | None | HubL and HubSpot CMS development | None |
| Reusable modules | No | Yes, if you build them | Yes |
| Header, footer, blog | No | Yes, if you build them | Yes |
| Best for | One campaign page | Developers who want control | A whole site your team edits |
Status as of September 2026.
Which route should you pick?
- One campaign page, fast: import it with the connector.
- You're a HubSpot developer: build the theme with Claude Code and the developer MCP server.
- A team will run the whole site in HubSpot: convert it into a native theme with transjt.
Once the site is live, keep the connector: Claude can then help with the CRM, emails and content on the site you just built.
On WordPress instead? Read Claude to WordPress for the connection options and routes to a native WordPress theme.
Frequently asked questions
Yes. The official HubSpot connector for Claude works with every HubSpot tier, including the free CRM, and needs a paid Claude plan. A Super Admin approves it and decides which data Claude can access.
According to HubSpot's documentation, Claude can read and write CRM records, marketing emails, landing pages, blog posts and website pages, and log calls, notes and tasks. It can't delete records, and bulk changes are limited to 10 records at a time.
Yes, as a single page. The HubSpot connector imports a Claude Design as a new landing page, email or blog layout. For a whole website with reusable modules, you need a HubSpot theme.
It depends on the route. An imported page is built from one HTML file and doesn't give you reusable modules. A theme built by Claude Code is as editable as its modules are. A theme from transjt comes with HubL modules your team edits and rearranges in the drag-and-drop editor.
Yes. WordPress has its own connection options, and the same Claude Code and Figma routes lead to a native WordPress theme with transjt.