HubSpot MCP Server

Read and update HubSpot CRM contacts, companies, deals, and tickets through MCP and OAuth 2.1 with PKCE.

Install HubSpot MCP Server

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)

Server URL

https://mcp.hubspot.com

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpoint

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint

https://mcp.hubspot.com

Overview

CRM & sales

HubSpot MCP Server connects MCP clients to HubSpot CRM records, with read and write access for contacts, companies, deals, and tickets. Authentication uses OAuth 2.1 with PKCE through an MCP connector created in a HubSpot account. Reach for it when an MCP-compatible agent needs to inspect or modify core HubSpot CRM data without building a separate API integration.

Use cases

Read contact details from HubSpot during an agent workflow
Update company records from an MCP-compatible client
Review and modify deals through conversational automation
Create or update ticket data with an AI agent

Key features

HubSpot CRM record access
Read and write operations
Contacts, companies, deals, and tickets
OAuth 2.1 authentication
PKCE support
HubSpot account MCP connector

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

How HubSpot MCP Server works

What HubSpot MCP Server does

HubSpot MCP Server exposes HubSpot CRM data to MCP clients. Its supported record types include contacts, companies, deals, and tickets. The server provides both read and write access, allowing an MCP-connected agent to retrieve CRM information and make changes to those records.

This makes the server relevant for workflows where an agent needs to work with customer, account, sales, or support records held in HubSpot. The connection is intended for MCP clients rather than for direct use as a standalone REST API.

How it works

Access is established through OAuth 2.1 with PKCE. A HubSpot account owner or administrator creates an MCP connector in HubSpot, and that connector is used to authorize the MCP client’s access to HubSpot CRM.

Once authorized, the MCP client can use the server’s read and write capabilities against the supported CRM record types. The server is hosted by HubSpot, so the connection targets HubSpot’s service rather than a locally run process.

OAuth-based authorization makes the HubSpot account and connector central to setup. The MCP client must support the server’s authentication flow and MCP connections.

Setup and configuration

Create an MCP connector in the relevant HubSpot account before connecting a client. Use the connector as the authorization path for the MCP client, completing the OAuth 2.1 flow with PKCE.

Configuration is account-based rather than described as a set of local environment variables. The account used for authorization determines the HubSpot CRM data available through the connection and the actions permitted by the connector.

After authorization, select the HubSpot MCP connection in an MCP-compatible client and use it for CRM operations. Keep access aligned with the HubSpot account and connector intended for the workflow.

Tools and capabilities

Read HubSpot CRM contacts.
Write changes to contact records.
Read and update company records.
Read and update deal records.
Read and update ticket records.
Authenticate through OAuth 2.1 with PKCE.

Limitations and notes

The supported CRM scope described for this server covers contacts, companies, deals, and tickets. The server depends on an MCP connector created in HubSpot and an MCP client that can complete OAuth 2.1 with PKCE. It is hosted rather than presented as a local server package, so deployment and local process management are not part of the described setup.

Read the full README

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about HubSpot MCP Server

HubSpot MCP Server is an MCP server that connects MCP clients to HubSpot's CRM. It provides read and write access to records including contacts, companies, deals, and tickets, using OAuth 2.1 with PKCE through an MCP connector created in a HubSpot account.

You connect to the hosted server rather than install a local package. Create an MCP connector in your HubSpot account, then authorize your MCP client through the OAuth 2.1 flow with PKCE.

HubSpot MCP Server authenticates clients with OAuth 2.1 and PKCE. The client uses an MCP connector created in a HubSpot account to authorize access to the supported HubSpot CRM records.

The server can read and write HubSpot CRM contacts, companies, deals, and tickets. These record types are the supported CRM scope described for the connection.

Related MCP servers

All in Customer Data Platforms All alternatives

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

HubSpot MCP Server AllMCPs Directory Badge

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/hubspot-mcp-server?style=directory)](https://allmcps.com/mcp/hubspot-mcp-server)

HTML Embed

<a href="https://allmcps.com/mcp/hubspot-mcp-server"><img src="https://allmcps.com/api/badge/hubspot-mcp-server?style=directory" alt="HubSpot MCP Server on AllMCPs" /></a>