# HubSpot MCP Server [Official] [Health: Active]

**Category:** 👤 Customer Data Platforms  
**Repository:** https://developers.hubspot.com/mcp  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/hubspot-mcp-server

## Description
HubSpot's official hosted MCP server. Gives MCP clients read and write access to HubSpot CRM records such as contacts, companies, deals and tickets, over OAuth 2.1 with PKCE using an MCP connector created in your HubSpot account.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: medium). Install path inferred — verify against the README before running it. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "hubspot-mcp-server": {
    "url": "https://developers.hubspot.com/mcp"
  }
}
```

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/hubspot-mcp-server/readme_