HubSpot MCP Server – CRM Access for AI Agents

Overview

HubSpot provides an official remote Model Context Protocol server for connecting MCP-compatible AI tools and agents to HubSpot CRM data. The hosted endpoint at https://mcp.hubspot.com/ acts as a bridge between an AI client and HubSpot APIs, allowing users and developers to work with HubSpot account context through natural-language workflows instead of calling individual APIs directly.

This entry describes the remote HubSpot MCP server for CRM access. HubSpot also documents a separate local Developer MCP server for building apps and CMS assets through the HubSpot CLI; that local developer workflow is distinct from the hosted CRM MCP endpoint.

What the MCP server enables

The remote server can expose HubSpot CRM, activity, and marketing context to an authorized MCP client. Documented read access includes CRM records such as contacts, companies, deals, tickets, users, carts, invoices, orders, line items, products, quotes, subscriptions, and segments; activities such as calls, emails, meetings, notes, and tasks; and content or marketing objects such as blog posts, landing pages, site pages, campaigns, and marketing events.

Documented write access includes supported CRM records such as contacts, companies, deals, tickets, line items, and products, plus activities such as calls, emails, meetings, notes, and tasks. Useful agent workflows include summarizing deal pipelines, reviewing recent contact activity, creating follow-up tasks, logging calls, updating CRM records, and building custom agentic workflows that need HubSpot account context.

When to use it

Use the HubSpot MCP server when an AI assistant needs live HubSpot data and should operate under HubSpot's normal user-permission model. It is appropriate for sales, service, marketing, and RevOps workflows such as summarizing opportunities by stage, checking recent engagement history for a company, drafting CRM updates, or generating reports from supported HubSpot objects.

It should not be treated as a general-purpose semantic search layer. HubSpot notes that the server is based behind the scenes on the CRM search API and currently does not include vector search capabilities.

Connection and authentication

The hosted server uses Streamable HTTP at https://mcp.hubspot.com/. To connect, create an MCP auth app in HubSpot, configure a redirect URL for the MCP client, and use the generated client ID and client secret. The MCP client must support OAuth with PKCE; PKCE is required for HubSpot MCP authentication. During authorization, the user selects a HubSpot account, grants permissions, and the MCP client then makes requests on behalf of that authenticated user.

Key considerations

HubSpot actions respect existing HubSpot user permissions, so users can only view or modify records they already have access to. Available scopes are determined by the server tools available at installation time and the permissions the user grants; if HubSpot adds new scopes or object access later, an existing app may need reauthorization. If Sensitive Data is enabled in the HubSpot account, activity objects such as calls, emails, meetings, notes, and tasks are blocked through the MCP server. Store OAuth credentials securely, keep redirect URLs aligned between HubSpot and the MCP client, and design token refresh handling so expired or invalidated refresh tokens trigger a fresh authorization flow.