What is it?

The HubSpot MCP (Model Context Protocol) server (remote) is now available in public beta. This unlocks the ability to bring HubSpot context into the tools and environments where you work.

With the hosted endpoint (mcp.hubspot.com), you can connect any compatible MCP client, allowing you to create custom workflows and integrations powered by your HubSpot context.

The HubSpot MCP server supports read-only access to the following CRM objects:

• Contacts
• Companies
• Deals
• Tickets
• Invoices
• Products
• Line Items
• Orders
• Carts
• Subscriptions
• Quotes

The server is secure by design. It connects to HubSpot accounts via OAuth, and all tool calls respect both user-level and field-level permissions configured in the connected account.

Why does it matter?

The HubSpot MCP server gives you more flexibility to build secure, AI-powered workflows and integrations with HubSpot data. By enabling granular CRM access through AI agents and third-party apps, it supports use cases such as automated reporting, custom workflows, and embedding HubSpot context into external platforms.

This also unlocks new opportunities and use cases to bring HubSpot context into the tools you already use.

You can use the HubSpot MCP server with any compatible MCP client, as well as directly through the OpenAI or Anthropic APIs, to create custom integrations.

How does it work?

You must be on the new HubSpot Developer Platform, and create user-level applications with read scopes for the supported objects. These OAuth credentials are then used to connect to the mcp.hubspot.com endpoint through any compatible MCP client. Apps built with the HubSpot MCP server follow the same distribution limits as other HubSpot apps.

Who gets it?

The HubSpot MCP server is only available to all hubs and tiers using the new HubSpot Developer Platform.

Learn more about the HubSpot MCP Server on our documentation.