On this page
What HubSpot supports natively
This is what each HubSpot AI route documents for configuration assets, checked October 30, 2026 against HubSpot’s Claude and ChatGPT articles (both updated October 19, 2026) and November 5, 2026 against HubSpot’s Agent CLI guide. “Not listed” means HubSpot’s article doesn’t include it.
| Asset | Breeze Assistant | Claude connector | ChatGPT app | Remote MCP server | Agent CLI (beta) |
|---|---|---|---|---|---|
| Workflows | Add triggers and actions, configure settings (Pro/Ent) | No | No | No tool | Create, update, delete from JSON |
| Custom properties | Create, through the Data agent | Read and create, not update | Read and create, not update | Create | Create, update, delete |
| Pipelines | Not listed | Read, create, update | Read, create, update | Create and manage | Create, update, delete, with stages |
| Segments (lists) | Not listed | Read, create, update | Read, create, update | Create; add or remove records in static segments | Named, no commands documented |
| Forms | Not listed | Not listed | Not listed | No tool | Named, no commands documented |
| Saved reports | Charts from your data | Read only | Read only | No tool | Create, clone, delete |
| Custom object definitions | Not listed | Records only | Records only (inconsistent in HubSpot’s article) | Records only | Create, update, delete (Admin mode) |
| Marketing emails, pages, blog posts | Content generation | Read, create, update | Read, create, update | Drafts and edits | Not listed |
| CRM records | Create (examples) | Read, create, update | Read, create, update | Read, create, update | Read, create, update, merge, delete |
| Delete | Not listed | None documented; in our testing (October 2026) its segment tool offered delete and restore | None documented | Not listed | Documented, after a --dry-run safety digest |
The Agent CLI is HubSpot’s command-line tool for AI agents such as Claude Code, Claude Cowork and Codex. It runs as the signed-in user, or in Admin mode with a service key, which HubSpot’s guide says schema changes and most deletes need.
For the remote MCP server, HubSpot’s Fall 2026 developer changelog announced more than its tool reference documents (managing custom properties, and scheduling and publishing marketing emails); the table follows the reference. To filter this by asset and action, use the HubSpot AI capability matrix.
What the matrix means in practice
- Workflows are in-app or code. Breeze edits the one workflow open in the builder. Of HubSpot’s own routes outside the app, only the Agent CLI (beta) and the Automation API (beta) create workflows, from JSON your agent writes, with the IDs and ordering left to you.
- Data model work is half-covered. You can create properties and pipelines by chat, but not fix a property later, set who can edit it, or build the forms and workflows around it.
- Batch sizes are small. Both chat connectors cap creates and updates at 10 records at a time.
- Validations can be skipped. HubSpot notes that association label validations (and for ChatGPT, pipeline stage validations) aren’t applied to writes through the connectors.
For the MCP detail, see what the HubSpot MCP can create. For choosing between the assistants, see Breeze vs Claude and ChatGPT. For building configuration, our recommendation is Jetstack AI Projects; see how it compares with Claude and the HubSpot MCP and with ChatGPT.
How to pick a route for a configuration job
| Job | Route |
|---|---|
| Tweak one workflow | Breeze Assistant in the builder |
| Add a handful of fields or a new pipeline | Claude or ChatGPT connector or MCP server, with write tools set to Needs Approval |
| Script a change from Claude Code or Codex | HubSpot’s Agent CLI, previewing every write with --dry-run |
| Build a connected setup (fields, lists, forms, workflows) | Jetstack AI Projects, or the APIs with code review |
| Copy a working setup to another portal | A dependency-aware copy tool |
Where Jetstack AI fits
Jetstack covers the rows the matrix leaves empty, and the planning none of these tools does. To go from a written brief to a built setup, see whether an AI tool can implement HubSpot from a brief. Use Projects for any configuration build: describe the properties, pipelines, lists, forms and workflows in a brief, approve the plan Jetty (the Projects assistant) writes, review the generated assets, then approve deployment separately. Properties are built before the workflows that use them, workflows are created switched off, and the receipt confirms each asset by reading it back from HubSpot. Projects is currently in limited release; what Projects can build lists every type. Portal reuse copies existing setups between portals, and you can deploy the same setup to multiple destination portals, reviewing each portal’s mappings.
Sources
- Integrate with the remote HubSpot MCP server (HubSpot Developers)
- Set up and use the HubSpot connector for Claude (HubSpot Knowledge Base)
- Connect your HubSpot account to ChatGPT (HubSpot Knowledge Base)
- HubSpot Agent CLI guide, beta (HubSpot Developers)
- Create and edit properties (HubSpot Knowledge Base)
- Build workflows using Breeze Assistant in Agent Hub (HubSpot Knowledge Base)
Checked November 5, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
AI, Claude & MCP
Turn the brief into approved HubSpot assets.
Projects plans the build against the client portal, generates the assets and deploys them only after you approve.
Explore Projects