HubSpot MCP Server

The HubSpot MCP Server is the official Model Context Protocol implementation built and maintained by HubSpot. It exposes a HubSpot account to MCP-compatible clients like Claude Desktop, Cursor, and Claude Code so an AI agent can retrieve, create, and update CRM records, log engagements, manage associations, and surface marketing and reporting context. The server entered public beta on May 6, 2025.

HubSpot ships the MCP capability in two forms. A remote, OAuth-based server at mcp.hubspot.com is the path forward for client-side connections (Claude's HubSpot connector uses this flow). An npm-distributed local server, @hubspot/mcp-server, can be run with npx against a HubSpot private app access token, which is the most common setup for developer tooling today. A separate Developer MCP Server (hs mcp setup via the HubSpot CLI) is aimed at scaffolding HubSpot Developer Platform projects rather than CRM data access.

Read and write coverage spans contacts, companies, deals, tickets, line items, products, orders, carts, invoices, quotes, subscriptions, segments, and engagements (calls, emails, meetings, notes, tasks). Read-only coverage includes users, teams, owners, roles, campaigns and campaign metrics, landing pages, website pages, and blog posts. Custom Sensitive Data Properties and PHI are excluded from access, and sensitive standard records are read-only.

Tools

Option A: Remote MCP server (OAuth)

Some MCP clients (Claude Web/Desktop's HubSpot connector, Cursor) can connect directly to HubSpot's hosted endpoint at mcp.hubspot.com using OAuth 2.0. In Claude:

• Open Settings, then Connectors, then Browse connectors
• Select HubSpot, click Add to your team, then Connect
• Authenticate with HubSpot and approve the requested scopes
• Toggle HubSpot on inside the chat window

HubSpot is migrating to OAuth 2.1 with PKCE and single-use refresh tokens later in 2025.

Option B: Local server via npm and Private App token

1. In HubSpot, create a Private App (Settings, Integrations, Private Apps) and grant the CRM and content scopes you want the agent to use.
2. Copy the access token.
3. Add the server to your MCP client config:

{
  "mcpServers": {
    "HubspotMCP": {
      "command": "npx",
      "args": ["-y", "@hubspot/mcp-server"],
      "env": {
        "PRIVATE_APP_ACCESS_TOKEN": "YOUR_HUBSPOT_PRIVATE_APP_TOKEN"
      }
    }
  }
}

4. Restart the MCP client. The HubSpot tools will appear in the tools menu.

Prerequisites

• A HubSpot account (Free or paid). Some objects like quotes, invoices, and subscriptions require corresponding HubSpot products.
• For the remote server: a HubSpot Developer Platform account with a user-level app configured with read scopes.
• For the local npm server: Node.js (for npx) and a Private App access token.

Notes

• HubSpot recommends testing write and delete actions in a sandbox account first, since LLMs can hallucinate object IDs and properties.
• Custom Sensitive Data Properties and PHI are not accessible. Sensitive standard records are read-only.

• Pull a list of contacts at a target account, summarize recent engagement history, and draft a follow-up email logged back as a HubSpot note.
• Create or update deals from meeting transcripts, including amount, stage, and close date, and associate them to the right company and contact records.
• Triage open tickets by reading priority and engagement timeline, then update status or assign owners in bulk.
• Generate weekly pipeline and campaign performance summaries by reading deals, campaign metrics, and landing page analytics.
• Sync inbound research into HubSpot by creating contacts, attaching call notes, and linking line items or products to a quote.

• "List the 20 most recent deals in the New Business pipeline that have moved stages this week and summarize the changes."
• "Find all contacts at Acme Corp, show their last engagement, and add a note that we discussed Q3 renewal on the next-step call."
• "Create a HubSpot task for the deal owner of every deal stuck in 'Proposal Sent' for more than 14 days."
• "Update the lifecycle stage to 'Customer' for the contacts in this list and associate them with company Acme."
• "Show campaign performance for the May product launch campaign, including landing page sessions and influenced revenue."

• Official, vendor-maintained server with broad coverage of CRM objects, engagements, associations, and marketing content.
• Two deployment options: an OAuth-based remote server at mcp.hubspot.com and a local @hubspot/mcp-server npm package with a Private App token.
• Read and write support across contacts, companies, deals, tickets, line items, products, orders, carts, invoices, quotes, subscriptions, and engagements.
• Integrates cleanly with Claude (including the first-party HubSpot connector), Cursor, and other MCP clients.

• Still in public beta; behavior, scopes, and tool surface are evolving.
• No access to custom Sensitive Data Properties or PHI; sensitive standard records are read-only.
• Write and delete actions are easy to misfire; HubSpot explicitly warns to review every change-making tool call and to test in a non-production portal.

• Composio HubSpot toolkit, which wraps HubSpot APIs as MCP-callable tools alongside other SaaS connectors.
• shinzo-labs/hubspot-mcp, a community open-source MCP implementation for HubSpot.
• peakmojo/mcp-hubspot (baryhuang), a community server that adds vector storage and caching on top of the HubSpot API.