Skip to content
Book a build

Can the HubSpot MCP create properties, pipelines and workflows?

Partly. As of October 2026 the HubSpot MCP server can create custom properties and create and manage pipelines, but it can't edit existing properties or create workflows: HubSpot documents no workflow tool. It can also create and update CRM records, create segments, and draft emails and pages. For workflows, use HubSpot's workflow builder, its beta Agent CLI or Automation API, or a build tool such as Jetstack AI Projects.

On this page

What HubSpot supports natively

Here is what HubSpot’s remote MCP server documents for each configuration asset, checked October 2026:

AssetReadCreateEditTool
Custom propertiesYesYesNot documentedsearch_properties, get_properties, manage_custom_properties
Pipelines and stagesYesYesYes (“create and manage”)manage_custom_pipelines
WorkflowsNoNoNoNone
Segments (lists)YesYesAdd or remove records in static segmentsmanage_segment
FormsNoNoNoNone
Custom object definitionsDiscover onlyNot documentedNot documenteddiscover_hubspot_schema
CRM records and activitiesYesYesYesmanage_crm_objects
Marketing emailsYesDraftsDraftsmanage_marketing_email

HubSpot’s Fall 2026 developer changelog says agents can “create and manage” custom properties and schedule and publish marketing emails, while the tool reference above describes creating properties and email drafts only. Test edits and sends before you rely on them.

So yes, the HubSpot MCP server takes write actions, but on records, properties, pipelines, segments and content. It does not touch automation.

What the property and pipeline tools actually accept

The property tool takes a label, internal name, type, field type, group and, for dropdowns, a list of options, for one or more object types at once. Its published description limits types to string, bool, enumeration, date, datetime, number, currency, email and URL, so calculated, rollup and file properties aren’t covered.

The pipeline tool creates pipelines with their stages. Deal stages need a win probability; ticket stages need at least one open and one closed state. Free accounts can’t create custom pipelines but can edit the default pipeline.

Both tools return a per-item result, so one property can fail while the rest succeed. Read the results, not the assistant’s summary.

How to get workflows built when the MCP can’t

  1. In HubSpot: Breeze Assistant in the workflow builder can add triggers and actions from a prompt (Professional and Enterprise).
  2. Through the API or the Agent CLI: the v4 Automation API (beta) creates, updates and deletes workflows, and HubSpot’s Agent CLI (beta since June 2026) gives Claude Code, Claude Cowork and Codex the same workflow commands from a JSON definition, with a --dry-run preview. See building HubSpot workflows with Claude Code.
  3. With Jetstack AI Projects, which we recommend for new builds: it creates the workflow together with the properties and lists it depends on, from a plan you approve. See how Projects compares with Claude and the HubSpot MCP.

Whichever you use, create the properties and lists first, then the workflow that references them. To compare every AI route for one asset, see the HubSpot AI capability matrix.

Where Jetstack AI fits

Use Jetstack’s Projects for the parts the MCP can’t build. Write a brief such as “a Partner deal pipeline, a Partner tier dropdown with Gold, Silver and Bronze, and a workflow that creates a follow-up task for the owner of each new Partner deal”. Jetty, the Projects assistant, turns it into a plan you approve, generates properties (including calculated and rollup properties), pipelines, lists, forms and workflows in dependency order, and deploys them after a separate approval. Workflows are created switched off, and the receipt confirms each asset by reading it back from HubSpot. Projects is currently in limited release; the full list is in what Projects can build. Jetstack’s own MCP server can also copy existing workflows between portals with their dependencies, using a mapping you review before deploying.

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

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

AI, Claude & MCP

Related questions.

Can the HubSpot MCP create properties, pipelines and workflows?

Partly. As of October 2026 the HubSpot MCP server can create custom properties and create and manage pipelines, but it can't edit existing properties or create workflows: HubSpot documents no workflow tool. It can also create and update CRM records, create segments, and draft emails and pages. For workflows, use HubSpot's workflow builder, its beta Agent CLI or Automation API, or a build tool such as Jetstack AI Projects.

Does the HubSpot MCP server ask before it writes?

The write tools' descriptions, as HubSpot publishes them to MCP clients, tell the assistant to show the proposed change and get explicit approval first. A user can waive confirmations for a session, so don't rely on the assistant alone on a production portal.

Can the HubSpot MCP edit a property's dropdown options?

Not with a documented tool. HubSpot describes the property tool as creating custom properties; editing existing ones isn't mentioned, and HubSpot's Claude connector article says properties can be created but not updated. HubSpot's Fall 2026 changelog announced creating and managing custom properties, so test it in a sandbox before relying on it.

Can it create a deal pipeline on a free HubSpot account?

No. Accounts with free tools can't create custom pipelines, but the tool can edit the default pipeline instead.