HubSpot MCP Server: Which Route to Use, What It Can Do, Where It Stops

HubSpot MCP Server: Which Route to Use, What It Can Do, Where It Stops

Yes, HubSpot has an official MCP server. The remote server at https://mcp.hubspot.com lets Claude, ChatGPT and other MCP clients read and change records in your HubSpot account, and it has been generally available to all HubSpot accounts since 13 April 2026. If you use Claude or ChatGPT, you don't build anything: you install HubSpot's ready-made connector and sign in. You only create your own MCP connector in HubSpot when you connect a different client.

HubSpot also ships a second, unrelated server for developers that runs locally through the HubSpot CLI, a local MCP server in the protocol's terms. Most confusion around "HubSpot MCP" comes from mixing the two up, or from mixing HubSpot's server with the many community servers on GitHub.

Disclosure: Customermates, an open-source CRM with its own MCP server, publishes this guide. The HubSpot details were checked on 8 October 2026 against HubSpot's own pages, linked in the sources line at the end.

At a glance

Remote server

Hosted by HubSpot at mcp.hubspot.com. Reads and writes CRM records, activities and marketing content, always within the signed-in user's HubSpot permissions.

Fastest route

Claude and ChatGPT: install HubSpot's connector and sign in with OAuth. HubSpot says the Claude connector is free on every HubSpot tier.

Other clients

Create an MCP connector under Development in HubSpot, then use its client ID and secret in a client that supports OAuth with PKCE.

Main limits

Activity and conversation data is blocked when Sensitive Data is on, the documented write access has no delete, and some tools need paid hubs.

Pick your route first

The question "how do I connect HubSpot MCP" has four different answers, depending on the client and the job.

Third-party servers are a fifth option. Zapier, for example, offers HubSpot actions through its own MCP server at mcp.zapier.com, and GitHub has several community-built HubSpot servers that you run yourself. These are useful when you want one MCP server across many apps. They are not HubSpot's server, so their scope, maintenance and data handling are whatever their maintainer decides.

What the remote server can read and write

HubSpot's integration guide lists the access in detail. In short:

Two details matter for planning. The server is built on HubSpot's CRM search API, which HubSpot says has no vector search, so the AI finds records by filters and properties, not by meaning. And when a record is created or updated, the server applies the account's conditional field logic and pipeline stage validations, so the AI can't skip a required field that a human couldn't skip either.

Limits HubSpot documents

• Sensitive Data blocks activities. If your account has Sensitive Data turned on, calls, emails, meetings, notes, tasks and conversations are blocked through the MCP server. HubSpot notes this applies only to MCP, not to its standard CRM APIs.
• No delete. The documented write access covers creating, editing, logging and publishing. Deleting records is not listed, so cleanup stays a manual job in HubSpot.
• Permissions carry over. Every call runs as the signed-in user and respects their HubSpot permissions. Inbox access restricted to certain users or teams is restricted through MCP as well.
• Scopes are fixed at install. You don't choose scopes yourself. They come from the tools available at install time and the permissions the user grants. When HubSpot adds tools, existing users have to reinstall to grant the new scopes.
• Some tools need paid hubs. AEO metrics and tracked prompts need Marketing Hub Professional or Enterprise; quotes need Revenue Hub Professional or Enterprise.
• Analysis is limited. The SQL query tool supports filtering, aggregation and sorting, but HubSpot states it has no joins, subqueries, association traversal or currency conversion. Questions such as "win rate by stage transition last quarter" may need several calls or a report built in HubSpot.

Connect it: the custom route step by step

For Claude and ChatGPT, the connector handles everything below. For any other client, HubSpot's guide describes these steps:

1. Create an MCP connector

   In HubSpot, go to Development, then MCP Connectors, then Create MCP connector. Enter a name, an optional description and the redirect URL your client uses. For testing with MCP Inspector, HubSpot asks you to add http://localhost:6274/oauth/callback/debug.

2. Copy the credentials

   The connector's details page shows the client ID, client secret and redirect URLs. The redirect URL must match the one configured in your client exactly.

3. Point the client at the server

   Configure your client with https://mcp.hubspot.com and the credentials. The client has to run the OAuth flow with PKCE. MCP Inspector does this automatically; in a custom integration you implement it yourself.

