For sales teams on HubSpot

A HubSpot MCP server that answers deal questions under each user's own permissions

A HubSpot MCP server answers open deals, owners and company contacts under the permissions that user granted. HubSpot hosts the server and made write tools generally available on 13 April 2026. Activities stay hidden on that server when sensitive data is on. Pexon keeps the signed tool list read-only.

Checked 6 October 2026

HubSpot at a glance: interfaces, access and what exists for AI

What we found
InterfacesHubSpot remote MCP server (MCP over HTTPS, docs public) · CRM API v3 (REST/JSON, docs public)
AuthenticationThe remote MCP server requires OAuth 2.1 with PKCE through an MCP auth app. You do not pick scopes by hand: they follow the tools present at install and the permissions that user grants. CRM API calls can instead use a private-app token limited to the read scopes you select.
Vendor MCP serverVendor server, GA. HubSpot hosts the server at mcp.hubspot.com. It is generally available to all HubSpot accounts. Write tools and activity history take effect on 13 April 2026. If sensitive data is turned on, calls, emails, meetings, notes and tasks are blocked on the MCP server only.
Vendor AI assistantNone found.
Other connectorsNone found.

HubSpot, Inc. (US). Small and mid-sized sales teams, including DACH companies that pick a horizontal CRM. The DACH market overview of 14 May 2026 names HubSpot next to Pipedrive for sales-led SMEs. No customer count is taken from that page.

Why HubSpot is hard for agents

Where a HubSpot connection needs engineering, not configuration

01 · Write

The GA server can change the CRM

The April 2026 release adds write. A sales question does not need it. The tool list we sign starts read-only, even though the vendor server can update records.

02 · Sensitive

Activities disappear when sensitive data is on

Calls, emails, meetings, notes and tasks are blocked on the MCP server in that mode, and still exist on the CRM APIs. An agent that only uses the vendor server will say there is no history.

03 · Reauth

New objects need a fresh grant

HubSpot marks an installed app REQUIRES_REAUTHORIZATION when new object types appear. The user disconnects and reconnects. A stale grant is an empty answer, not a permission to guess.

04 · Identity

One token is not the sales team

A private-app token is an account credential. The MCP path runs as the user who installed and granted it. We use that path so two sellers do not share one view of the pipeline.

What we build

A first HubSpot tool list, written as the manifest your IT team signs

Built on what HubSpot, Inc. documents: contacts, companies, deals, owners, activities when sensitive data is off, tickets. Backends named below are documented resources; "confirmed in blueprint" means the vendor documentation sits behind a login and the resource is checked against your release first.

# hubspot-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
  list_my_deals:   # owner, pipeline, close date -> open deals the user may see
    backend: HubSpot MCP or CRM API deals, read scope
    mode: read
  get_company:     # company -> domain, owner and associated contacts
    backend: CRM companies and contacts
    mode: read
  list_activities: # record -> calls, emails, meetings, notes, tasks
    backend: MCP activity history, refused when sensitive data blocks it
    mode: read
  get_deal:        # deal -> stage, amount, close date, owner
    backend: CRM deals read
    mode: read
  draft_deal_note: # deal, text -> a note a person saves in HubSpot
    backend: not sent by the agent
    mode: propose
audit: every call logged with user, tool, arguments and the HubSpot response

The manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.

One interface per row

How the HubSpot interfaces differ

01

HubSpot remote MCP server

MCP over HTTPS. Documentation is public. hosted at mcp.hubspot.com. Generally available. The changelog dated for 13 April 2026 adds write tools, activity history and marketing objects. OAuth 2.1 with PKCE. Scopes follow the tools and the permissions the user grants at install

MCP over HTTPS. Docs public.

02

CRM API v3

REST/JSON. Documentation is public. contacts, companies, deals and owners. A private-app token can be scoped read-only. Activity objects that sensitive-data mode blocks on the MCP server remain available here

REST/JSON. Docs public.

HubSpot holds the records. An assistant without a governed way in answers from whatever someone pasted into the chat. The connector is the governed way in: named operations, the person's own permissions, every call logged.

What the connector answers, and what it will not do

Questions it answers

  • Which open deals in my pipeline close this month, and who owns each one?
  • What was the last meeting or email on this company, if sensitive data is off?
  • Which contacts on this account have no owner?

What it will not do

  • Move a deal stage, edit an amount or send an email. The signed list is read-only.
  • Read an activity the sensitive-data setting has blocked on the MCP server, and pretend the CRM API was not checked.
  • See a deal the asking user cannot see in HubSpot.

When this is the wrong page

If the only need is HubSpot's own MCP server inside Claude or ChatGPT, turn that on and HubSpot maintains it. A connector is right when the tool list must stay read-only, when sensitive-data mode has hidden activities, or when the answer also needs a second system.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your HubSpot owners and checks every backend against your release and licence. Week two tests whether a person's own HubSpot permissions reach through the connector. You keep the manifest and a costed build plan, whoever builds it. All prices are net and exclude VAT.

What we need from you: a named HubSpot administrator, a test or sandbox system we may call, and one business owner who can say which questions the assistant should answer first. The first production connector is usually a use-case pilot from €15,000; it runs in your environment, and the code is yours.

Sources: HubSpot remote MCP server, generally available · Integrate with the remote HubSpot MCP server · DACH CRM market overview, 14 May 2026. Read 6 October 2026. Vendor documentation changes; verify against the current release.

Questions HubSpot teams ask before the first tool call

Does HubSpot ship its own MCP server?

HubSpot hosts the server at mcp.hubspot.com. It is generally available to all HubSpot accounts. Write tools and activity history take effect on 13 April 2026. If sensitive data is turned on, calls, emails, meetings, notes and tasks are blocked on the MCP server only. This page describes what we add around that fact: a signed tool list and a test that the asking user only sees their own records.

Can the assistant change a deal or send a mail?

Not on the list we sign. The blueprint starts read-only. A draft the person saves in the CRM is the only write, and only after that is agreed.

Will two sellers see the same pipeline?

Only where the CRM would already show both of them the same records. Calls run as the person who asked. The blueprint tests that with two users before anything is called production.

What does a HubSpot connector cost?

The two-week Readiness Blueprint is fixed at €4,900: the tool list, a check against your tenant, and a test that permissions survive the round trip. A production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.

Next step

Not a sales call. An architecture call.

Thirty minutes with the engineer who would build the connector, with your HubSpot administrator in the room if you like.