HubSpot MCP connector for AI agents

HubSpot MCP tools for AI agents

CALL ANY TOOL

12 tools covering get.

hubspotmcp_get_campaign_analytics

Get campaign analytics

Retrieve engagement analytics (sessions, new contacts, influenced contacts) for one or more HubSpot campaigns.

Parameters

Name

Type

Required

Description

requests

array

Optional

Required: List of analytics requests to process. Each entry is a full CampaignAnalyticsRequest. Maximum 20 requests per batch.

hubspotmcp_get_campaign_asset_metrics

Get campaign asset metrics

hubspotmcp_get_campaign_contacts_by_type

Get campaign contacts by type

hubspotmcp_get_content_analytics_report

Get content analytics report

hubspotmcp_get_crm_objects

Get crm objects

hubspotmcp_get_organization_details

Get organization details

hubspotmcp_get_properties

Get properties

hubspotmcp_get_user_details

Get user details

hubspotmcp_manage_crm_objects

Manage crm objects

hubspotmcp_manage_landing_page

Manage landing page

Read from or write to HubSpot landing pages. Specify the action field to control the operation (LIST, GET, CREATE, UPDATE, DELETE, etc.).

Parameters

Name

Type

Required

Description

action

string

Required

Action to perform. One per call. READ actions (no side effects): "MODULES": list every module on the page draft. Each entry includes the module's field values, its layout position (sectionId, rowIndex, parentCellName when it lives inside a nested column, and cellWidth/cellX on the 12-column grid), and ownership flags (overrideable, globalOwned, globalPartialPath, themePartialOwned). Positions are populated even on a freshly created template page, before any edit. Capture a module's position here BEFORE you REMOVE or MOVE it so you can restore or reposition it precisely. Check ownership before REMOVE/MOVE: true global partials (header/footer) and global widgets are refused, but modules inside theme dnd_partial sections are removable and movable. "MODULE_TYPES": list available module types for this page's theme (call before INSERT). "MODULE_DEF": full field schema for a module type (requires modulePath). The response also includes the curated guide in moduleGuide when one exists, so a separate MODULE_GUIDE call is usually unnecessary. "MODULE_STYLES": read the layout styles (padding, margin, background, visibility) for a module (requires moduleId). "MODULE_GUIDE": (rarely needed — MODULE_DEF already returns the same guide inline) curated markdown for the modulePath covering required fields, common traps, and a minimal INSERT body. Errors if no guide exists; check MODULE_TYPES.hasGuide first. "REVISIONS": list recent page revisions for undo. "TEMPLATES": list landing page templates available in the portal (contentId not required). "FORMS": list forms available in the portal for embedding via the @hubspot/form module (contentId not required). Returns guid, name, portalId, formType, isPublished, createdAt, updatedAt. "BRAND_KIT": fetch the portal's primary brand kit (colors, fonts, logos) when brand-consistent content would help — e.g. picking a CTA color, a hero font, or a logo to drop into a header (contentId not required). WRITE actions (mutate the same shared draft — issue them ONE AT A TIME, never in parallel): "CLONE": duplicate an existing page (requires contentId of the source page; optional pageName and slug for the clone). Returns a new contentId. "CREATE_FROM_TEMPLATE": create the page from a template (requires pageName and templatePath; optional slug). MUST be preceded by a proposal card (call render_landing_page_ui directly with a "propose" target — there is no separate write step to propose) and an explicit user confirmation IN CHAT — never the first step of creating a page, and choosing a template is NOT confirmation. Returns contentId. "SET_MODULE_FIELDS": verbatim field patch on one module (requires contentId, moduleId, fieldOverridesJson). "SET_MODULE_STYLES": set layout styles (padding, margin, background, visibility) on one module (requires contentId, moduleId, stylesJson). Merge semantics — only supplied fields are updated. Call action=MODULE_STYLES first to see current values. "SET_SECTION_STYLES": set the background, padding, margin, or full-width of the ENTIRE SECTION band a module sits in (requires contentId, moduleId, stylesJson; moduleId is any module inside the band, used as an anchor). This is the correct way to do "make this section's background " — do NOT inject CSS via SET_METADATA headHtml for section backgrounds. Merge semantics. Page-scoped bands — including theme dnd_partial sections — CAN be styled; only true global sections (header/footer/global widgets) are refused. "INSERT": add a new module (requires contentId, modulePath; then EITHER anchorModuleId+anchorPosition for anchor-based placement, OR sectionId+rowStart+columnStart+columnsSpanned for grid-coord placement; optional fieldOverridesJson). "REMOVE": delete one module (requires contentId, moduleId). If it was the last module in its section band, the now-empty band — background and padding included — is collapsed too, so no empty "Drop modules here" ghost band is left behind. "REMOVE_SECTION": delete the ENTIRE section band a module sits in — the whole top-level row, every module in it, AND the band's own background/padding styles (requires contentId, moduleId; moduleId is any module inside the target band, used as an anchor). Page-scoped sections — including theme dnd_partial sections like a logo bar — CAN be removed; only true global sections are refused. "MOVE": reposition module (requires contentId, moduleId; optional sectionId, rowStart, columnStart). "SET_METADATA": update page metadata — pageName, htmlTitle, slug, metaDescription, featuredImageUrl, language, headHtml (requires contentId; all metadata fields optional). "PUBLISH": publish draft (requires contentId; confirm with the user first). "RESTORE_REVISION": roll back to revision (requires contentId, revisionId; confirm first).