4. Authorize and verify

   Choose the HubSpot account, grant the permissions and authorize. Then call get_user_details: HubSpot recommends it to see which tools and objects your account can actually use.

If a client stops working after a period of inactivity, the usual cause is token refresh. The client must use the refresh token from the first sign-in; if that has expired too, run the OAuth flow again.

The HubSpot developer MCP server

The developer MCP server runs on your machine and is set up with hs mcp setup (HubSpot CLI 8.2.0 or later). It works with Claude Code, Codex CLI, Cursor, Gemini CLI, VS Code and Windsurf and appears there as "HubSpotDev". HubSpot describes it as tools for app and CMS development tasks. It is not the route for a sales team that wants to work with CRM records; that is the remote server's job.

A rollout checklist for a small team

1. Check Sensitive Data first. If it is on, MCP won't see activities or conversations, which removes most of the useful questions about a deal. Better to know before anyone tries it.
2. Review user permissions in HubSpot. The AI sees exactly what the user sees. If a user can edit every deal, so can their connected client.
3. Start with reads. Good first prompts: "Summarize the last five activities on the Acme deal", "Which open deals in the Proposal stage have no activity in 14 days?", "List contacts at Acme and their last meeting."
4. Then allow logging. "Log a note on the Acme deal: call on Tuesday, budget approved, send contract draft." Check the note in HubSpot afterwards.
5. Keep publishing human. The server can publish landing pages and blog posts. Decide who may ask an AI to do that before someone does it by accident.
6. Restrict accounts where you can. HubSpot points out that Claude Enterprise admins can limit the connector to company-provisioned accounts with verified domain restrictions.

One more point for teams in the EU: whatever the AI client reads from HubSpot is processed by that client's AI provider. Your HubSpot data processing terms don't cover that leg, so check the AI provider's terms and your own records of processing before connecting customer data. HubSpot's ChatGPT listing also notes that chat in the connector is not currently available on the ChatGPT Pro plan for users in the EEA, Switzerland and the UK.

When the CRM itself has an MCP server

If you are choosing a CRM rather than connecting an existing one, an MCP server built into the CRM is the alternative. Customermates is one example: the endpoint at /api/v1/mcp is part of every cloud plan and of self-hosted installations. In Claude and ChatGPT you add it as a custom connector and sign in (setup guide); Claude Code, Codex, Cursor and Gemini CLI connect with an API key (CLI setup). A connected client discovers 59 tools, and you can narrow the set with a URL parameter, as described in the MCP reference.

Being able to delete and send cuts both ways. The Customermates server tells connected clients to ask for confirmation before deleting or sending, but that is guidance to the client, not a gate in the server: once an authorized client calls a tool, it runs. Check how your client handles tool approvals, and start with reads and drafts, the same as with HubSpot.

Cost works differently too. MCP is included on every plan, the free plan too with a rate limit; paid plans start at €12 per user per month, and the inbox tools need Pro at €29. An external AI client uses your own AI subscription, not Customermates credits. Customermates Cloud also has Mate, an in-app assistant that uses hosted AI credits, if you'd rather not connect an outside client at all (Mate documentation).

What your own agent does with it is follow-up. With LinkedIn and email connected on Customermates Cloud from Pro, client conversations sit on the client record when the contact details match or you link them, and Claude, ChatGPT or Mate drafts the reply and the next step for you to review and send. To try it, start your trial: 14 days of Pro with no credit card.

Customermates is the wrong pick if you rely on HubSpot's marketing tools, help desk or revenue objects; it has none of them. If you stay on HubSpot, use HubSpot's server. If you are weighing a switch, the HubSpot alternative comparison covers the trade-offs, and the Salesforce MCP guide explains the equivalent servers on Salesforce. To see how HubSpot's server compares with those of Pipedrive, Attio, Salesforce and the email providers, read the ranking of the best MCP servers for sales.

Frequently asked questions

Sources: HubSpot details checked on 8 October 2026 against the remote MCP server integration guide, the general availability changelog, the developer MCP setup guide, HubSpot's Claude connector page, HubSpot's ChatGPT connector listing, HubSpot AI tools and Zapier's HubSpot MCP page.