@iamsamuelfraga/mcp-hubspot
This server provides comprehensive MCP access to HubSpot CRM through 37–53 tools, enabling management of CRM objects, associations, properties, workflows, automation callbacks, and more.
CRM Object Management
CRUD & batch operations: Create, read, update, archive, and upsert deals, line items, products, quotes, calls, meetings, tasks, notes, and emails — up to 100 records per batch call
Smart search: Filter groups, multiple operators (EQ, NEQ, LT, GT, BETWEEN, IN, etc.), multi-field sorting, and cursor pagination
Sales Tools
Merge duplicate deals — absorb a secondary deal into a primary (irreversible)
Assemble quotes — create a HubSpot Quote and associate it to a deal and line items in one call
Association Management
Create, archive, and list associations between any two CRM object types (v4 API)
Batch-create up to 100 association pairs in a single request
Discover valid association label types between object pairs
Custom Properties
List all properties for any CRM object type (standard + custom)
Get specific property definitions (type, field type, options, etc.)
Create custom properties with various types (text, number, date, enumeration, boolean, etc.)
Workflow Automation (v4 BETA)
List, get, create, update, and delete automation workflows
Batch read multiple workflows by ID
Retrieve associated email campaigns and performance metrics
Map legacy v3 workflow IDs to v4 flow IDs
Automation Callbacks
Complete single or batch async custom-action callbacks, reporting execution state (SUCCESS, FAIL_CONTINUE, or BLOCK)
Contact Enrollment (v2)
Enroll or unenroll contacts in workflows by email
Retrieve all active enrollments for a contact by HubSpot VID
Legacy Workflows (v3)
Read-only access to list and get existing v3 workflow definitions
Custom Workflow Actions (requires developer API key + App ID)
16 additional tools to manage custom action definitions, revisions, functions, and requires-object settings
Resources & Prompts
Static reference resources for HubSpot scopes, CRM object types, and usage conventions
Guided prompts for common multi-step operations (e.g., creating deals with line items, enrolling contacts)
Provides comprehensive tools for managing HubSpot CRM, including CRUD operations on contacts, companies, deals, tickets, quotes, line items, and engagements; batch operations; smart search with filters and pagination; association management; custom property definitions; workflow automation (v4 BETA and v3 legacy); enrollment management; and delayed workflow callbacks.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@iamsamuelfraga/mcp-hubspot list all deals won this month"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@nubiia/mcp-hubspot
The most complete HubSpot MCP server for Claude.
A Model Context Protocol (MCP) server that gives Claude comprehensive, enterprise-grade access to HubSpot CRM — covering contacts, companies, deals, tickets, quotes, owners, pipelines, custom object schemas, engagements, workflows, and more, all through 56 battle-tested tools (72 with a developer key).
Built and maintained by Nubiia — automatización e integraciones con IA para negocios (MCP, HubSpot, Pipedrive, Holded y más). ¿Quieres algo así para tu empresa? Escríbenos en nubiia.es.
Features
56 Tools Across 10 Toolsets (+ 16 with developer key = 72 total) — complete coverage of the HubSpot CRM API surface
Workflow Automation v4 BETA — create, update, monitor, and delete automation workflows
Contact Enrollment — enroll and unenroll any CRM object in a workflow
CRM Object CRUD — full create/read/update/archive for contacts, companies, deals, tickets, quotes, line_items, notes, calls, emails, meetings, and tasks
Batch Operations — up to 100 objects per call for efficient bulk reads and writes
Smart & Guided Search — filter groups with operators and sorting, plus guided helpers: by property, recent (created/modified since), full-text keyword (
search_text), and by association (search_by_association) — with optional auto-pagination and sensible default propertiesRobust Date Handling — ISO dates, datetimes, and epoch seconds/ms are normalized to the epoch-ms (midnight-UTC) values HubSpot requires, avoiding off-by-one and rejected-timestamp errors
Owner Resolution — translate
hubspot_owner_idvalues into real users (name, email)Pipelines & Stages — translate
dealstage/ ticket stage IDs into readable stage labelsCustom Object Schemas — define, inspect, update, and delete custom object types
Engagement Logging — log a note/call/email/meeting/task and associate it to records in one call
Deal & Quote Assembly — merge duplicate deals, assemble quotes from existing deals
Association Management — link any two CRM objects with typed association labels
Properties & Groups — discover, create, update, and archive property definitions and property groups
Rate Limiting + Retry Logic — automatic backoff to protect your HubSpot API quota
MCP Resources — three static reference resources (scope guide, object type catalog, conventions)
MCP Prompts — five guided workflows to orchestrate multi-step CRM operations
Toolset Filtering — enable only the domains you need via
HUBSPOT_TOOLSETSFull TypeScript — strict types, Zod validation, and comprehensive TSDoc
Related MCP server: hubspot-mcp
Tool Categories
Domain | Tools | Description |
CRM | 15 | Generic CRUD and batch for all object types, advanced search, plus guided search: by property, recent, full-text ( |
Sales | 2 | Deal merging and quote assembly |
Engagements | 1 | Log a note/call/email/meeting/task and associate it to records in one call |
Associations | 5 | Create, archive, list, and batch-create object associations |
Properties | 7 | List, get, create, update, archive properties + list/create property groups |
Owners | 2 | Resolve |
Pipelines | 3 | Resolve pipeline and stage IDs to readable stages (list / get / get stages) |
Schemas | 5 | Manage custom object type definitions (list / get / create / update / delete) |
Workflows v4 BETA | 9 | Create, update, delete, and monitor automation workflows |
Automation | 2 | Complete delayed workflow callbacks (single and batch) |
Enrollment | 5 | Enroll/unenroll objects in workflows; v3 legacy reads ¹ |
Actions (dev key) | 16 | Custom Workflow Action definitions — requires |
¹ The v3 legacy tools (
hubspot_workflows_v3_list,hubspot_workflows_v3_get) belong to theautomationtoolset — activate them withHUBSPOT_TOOLSETS=automation.² Actions tools use developer API key auth (hapikey) instead of a Private App access token and are only registered when
HUBSPOT_DEVELOPER_API_KEYis present. See Actions Toolset below.
Installation
Global install
npm install -g @nubiia/mcp-hubspotVia npx (no install needed)
npx @nubiia/mcp-hubspotConfiguration
Prerequisites
You need a HubSpot Private App to obtain an access token:
Log in to HubSpot and go to Settings → Integrations → Private Apps
Click Create a Private App
Give it a name and select the required scopes (see table below)
Click Create app and copy the generated access token (
pat-na1-...)
Claude Desktop Setup
Add the server to your Claude Desktop config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json
{
"mcpServers": {
"hubspot": {
"command": "npx",
"args": ["-y", "@nubiia/mcp-hubspot"],
"env": {
"HUBSPOT_ACCESS_TOKEN": "pat-na1-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}
}
}
}Environment Variables
Variable | Required | Default | Description |
| Yes | — | HubSpot Private App access token ( |
| No | all | Comma-separated domains to enable: |
| No |
| Logging level: |
Required Scopes
Grant only the scopes your use-case needs:
Toolset | Required Scopes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Advanced Configuration Examples
Enable only sales and properties toolsets:
{
"mcpServers": {
"hubspot": {
"command": "npx",
"args": ["-y", "@nubiia/mcp-hubspot"],
"env": {
"HUBSPOT_ACCESS_TOKEN": "pat-na1-...",
"HUBSPOT_TOOLSETS": "sales,properties"
}
}
}
}Enable debug logging for troubleshooting:
{
"env": {
"HUBSPOT_ACCESS_TOKEN": "pat-na1-...",
"LOG_LEVEL": "debug"
}
}Usage Examples
Create a deal and attach products
"Create a deal named 'Acme Corp - Enterprise Plan' closing on March 31st, add a line item for the Enterprise annual plan at $24,000, and associate it with the contact john.doe@acme.com."
Claude will:
Search for the contact by email using
hubspot_crm_searchCreate the deal with
hubspot_crm_create(objectType: deals)Create the line item with
hubspot_crm_create(objectType: lineItems)Link them with
hubspot_associations_createAssociate the contact with
hubspot_associations_create
Find all deals closing this month above $10k
"Search for all open deals with a close date in the current month and amount greater than $10,000. Sort by amount descending."
Claude will:
Use
hubspot_crm_searchwith filterGroups combiningclosedateBETWEEN andamountGT operatorsSet sorts to
[{ propertyName: "amount", direction: "DESCENDING" }]Paginate through results using the
aftercursor if there are more than one page
Enroll a contact who just filled a form in the onboarding workflow
"The contact with ID 98765 just submitted the trial sign-up form. Enroll them in the onboarding workflow."
Claude will:
Use
hubspot_workflows_listto find the onboarding workflow (filtering by objectTypeId for contacts)Verify the contact exists with
hubspot_crm_getEnroll with
hubspot_enrollment_enrollConfirm enrollment with
hubspot_enrollment_get_enrollments
Workflows v4 BETA
The workflows toolset uses HubSpot's Workflows v4 API, which is currently in BETA:
Breaking changes may occur without notice
Access requires explicit approval from HubSpot — contact HubSpot support if you receive 403 errors
The following tools are included in the
workflowstoolset:hubspot_workflows_list,hubspot_workflows_get,hubspot_workflows_create,hubspot_workflows_update,hubspot_workflows_delete,hubspot_workflows_batch_read,hubspot_workflows_email_campaigns,hubspot_workflows_performance,hubspot_workflows_id_mappings
For stable, read-only access to existing workflows, use the legacy v3 tools included in the automation toolset:
hubspot_workflows_v3_list— list all workflowshubspot_workflows_v3_get— get a specific workflow by ID
Actions Toolset (Phase 7)
The actions toolset exposes 16 tools for managing Custom Workflow Action definitions — the
reusable action types that developers can publish to the HubSpot Workflows editor.
Required environment variables
Variable | Required | Description |
| Yes (for actions) | HubSpot developer API key — obtain from your developer account at developers.hubspot.com |
| Yes (for actions) | The HubSpot App ID that owns the action definitions |
Activation
Actions tools are only registered when HUBSPOT_DEVELOPER_API_KEY is present. They do not
appear in the tool list when only HUBSPOT_ACCESS_TOKEN is configured. You can also explicitly
enable them via HUBSPOT_TOOLSETS=actions (still requires the developer key).
Authentication
All 16 hubspot_actions_* tools authenticate via hapikey (developer API key appended to the
query string), not the Private App bearer token used by the other 37 tools.
Tools
Tool | Description |
| List all custom action definitions for an app |
| Create a new action definition |
| Get a single action definition |
| Update (PATCH) an action definition |
| Delete an action definition |
| List all revisions for an action |
| Get a specific revision |
| List all functions on an action |
| Get a function by type |
| Create or replace a function by type |
| Delete a function by type |
| Get a function by type and ID |
| Replace a function by type and ID |
| Delete a function by type and ID |
| Get the requires-object setting for an action |
| Set the requires-object setting for an action |
Claude Desktop configuration example
{
"mcpServers": {
"hubspot": {
"command": "npx",
"args": ["-y", "@nubiia/mcp-hubspot"],
"env": {
"HUBSPOT_ACCESS_TOKEN": "pat-na1-...",
"HUBSPOT_DEVELOPER_API_KEY": "your-developer-api-key",
"HUBSPOT_APP_ID": "123456"
}
}
}
}Known Limitations
Search latency: Records created or updated via the API may take 1–5 minutes to appear in
hubspot_crm_searchresults due to HubSpot's indexing pipelineBatch cap: All
hubspot_crm_batch_*tools enforce a hard limit of 100 objects per call; split larger sets across multiple callsWorkflows v4 API: Subject to breaking changes while in BETA; HubSpot support approval required for access
Quote assembly:
hubspot_quotes_assemblerequires the deal to have at least one associated line item; the call will fail otherwise
MCP Resources
Three static reference resources are available to LLM clients:
URI | Name | Description |
| HubSpot Private App Scopes Guide | Required OAuth scopes per toolset/domain |
| CRM Object Types Catalog | Supported objectType values and key properties |
| HubSpot MCP Usage Conventions | Rate limits, batch caps, search latency, pagination |
MCP Prompts
Five guided workflow prompts help orchestrate multi-step operations:
Prompt | Description |
| Create a Deal and attach Line Items from HubSpot Products |
| Assemble a HubSpot Quote from an existing Deal |
| Log a CRM engagement (call, email, or meeting) and associate it with contacts/deals |
| Enroll a contact (or other object) in a HubSpot Workflow |
| Search CRM records with filters, sort, and pagination |
Contributing
See CONTRIBUTING.md for development setup, code style guidelines, testing requirements, and how to add new tools.
Security
See SECURITY.md for the vulnerability reporting policy and security best practices.
About Nubiia
This MCP server is built and maintained by Nubiia.
Nubiia ayuda a empresas a automatizar procesos e integrar sus herramientas con IA: servidores MCP a medida, integraciones con CRMs y ERPs (HubSpot, Pipedrive, Holded), y agentes que conectan tus datos de negocio con asistentes como Claude. Este @nubiia/mcp-hubspot es un ejemplo open source de lo que hacemos.
👉 ¿Quieres una integración o automatización con IA para tu negocio? nubiia.es · ✉️ hola@nubiia.es
Author
Built by Nubiia — nubiia.es · hola@nubiia.es
Maintainer: Samuel Fraga — GitHub
Links
License
MIT — Copyright (c) 2025 Samuel Fraga
Available Tools
37 toolshubspot_associations_archiveA
Remove all associations between two HubSpot CRM objects (v4 API). This deletes the relationship link — it does NOT delete the objects themselves. To remove only a specific labeled association, use the batch archive endpoint instead.
Inputs: toId (required), fromId (required), toType (required), fromType (required).
hubspot_associations_batch_createA
Batch-create associations between multiple HubSpot object pairs in a single request (v4 API). More efficient than individual creates when linking many records at once. Maximum 100 pairs per request. Use this to associate a set of calls with their respective contacts after bulk import, or to link multiple deals to a single company.
Default HUBSPOT_DEFINED typeIds (verify via hubspot_associations_labels_list): Call: Contact 194 | Company 182 | Deal 206 | Ticket 220 Email: Contact 198 | Company 186 | Deal 210 | Ticket 224 Meeting: Contact 200 | Company 188 | Deal 212 | Ticket 226 Note: Contact 202 | Company 190 | Deal 214 | Ticket 228 Task: Contact 204 | Company 192 | Deal 216 | Ticket 230
Inputs: inputs (required), toType (required), fromType (required).
hubspot_associations_createC
Create or update an association between two HubSpot CRM objects using the v4 API. Use this to link a call/meeting/note/task/email to a contact, company, deal, or ticket, or to link any two objects with a labeled relationship.
Default HUBSPOT_DEFINED typeIds (verify via hubspot_associations_labels_list): Call: Contact 194 | Company 182 | Deal 206 | Ticket 220 Email: Contact 198 | Company 186 | Deal 210 | Ticket 224 Meeting: Contact 200 | Company 188 | Deal 212 | Ticket 226 Note: Contact 202 | Company 190 | Deal 214 | Ticket 228 Task: Contact 204 | Company 192 | Deal 216 | Ticket 230
Inputs: toId (required), fromId (required), toType (required), fromType (required), +1 more.
hubspot_associations_labels_listA
List all available association label types between two HubSpot object types (v4 API). Use this BEFORE creating associations to discover valid associationTypeId values for your portal. Association typeIds can differ between HubSpot portals — always verify in runtime rather than hardcoding.
Example: call this with fromType="calls", toType="contacts" to see all labeled association types available for linking calls to contacts, including their typeIds and categories.
Inputs: toType (required), fromType (required).
hubspot_associations_listA
List all associated records of a given type for a specific HubSpot object (v4 API). For example, retrieve all contacts associated with a deal, or all deals linked to a call. Returns { results, total, pagination: { nextCursor } | null }. Use pagination.nextCursor as the "after" parameter to fetch subsequent pages.
Inputs: fromId (required), toType (required), fromType (required), after, +1 more.
hubspot_automation_callback_completeA
Complete a single async custom-action callback in a HubSpot Workflow (v4 automation runtime). Called after your external action finishes. Set hs_execution_state to SUCCESS to continue, FAIL_CONTINUE to continue despite failure, or BLOCK to stop enrollment at this step.
Inputs: callbackId (required), outputFields (required).
hubspot_automation_callback_complete_batchA
Complete multiple async custom-action callbacks in bulk (HubSpot Automation v4). Useful when your external system processed several workflow enrollments concurrently. Each item in callbackInputs must include its own callbackId and hs_execution_state.
Inputs: callbackInputs (required).
hubspot_crm_archiveA
Archive (soft-delete) a HubSpot CRM record. Archived records are not permanently deleted and can be retrieved with archived=true on list/get calls. Applies to all object types. Returns an empty response (HTTP 204) on success. To permanently delete, use the HubSpot UI or the GDPR delete endpoint.
Inputs: id (required), objectType (required).
hubspot_crm_batch_archiveA
Archive (soft-delete) up to 100 HubSpot CRM records in a single request. Applies to all object types. Archived records are not permanently deleted and can be retrieved with archived=true. Returns an empty response (HTTP 204) on success. LIMIT: Maximum 100 inputs per request.
Inputs: inputs (required), objectType (required).
hubspot_crm_batch_createA
Create up to 100 HubSpot CRM records in a single request. Applies to all object types. Each input requires a properties map and may optionally include inline associations. For engagements, each record must include hs_timestamp in its properties. Returns a batch response with created records and any per-record errors. LIMIT: Maximum 100 inputs per request.
Inputs: inputs (required), objectType (required).
hubspot_crm_batch_readA
Read up to 100 HubSpot CRM records by ID in a single request. Applies to all object types. Specify properties to control which fields are returned. Optionally use idProperty to look up records by a custom unique property value (e.g., your own external system ID) instead of the HubSpot hs_object_id. Returns a batch response with found records and any per-record errors. LIMIT: Maximum 100 inputs per request.
Inputs: inputs (required), objectType (required), idProperty, properties, +1 more.
hubspot_crm_batch_updateA
Update up to 100 existing HubSpot CRM records in a single request. Applies to all object types. Each input must include the record id and the properties to change (partial update — omitted properties are unchanged). Pass "" as a property value to clear it. Returns a batch response with updated records and any per-record errors. LIMIT: Maximum 100 inputs per request.
Inputs: inputs (required), objectType (required).
hubspot_crm_batch_upsertA
Upsert up to 100 HubSpot CRM records: creates them if they do not exist, updates them if they do. Each input must include idProperty (the unique property name used for matching, e.g., "email" or a custom external ID property), id (the value of that property), and properties (fields to set). The idProperty must be marked as unique in HubSpot. LIMIT: Maximum 100 inputs per request.
Inputs: inputs (required), objectType (required).
hubspot_crm_createA
Create a new HubSpot CRM record (deal, line item, product, quote, call, meeting, task, note, or email engagement). Required properties vary by type — for engagements, hs_timestamp (epoch ms string) is mandatory. For deals, dealname is required. For tasks, hs_task_subject is required. Optionally associate the new record to existing objects inline via the associations parameter (avoids a separate association API call). Returns the created record with its HubSpot-assigned id.
Inputs: objectType (required), properties (required), associations.
hubspot_crm_getA
Retrieve a single HubSpot CRM record by its ID. Works with all object types. IMPORTANT: Specify the properties parameter to get non-default property values (e.g., "dealname,amount,closedate"). Returns 404 if the record does not exist or is archived (use archived=true to fetch archived records).
Inputs: id (required), objectType (required), archived, properties, +1 more.
hubspot_crm_listA
List HubSpot CRM records of any object type (deals, line_items, products, quotes, calls, meetings, tasks, notes, emails). Returns a paginated collection with shape { results, total, pagination: { nextCursor } | null }. IMPORTANT: HubSpot returns only default properties unless you specify them explicitly via the properties parameter (e.g., "dealname,amount,closedate"). Use pagination.nextCursor from the response as the after parameter to page through large result sets.
Inputs: objectType (required), after, limit, archived, +2 more.
hubspot_crm_searchA
Search HubSpot CRM records using filters, sorts, and full-text query. Applies to all object types. Supports up to 5 filter groups (OR-ed) with up to 6 filters per group (AND-ed). IMPORTANT NOTES: (1) Search has stricter rate limits (~5 req/s per token) than regular reads — avoid polling. (2) Search has an indexing latency of several seconds — do NOT use immediately after create/update. Use hubspot_crm_get instead for read-after-write. (3) Max total results via paging: 10 000. (4) Specify properties explicitly — HubSpot returns only defaults otherwise. Returns matching records with their requested properties.
Inputs: objectType (required), after, limit, query, +3 more.
hubspot_crm_updateA
Update an existing HubSpot CRM record (partial update — only provided properties are changed). Applies to all object types. Pass only the properties you want to modify; omitted properties are left unchanged. To clear a property, pass an empty string "" as the value. Returns the updated record.
Inputs: id (required), objectType (required), properties (required).
hubspot_deals_mergeA
Merge two HubSpot deal records into one. The secondary deal is absorbed into the primary: all associated contacts, companies, activities, and line items are moved to the primary deal. Properties from the secondary deal fill in any blanks on the primary (primary values take precedence on conflicts). The secondary deal is then archived. This operation is IRREVERSIBLE — confirm the deal IDs before calling. Required scopes: crm.objects.deals.write.
Inputs: objectIdToMerge (required), primaryObjectId (required).
hubspot_enrollment_enrollA
Enroll a contact into a HubSpot Workflow (Automation v2). The contact must exist in HubSpot. Use the workflow's numeric ID and the contact's email address.
Inputs: email (required), workflowId (required).
hubspot_enrollment_get_enrollmentsA
Get all active workflow enrollments for a contact by their HubSpot VID (contact record ID). Returns the list of workflows the contact is currently enrolled in.
Inputs: vid (required).
hubspot_enrollment_unenrollA
Unenroll a contact from a HubSpot Workflow (Automation v2). Stops the contact from progressing through remaining workflow actions.
Inputs: email (required), workflowId (required).
hubspot_properties_createA
Create a new custom property (field) on a HubSpot CRM object type. Use this to extend deal, contact, company, or other object records with business-specific data fields.
Common type+fieldType combinations: Single-line text: type="string", fieldType="text" Multi-line text: type="string", fieldType="textarea" Number: type="number", fieldType="number" Date: type="date", fieldType="date" Dropdown: type="enumeration", fieldType="select" (requires options) Checkbox list: type="enumeration", fieldType="checkbox" (requires options) Yes/No toggle: type="bool", fieldType="booleancheckbox"
Note: property names must be lowercase with underscores (e.g., "my_custom_field"). The name cannot be changed after creation.
Inputs: name (required), type (required), label (required), fieldType (required), +8 more.
hubspot_properties_getA
Retrieve the full definition of a specific HubSpot CRM property by its internal name. Returns the property type, field type, group, options (for enumeration fields), and whether it is a HubSpot default or custom property. Useful for inspecting field constraints before creating or updating records.
Inputs: objectType (required), propertyName (required).
hubspot_properties_listA
List all properties (fields) defined for a HubSpot CRM object type. Returns both default HubSpot properties and custom properties created by your team. Use this to discover available property names before reading or writing record data.
Standard object types: "contacts", "companies", "deals", "tickets", "products", "line_items", "quotes", "calls", "meetings", "tasks", "notes", "emails". Custom objects use their numeric object type ID.
Inputs: objectType (required), archived.
hubspot_quotes_assembleA
Create a HubSpot Quote and associate it to a deal and line items in a single operation. This is a high-level helper that wraps the standard quote create endpoint with inline associations, saving multiple separate API calls. PREREQUISITES: The deal and all line items must already exist. Create line items first with: hubspot_crm_create objectType="line_items". ASSOCIATION TYPE IDs: Uses HUBSPOT_DEFINED typeId 64 (Quote→Deal) and 67 (Quote→LineItem) by default. Override with dealAssociationTypeId / lineItemAssociationTypeId if your portal uses different IDs. Verify IDs with hubspot_associations_labels_list for fromType=quotes. Required scopes: crm.objects.quotes.write.
Inputs: title (required), dealId (required), lineItemIds (required), locale, +13 more.
hubspot_workflows_batch_readA
[BETA] Read multiple automation workflows (flows) by their IDs in a single API call. More efficient than multiple individual hubspot_workflows_get calls when fetching several flows at once. Maximum 100 flow IDs per request. Requires the "automation" OAuth scope.
Inputs: flowIds (required).
hubspot_workflows_createA
[BETA] Create a new automation workflow (flow) in HubSpot Automation v4 API. The "name" and "type" fields are required. All other fields are optional and can be configured after creation using hubspot_workflows_update. Complex fields like enrollmentCriteria use recursive filter branch structures — see the HubSpot Automation v4 BETA documentation for the full schema. Requires the "automation" OAuth scope.
Inputs: name (required), type (required), actions, flowType, +3 more.
hubspot_workflows_deleteA
[BETA] WARNING: IRREVERSIBLE. Delete an automation workflow (flow) from HubSpot. The workflow CANNOT be recovered after deletion via the API. Consider disabling the flow (isEnabled: false) instead if you may need it later. Use hubspot_workflows_get to confirm the flow ID before proceeding. Requires the "automation" OAuth scope.
Inputs: flowId (required).
hubspot_workflows_email_campaignsA
[BETA] Get the email marketing campaigns associated with a specific automation workflow (flow) in HubSpot Automation v4 API. Returns campaign data linked to Send Email actions within the flow. Requires the "automation" OAuth scope.
Inputs: flowId (required).
hubspot_workflows_getA
[BETA] Get a single automation workflow (flow) by its ID from HubSpot Automation v4 API. Returns the full flow definition including actions, enrollment criteria, and settings. Requires the "automation" OAuth scope.
Inputs: flowId (required).
hubspot_workflows_id_mappingsA
[BETA] Map legacy HubSpot Workflows v3 integer IDs to the new Automation v4 flow string IDs. Use this when migrating from the deprecated v3 Workflows API to the v4 Flows API, or when you have stored references to v3 workflow IDs and need the corresponding v4 IDs. Returns a mapping of legacyWorkflowId → v4 flowId. Requires the "automation" OAuth scope.
Inputs: workflowIds (required).
hubspot_workflows_listA
[BETA] List automation workflows (flows) from HubSpot Automation v4 API. Returns a paginated list of all flows in the portal with shape { results, total, pagination: { nextCursor } | null }. Use pagination.nextCursor from the response as the "after" parameter to fetch subsequent pages. Requires the "automation" OAuth scope.
Inputs: after, limit.
hubspot_workflows_performanceA
[BETA] Get performance metrics for a specific automation workflow (flow) from HubSpot Automation v4 API. Returns enrollment counts, action completion rates, and other performance statistics. Requires the "automation" OAuth scope.
Inputs: flowId (required).
hubspot_workflows_updateA
[BETA] Fully replace an existing automation workflow (flow) in HubSpot Automation v4 API. This is a PUT operation — it replaces the entire flow definition. Fields not included in the request body will be reset to their defaults. To fetch the current state before updating, use hubspot_workflows_get first. Requires the "automation" OAuth scope.
Inputs: flowId (required), name, type, actions, +4 more.
hubspot_workflows_v3_getA
[LEGACY] Get a single Workflow by ID using the HubSpot Automation v3 API. This is the legacy API — prefer Automation v4 flows for new integrations.
Inputs: workflowId (required).
hubspot_workflows_v3_listA
[LEGACY] List all Workflows using the HubSpot Automation v3 API. This is the legacy API — prefer Automation v4 flows for new integrations. Returns a flat list of workflow definitions.
Inputs: limit, offset.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 37 tools
Each tool targets a distinct operation within a well-defined module (associations, CRM objects, properties, workflows, enrollments, quotes, automation callbacks). Overlaps are only between individual and batch variants, which are clearly differentiated by name and description.
All tools follow the consistent pattern 'hubspot_<module>_<action>', with actions using clear verbs (create, get, list, update, delete, archive, etc.). Batch variants and legacy versions are indicated by predictable prefixes ('batch_', 'v3_').
With 37 tools, the server exceeds the recommended range of 3-15 for a well-scoped set. While the domain (HubSpot CRM + Automation) is broad and each tool has a clear purpose, the sheer number makes it harder for an agent to navigate without advanced context.
The tool surface provides comprehensive coverage for CRM object CRUD (including batch operations and search), associations (with label discovery), property management, workflow management (v3 and v4), enrollment lifecycle, and automation callback handling. No obvious gaps for typical HubSpot automation tasks.
Maintenance
Related MCP Connectors
The HubSpot MCP Server acts as a bridge that enables AI assistants and Large Language Models to securely interact with HubSpot CRM data through natural conversation, without requiring users to understand complex API structures. It provides read-only access to standard CRM objects (contacts, companies, deals, tickets, products, invoices, and more) and their associations, secured via OAuth 2.0, allowing AI agents to perform tasks like summarizing deals, fetching company updates, and looking up record changes.
HubSpot MCP server: 9 tools, every client portal on one connector. Writes preview first.
MCP server for the HubSpot Integrations Center HubDB: search and retrieve integration data.
Marketo MCP server for AI. 130 tools to operate Marketo from Claude, Cursor, or ChatGPT.
Related MCP Servers
- AlicenseBqualityFmaintenanceMCP server for HubSpot CRM — 33 tools covering contacts, companies, deals, pipelines, lists, marketing emails, forms, workflows, and properties.3014 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the HubSpot CRM API with tools for managing contacts, companies, deals, tickets, and CRM workflows. Generated with MCPForge. Sensitive operations can be protected with permissions, audit logs, and approval workflows.MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides AI assistants with full access to HubSpot CRM. Manage contacts, companies, deals, pipelines, and associations directly from Claude, Cursor, or any MCP-compatible client.8 npmMIT
- FlicenseCqualityDmaintenanceAn independent MCP server built from HubSpot's OpenAPI specs, offering 106 tools for CRM automation including contacts, companies, deals, invoices, and line items.1002-