anchorModuleId

string

Optional

Anchor-based placement: moduleId of an existing module that the new INSERT should land relative to. When provided, omit rowStart / columnStart / columnsSpanned — the backend resolves the target row from the anchor and auto-redistributes column widths across siblings. Pair with anchorPosition.

anchorPosition

string

Optional

Anchor placement direction. Used with anchorModuleId on INSERT. Values: "BEFORE" (new module on a new row immediately above the anchor's row), "AFTER" (new row immediately below), "IN_ROW_WITH" (sibling cell appended to the right of all existing cells in the anchor's row — siblings give up width), "IN_ROW_BEFORE" (sibling cell positioned to the LEFT of the anchor within the same row), "IN_ROW_AFTER" (sibling cell positioned to the RIGHT of the anchor within the same row, regardless of any cells beyond the anchor), "START_OF_SECTION" (first row of anchor's section), "END_OF_SECTION" (last row of anchor's section), "STACK_ABOVE" (wrap the anchor in a column and place the new module ABOVE it as a stacked row), "STACK_BELOW" (same, stacked BELOW). STACK_* builds a "unified section" — both modules share ONE wrapper cell as separate rows (the shape the editor's drag-to-stack creates); use it instead of BEFORE/AFTER when the two modules should read as one visual group rather than independent section rows. STACK requires a module anchor inside a section (not a top-level section id).

availableForNewContent

boolean

Optional

When action=TEMPLATES: filter to templates available for new page creation. Omit to return all templates.

columnsSpanned

integer

Optional

Width in columns on the 12-column grid. Required for INSERT when using legacy grid-coord placement. Full width=12, two halves=6 each, three thirds=4 each. Omit when using anchor-based placement (anchorModuleId + anchorPosition) — width is computed automatically by stealing from siblings.

columnStart

integer

Optional

1-based column position on a 12-column grid. Required for INSERT (grid-coord placement). Optional for MOVE. columnStart=1 is leftmost.

contentId

integer

Optional

Content ID of the landing page. Required for most actions. NOT required for CREATE_FROM_TEMPLATE (creates a new page), TEMPLATES, FORMS, BRAND_KIT, MODULE_DEF, and MODULE_GUIDE.

featuredImageUrl

string

Optional

Featured image URL for social sharing. Only used for SET_METADATA. Omit to leave unchanged.

fieldOverridesJson

string

Optional

JSON object of verbatim field values (e.g. {"heading":"Close deals faster"}). Required for SET_MODULE_FIELDS. Optional for INSERT (sets initial field values on the new module).

folderName

string

Optional

When action=TEMPLATES: filter by folder name (e.g. "my-theme/templates").

headHtml

string

Optional

Raw HTML injected into (e.g. ""). Only used for SET_METADATA. Omit to leave unchanged.

htmlTitle

string

Optional

HTML tag for the page (~50–60 chars). Only used for SET_METADATA. Omit to leave unchanged.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>language</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>ISO-639-1 language code (e.g. "en", "de"). Used for SET_METADATA (omit to leave unchanged).</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>limit</div></div><div class="cd-ta-table-td _02"><div>integer</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Maximum number of results to return per page.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>metaDescription</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Meta description for search snippets (~140–160 chars). Only used for SET_METADATA. Omit to leave unchanged.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>moduleId</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Module ID to operate on. Required for SET_MODULE_FIELDS, SET_MODULE_STYLES, SET_SECTION_STYLES, REMOVE, REMOVE_SECTION, MOVE, and MODULE_STYLES. For REMOVE_SECTION and SET_SECTION_STYLES it is any module inside the target section band (an anchor). Find IDs via action=MODULES.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>modulePath</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Module type path (e.g. "@hubspot/rich_text"). Required for INSERT, MODULE_DEF, and MODULE_GUIDE. Use paths exactly as returned by action=MODULE_TYPES.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>offset</div></div><div class="cd-ta-table-td _02"><div>integer</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Pagination offset — number of records to skip before returning results.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>pageName</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Name for the landing page. Required for CREATE_FROM_TEMPLATE. Optional for CLONE (defaults to a copy of the source page name). Also used by SET_METADATA to update the internal listing name shown in the HubSpot content listing UI (not the HTML title).</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>query</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Text to search for within the default searchable properties of the specified object type.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>responseFormat</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Verbosity of the response. "DETAILED" returns all fields and is the default when omitted. "SUMMARY" trims verbose fields to save tokens on large pages: when action=MODULES, drops module field values and returns only module IDs, modulePaths, and section info. For MODULE_TYPES, MODULE_DEF, and REVISIONS, SUMMARY currently returns the same payload as DETAILED.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>revisionId</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Revision ID to restore. Required for RESTORE_REVISION. Find IDs via action=REVISIONS.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>rowStart</div></div><div class="cd-ta-table-td _02"><div>integer</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>1-based row position within the section. Required for INSERT (grid-coord placement). Optional for MOVE. Modules with the same rowStart and sectionId are placed side-by-side.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>sectionId</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Layout section ID to place the module in. Required for INSERT (grid-coord placement). Optional for MOVE (omit to keep current section). Find section IDs via action=MODULES.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>slug</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>URL slug (lowercase, hyphenated, no leading slash). Used for SET_METADATA (omit to leave unchanged), CREATE_FROM_TEMPLATE (omit to derive from pageName), or CLONE (omit to auto-generate).</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>stylesJson</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>JSON object of structured layout styles to merge. Required for SET_MODULE_STYLES (onto a module) and SET_SECTION_STYLES (onto a section band). Uses merge semantics: only supplied fields are updated, existing styles are preserved. Shape: {"breakpoint_styles":{"default":{"padding":{"top":{"value":20,"units":"px"}},"margin":{"top":{"value":10,"units":"px"}}}}}. Supported breakpoints: "default" (desktop), "mobile". Supported spacing sides — padding: top, right, bottom, left; margin: top, bottom. Each side is a Size: {"value":<number>,"units":"px"|"em"|"rem"|..."}. Background color (mainly for SET_SECTION_STYLES) goes in the top-level backgroundColor field as r/g/b/a: {"backgroundColor":{"r":255,"g":238,"b":0,"a":1}} (r/g/b 0–255, a 0–1). Section-only fields (SET_SECTION_STYLES): "forceFullWidthSection":true OR "maxWidthSectionCentering":<px> (mutually exclusive). Use camelCase keys (e.g. backgroundColor, breakpointStyles, forceFullWidthSection) — they mirror what action=MODULE_STYLES returns. Also supports per-breakpoint "hidden":true/false to toggle visibility. Layout only — for TEXT color use the separate textColor field, not this.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>templatePath</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Template path to build the page on. Required for CREATE_FROM_TEMPLATE. Use action=TEMPLATES to discover available templates, then pass the templatePath exactly as returned.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>textColor</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>For action=SET_MODULE_STYLES: set the text color of ALL text in a module (headings, paragraphs, list items) to this CSS color, e.g. "#cc0000", "red", or "rgb(204,0,0)". This is the reliable way to recolor module text — it writes a scoped, !important rule the renderer applies to the module's own elements, overriding the theme. Do NOT hand-roll headHtml CSS for text color, and do NOT use it to recolor a whole section (use the section's sectionStyleVariant for that). Supply with moduleId; may be combined with stylesJson.</div></div></div><div class="cd-ta-table-tr last"><div class="cd-ta-table-td _01"><div>themePath</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>When action=TEMPLATES: filter templates by theme path. Use for HubSpot themes ("@hubspot/elevate", "@hubspot/growth"), marketplace themes ("@marketplace/vendor/theme-name"), or custom themes ("my-custom-theme"). Omit to return templates across all themes.</div></div></div></div></div></div></div></div><div class="cd-ta-item"><div class="cd-ta-item-trigger" style="cursor: pointer"><div class="cd-ta-item-trigger-left"><div class="cd-ta-item-trigger-text">hubspotmcp_query_crm_data</div><div class="cd-ta-item-trigger-text-2">Query crm data</div></div><div class="cd-ta-item-trigger-right" style="transition: transform 0.3s; transform: rotate(0deg)"></div></div><div class="cd-ta-item-content" style="display: none; height: 0px; overflow: hidden"><div class="cd-ta-item-content-inner"><div class="cd-ta-item-subtext">Query HubSpot CRM data using SQL with HubSpot-specific extensions. Call get_properties first to discover valid property names.</div><div class="cd-ta-item-caption">Parameters</div><div class="cd-ta-table"><div class="cd-ta-table-inner"><div class="cd-ta-table-tr"><div class="cd-ta-table-th _01"><div>Name</div></div><div class="cd-ta-table-th _02"><div>Type</div></div><div class="cd-ta-table-th _03"><div>Required</div></div><div class="cd-ta-table-th _04"><div>Description</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>sql</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03 green"><div>Required</div></div><div class="cd-ta-table-td _04"><div>SQL query to execute against HubSpot CRM data.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>chatInsights</div></div><div class="cd-ta-table-td _02"><div>object</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Insights about the chat including user intent and satisfaction level.</div></div></div><div class="cd-ta-table-tr last"><div class="cd-ta-table-td _01"><div>verbosityLevel</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Controls the amount of data returned in the response: - LOW: Data only, no citation links - MEDIUM/HIGH: Data with citation links for each record when available</div></div></div></div></div></div></div></div><div class="cd-ta-item"><div class="cd-ta-item-trigger" style="cursor: pointer"><div class="cd-ta-item-trigger-left"><div class="cd-ta-item-trigger-text">hubspotmcp_render_landing_page_ui</div><div class="cd-ta-item-trigger-text-2">Render landing page ui</div></div><div class="cd-ta-item-trigger-right" style="transition: transform 0.3s; transform: rotate(0deg)"></div></div><div class="cd-ta-item-content" style="display: none; height: 0px; overflow: hidden"><div class="cd-ta-item-content-inner"><div class="cd-ta-item-subtext">Display the landing page card (preview image and open-in-editor link) in the chat UI.</div><div class="cd-ta-item-caption">Parameters</div><div class="cd-ta-table"><div class="cd-ta-table-inner"><div class="cd-ta-table-tr"><div class="cd-ta-table-th _01"><div>Name</div></div><div class="cd-ta-table-th _02"><div>Type</div></div><div class="cd-ta-table-th _03"><div>Required</div></div><div class="cd-ta-table-th _04"><div>Description</div></div></div><div class="cd-ta-table-tr last"><div class="cd-ta-table-td _01"><div>target</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03 green"><div>Required</div></div><div class="cd-ta-table-td _04"><div>What to render. Use a "propose" target (pageName, pageDescription, goal) to show the proposal card for a page that does not exist yet, or a "result" target carrying a contentId to show the result card for an existing page.</div></div></div></div></div></div></div></div><div class="cd-ta-item"><div class="cd-ta-item-trigger" style="cursor: pointer"><div class="cd-ta-item-trigger-left"><div class="cd-ta-item-trigger-text">hubspotmcp_search_crm_objects</div><div class="cd-ta-item-trigger-text-2">Search crm objects</div></div><div class="cd-ta-item-trigger-right" style="transition: transform 0.3s; transform: rotate(0deg)"></div></div><div class="cd-ta-item-content" style="display: none; height: 0px; overflow: hidden"><div class="cd-ta-item-content-inner"><div class="cd-ta-item-subtext">Search and retrieve CRM records from HubSpot using filters, sorting, and keyword queries.</div><div class="cd-ta-item-caption">Parameters</div><div class="cd-ta-table"><div class="cd-ta-table-inner"><div class="cd-ta-table-tr"><div class="cd-ta-table-th _01"><div>Name</div></div><div class="cd-ta-table-th _02"><div>Type</div></div><div class="cd-ta-table-th _03"><div>Required</div></div><div class="cd-ta-table-th _04"><div>Description</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>objectType</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03 green"><div>Required</div></div><div class="cd-ta-table-td _04"><div>The HubSpot CRM object type to operate on (e.g. contacts, companies, deals).</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>chatInsights</div></div><div class="cd-ta-table-td _02"><div>object</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Insights about the chat including user intent and satisfaction level. IMPORTANT: MUST be provided for all scenarios.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>filterGroups</div></div><div class="cd-ta-table-td _02"><div>array</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>* The filter groups that define the search criteria. * Filters that match ALL of several conditions (AND logic) should be put in the same filterGroup. * Filters that match AT LEAST ONE of several conditions (OR logic) should be put in a separate filterGroup.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>limit</div></div><div class="cd-ta-table-td _02"><div>integer</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Maximum number of results to return per page.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>offset</div></div><div class="cd-ta-table-td _02"><div>integer</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Pagination offset — number of records to skip before returning results.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>properties</div></div><div class="cd-ta-table-td _02"><div>array</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>List of property names to include in results.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>query</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Text to search for within the default searchable properties of the specified object type.</div></div></div><div class="cd-ta-table-tr last"><div class="cd-ta-table-td _01"><div>sorts</div></div><div class="cd-ta-table-td _02"><div>array</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Optional sorting rules for results. Only one sort rule can be applied</div></div></div></div></div></div></div></div><div class="cd-ta-item"><div class="cd-ta-item-trigger" style="cursor: pointer"><div class="cd-ta-item-trigger-left"><div class="cd-ta-item-trigger-text">hubspotmcp_search_owners</div><div class="cd-ta-item-trigger-text-2">Search owners</div></div><div class="cd-ta-item-trigger-right" style="transition: transform 0.3s; transform: rotate(0deg)"></div></div><div class="cd-ta-item-content" style="display: none; height: 0px; overflow: hidden"><div class="cd-ta-item-content-inner"><div class="cd-ta-item-subtext">List and search for HubSpot owners who can be assigned to CRM records.</div><div class="cd-ta-item-caption">Parameters</div><div class="cd-ta-table"><div class="cd-ta-table-inner"><div class="cd-ta-table-tr"><div class="cd-ta-table-th _01"><div>Name</div></div><div class="cd-ta-table-th _02"><div>Type</div></div><div class="cd-ta-table-th _03"><div>Required</div></div><div class="cd-ta-table-th _04"><div>Description</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>limit</div></div><div class="cd-ta-table-td _02"><div>integer</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Maximum number of results to return per page.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>offset</div></div><div class="cd-ta-table-td _02"><div>integer</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Pagination offset — number of records to skip before returning results.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>ownerIds</div></div><div class="cd-ta-table-td _02"><div>array</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Optional list of owner IDs to lookup directly. When provided, search query is ignored</div></div></div><div class="cd-ta-table-tr last"><div class="cd-ta-table-td _01"><div>searchQuery</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Optional search query to find owners by name or email. Returns all owners if not provided</div></div></div></div></div></div></div></div><div class="cd-ta-item"><div class="cd-ta-item-trigger" style="cursor: pointer"><div class="cd-ta-item-trigger-left"><div class="cd-ta-item-trigger-text">hubspotmcp_search_properties</div><div class="cd-ta-item-trigger-text-2">Search properties</div></div><div class="cd-ta-item-trigger-right" style="transition: transform 0.3s; transform: rotate(0deg)"></div></div><div class="cd-ta-item-content" style="display: none; height: 0px; overflow: hidden"><div class="cd-ta-item-content-inner"><div class="cd-ta-item-subtext">Find the most relevant CRM property definitions using keyword-based search.</div><div class="cd-ta-item-caption">Parameters</div><div class="cd-ta-table"><div class="cd-ta-table-inner"><div class="cd-ta-table-tr"><div class="cd-ta-table-th _01"><div>Name</div></div><div class="cd-ta-table-th _02"><div>Type</div></div><div class="cd-ta-table-th _03"><div>Required</div></div><div class="cd-ta-table-th _04"><div>Description</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>objectType</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03 green"><div>Required</div></div><div class="cd-ta-table-td _04"><div>The HubSpot CRM object type to operate on (e.g. contacts, companies, deals).</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>keywords</div></div><div class="cd-ta-table-td _02"><div>array</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Multiple search keywords (max 5) to find relevant properties using efficient keyword-based search. Supports searching for multiple related property concepts in a single request. Examples: - ["urgency"] - Single keyword search - ["assignee", "assigned_to", "owner"] - Multiple related keywords for assignment - ["name", "employees", "zip", "contact"] - Multiple unrelated keywords for different properties If both query and keywords are provided, keywords takes precedence. If empty and no query provided, returns all properties for the object type.</div></div></div><div class="cd-ta-table-tr last"><div class="cd-ta-table-td _01"><div>query</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Text to search for within the default searchable properties of the specified object type.</div></div></div></div></div></div></div></div><div class="cd-ta-item"><div class="cd-ta-item-trigger" style="cursor: pointer"><div class="cd-ta-item-trigger-left"><div class="cd-ta-item-trigger-text">hubspotmcp_submit_feedback</div><div class="cd-ta-item-trigger-text-2">Submit feedback</div></div><div class="cd-ta-item-trigger-right" style="transition: transform 0.3s; transform: rotate(0deg)"></div></div><div class="cd-ta-item-content" style="display: none; height: 0px; overflow: hidden"><div class="cd-ta-item-content-inner"><div class="cd-ta-item-subtext">Submit user feedback about the HubSpot MCP connector to HubSpot.</div><div class="cd-ta-item-caption">Parameters</div><div class="cd-ta-table"><div class="cd-ta-table-inner"><div class="cd-ta-table-tr"><div class="cd-ta-table-th _01"><div>Name</div></div><div class="cd-ta-table-th _02"><div>Type</div></div><div class="cd-ta-table-th _03"><div>Required</div></div><div class="cd-ta-table-th _04"><div>Description</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>explanationOfSatisfaction</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03 green"><div>Required</div></div><div class="cd-ta-table-td _04"><div>Brief explanation of what went wrong from the agent's perspective. When errors occurred: Explain why the agent made a request that failed validation, including what the agent's reasoning was and why it failed. This helps with investigation and improvement. Example: 'Error: "A non-empty list of objects to create or update must be provided" - Agent attempted to batch update contacts but incorrectly passed an empty list because it filtered out all objects based on a misunderstanding of the user's criteria.'</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>feedback</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03 green"><div>Required</div></div><div class="cd-ta-table-td _04"><div>User's verbatim feedback about the HubSpot connector. CRITICAL RULES: - Use the user's EXACT words. NEVER paraphrase, summarize, or rewrite. - If the user said it in their language, keep it in their language. - If the user hasn't typed specific feedback yet, do NOT fill this in yourself — ask them first. - Avoid PII — use anonymized references.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>goal</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03 green"><div>Required</div></div><div class="cd-ta-table-td _04"><div>User's goal or what they were trying to accomplish and relevant conversation context. Avoid PII - use anonymized references. Important: Avoid adding extraneous information, especially from memory.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>feedbackType</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Category of the feedback being submitted. Used to triage and analyze feedback trends. - PROBLEM: Something is broken or not working as expected (errors, incorrect results, bugs). - FEATURE_REQUEST: A request for new functionality or capability, including enhancements to existing features that would require new behavior to be built. - GENERAL_FEEDBACK: Opinions, observations, or suggestions about an existing tool or workflow — e.g., usability impressions, praise, workflow friction, or improvement ideas that don't rise to the level of a bug report or feature request. - OTHER: Use only when the feedback genuinely does not fit any of the above categories.</div></div></div><div class="cd-ta-table-tr"><div class="cd-ta-table-td _01"><div>sourceInterface</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Where the feedback originated. - MCP_UI: Submitted from the dedicated in-app feedback UI rendered by the MCP host (e.g. a feedback form/widget the user explicitly opened). - NON_UI: Submitted from a regular chat conversation (no dedicated feedback UI).</div></div></div><div class="cd-ta-table-tr last"><div class="cd-ta-table-td _01"><div>triggeringToolName</div></div><div class="cd-ta-table-td _02"><div>string</div></div><div class="cd-ta-table-td _03"><div>Optional</div></div><div class="cd-ta-table-td _04"><div>Name of the HubSpot tool related to this feedback. IMPORTANT: This tool ONLY collects feedback about HubSpot connector tools. Do NOT submit feedback about non-HubSpot tools (e.g. Slack, Microsoft 365, Notion, iMessage, Intercom, Bash, etc.).</div></div></div></div></div></div></div></div><div class="cd-ta-item"><div class="cd-ta-item-trigger" style="cursor: pointer"><div class="cd-ta-item-trigger-left"><div class="cd-ta-item-trigger-text">hubspotmcp_tool_guidance</div><div class="cd-ta-item-trigger-text-2">Tool guidance</div></div><div class="cd-ta-item-trigger-right" style="transition: transform 0.3s; transform: rotate(0deg)"></div></div><div class="cd-ta-item-content" style="display: none; height: 0px; overflow: hidden"><div class="cd-ta-item-content-inner"><div class="cd-ta-item-subtext">Retrieve usage instructions and guidance for one or more HubSpot MCP tools.</div><div class="cd-ta-item-caption">Parameters</div><div class="cd-ta-table"><div class="cd-ta-table-inner"><div class="cd-ta-table-tr"><div class="cd-ta-table-th _01"><div>Name</div></div><div class="cd-ta-table-th _02"><div>Type</div></div><div class="cd-ta-table-th _03"><div>Required</div></div><div class="cd-ta-table-th _04"><div>Description</div></div></div><div class="cd-ta-table-tr last"><div class="cd-ta-table-td _01"><div>toolNames</div></div><div class="cd-ta-table-td _02"><div>array</div></div><div class="cd-ta-table-td _03 green"><div>Required</div></div><div class="cd-ta-table-td _04"><div>List of tool names to get usage instructions for</div></div></div></div></div></div></div></div> </div></div></div>

Build your Agent

Same auth pattern across every framework.

from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="hubspotmcp")

mcp = MultiServerMCPClient({
    "hubspotmcp": {
        "url": "https://mcp.scalekit.com/hubspotmcp",
        "headers": {"Authorization": "Bearer " + token}
    }
})
tools = await mcp.get_tools()

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "hubspotmcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/hubspotmcp
// Pass: Authorization: Bearer + token

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "hubspotmcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/hubspotmcp
// Pass: Authorization: Bearer + token

from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="hubspotmcp")
# Connect to MCP at https://mcp.scalekit.com/hubspotmcp
# Pass: Authorization: Bearer + token

Try these prompts

Paste any prompt into your agent to get started.

Get started

Copy the prompt

Copied

Retrieve usage instructions and guidance for one or more HubSpot MCP tools?

Copy the prompt

Copied

Submit user feedback about the HubSpot MCP connector to HubSpot?

Advanced

Copy the prompt

Copied

Find the most relevant CRM property definitions using keyword-based search?

Copy the prompt

Copied

Display the landing page card (preview image and open-in-editor link) in the chat UI?

SEE HOW AUTH WORKS

User authorises once. Every agent call after uses their token with scope enforcement.

Authorize

Your user connects

HubSpot MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

HubSpot MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

HubSpot MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

HubSpot MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

GTM and RevOps Teams

CRM AI agent

Reads the Granola transcript after every call, extracts next steps and updates the HubSpot record, drafts the follow-up in Gmail, and confirms in Slack, all on the rep's own delegated OAuth.

GTM and RevOps Teams

Deal intelligence agent

Pulls recent Gong calls, scores deal risk with an LLM, cross-references the record in Attio, and DMs each owner their at-risk deals in Slack. Every read is scoped to that rep's own access.

GTM and RevOps Teams

Sales call prep agent

Reads tomorrow's calls from Google Calendar, mines past Granola notes and Attio history for context, and delivers each rep a prep brief in Slack, scoped to the calls that rep actually owns.

GTM and RevOps Teams

Outbound prospecting agent

Searches Apollo for prospects matching your ICP, scores and ranks them, drafts personalized outreach in Gmail, and logs every send to Google Sheets. Mail goes out as the rep, not from a shared inbox.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.

// shared token
 audit → bot_service_account

 // scalekit
 audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

One connector today. Ten tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access HubSpot as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the HubSpot OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in HubSpot?
Yes. Pass a tool name filter to listScopedTools so the marketing agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches HubSpot.

What happens when a user revokes HubSpot access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent work across multiple HubSpot portals?
Yes. Each portal is its own connected account with per-user, per-portal vault namespacing. Campaign analytics and CRM reads inherit the user's HubSpot seat permissions.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit