HubSpot MCP: connect HubSpot to ChatGPT, Claude or Copilot

What the HubSpot MCP server is

MCP (Model Context Protocol) is an open standard that lets an AI assistant use another tool on your behalf. HubSpot runs its own MCP server at https://mcp.hubspot.com. Through the server, an assistant can search records, read activities and, if you allow it, create and update records.

You rarely deal with the server itself. HubSpot has ready-made connectors for Claude, ChatGPT, Microsoft Copilot and Gemini, and all of them use this server. You only enter the server address yourself for your own agent or for an AI tool that has no HubSpot connector.

Two other things get mixed up with the HubSpot MCP server. HubSpot’s developer MCP server helps developers build apps and CMS themes; it doesn’t work with CRM data. And Breeze, HubSpot’s own AI inside HubSpot, was once called Breeze Copilot but has nothing to do with Microsoft Copilot.

HubSpot with ChatGPT, Claude or Copilot: what each can do

As of October 2026, Claude and ChatGPT read and change HubSpot records, and Microsoft 365 Copilot only reads. A HubSpot Super Admin approves the Claude and ChatGPT connectors; for Copilot, a Microsoft 365 admin installs the HubSpot agent.

HubSpot also shows up in the Microsoft 365 admin center as a pre-enabled Copilot connector, visible to everyone, before anyone has set it up. Admins find it under Copilot > Connectors > Your connections, where they can turn it off or release it to chosen groups first. As of October 2026, Microsoft has announced that MCP connectors will create, update and delete from Copilot.

What the AI can read and change in HubSpot

The assistant sees what the connected user sees in HubSpot, nothing more. If a sales rep may only view their own deals, ChatGPT or Claude only finds those deals for them.

• Nothing can be deleted. No connector deletes records or values, even with delete permissions granted. HubSpot says it will tell you and may ask you to reconnect if that changes. A wrong change has to be undone by hand.
• 10 records per write. Claude and ChatGPT create or update at most 10 records at a time. Larger changes belong in an import or a workflow.
• Sensitive Data hides activities. If Sensitive Data is turned on in your account, no assistant sees emails, calls, meetings, notes or tasks. Properties marked as sensitive stay hidden either way.
• Validation rules don’t always hold. Through Claude, HubSpot applies conditional property rules and pipeline stage rules. HubSpot’s ChatGPT page says that connector skips them. Association label rules apply in neither, so don’t count on rules to stop a wrong change.
• No workflows. Ask for a workflow or an email campaign and you get a draft to build yourself.
• Every change is on record. Creates and updates show in HubSpot’s audit log under the user and the connector, and in the record’s property history.

How to connect HubSpot to ChatGPT, Claude or Copilot

A HubSpot Super Admin approves the connector once for the account. Then each user connects their own assistant account and confirms the permissions in HubSpot.

1. Step 01

   Approve the connector in HubSpot

   As a Super Admin, go to Settings > Integrations > Connected Apps, tab “Approved apps”, and click “Approve apps”. Pick the HubSpot connector for your assistant and click Approve. Choose who may install it: admins only, specific users and teams, or everyone. Super Admins and users with App Marketplace Access can install it without approval.

   

2. Step 02

   Choose the data permissions

   Click “Next: Review data permissions”. The five required permissions only read companies, contacts, deals, tickets and account details. All optional permissions start switched off. “View only” switches on every read permission and leaves writing off; “All” adds writing. Your choice applies to every user, admins included. Then click “Approve app”.

   

3. Step 03

   Connect the assistant

   In Claude: Customize > Connectors, tab “Discover”, search for HubSpot and click “Connect to Claude”. In ChatGPT: Settings > Plugins, “Browse plugins”, HubSpot, “Install plugin” and “Sign in with HubSpot”. For Copilot, a Microsoft 365 admin opens Agents > All agents in the Microsoft 365 admin center, picks HubSpot, clicks Install and chooses the users. Users then open HubSpot under Agents in Copilot Chat, ask a question and click “Sign in to HubSpot”.

   

   

4. Step 04

   Pick the account and permissions

   Log in to HubSpot, choose the account and check the permissions on the page “Connecting HubSpot connector for … to HubSpot”. Each user can click “View-only” here, even if the admin approved more. Tick the terms and click “Connect app”. ChatGPT can hold several HubSpot accounts and names them all the same, so rename each one in the plugin settings.

   

5. Step 05

   Make every change ask first

   Claude asks before every write by default: read tools are set to “Always allow”, write and delete tools to “Needs approval”. Leave it that way. In ChatGPT, go to Settings > Plugins > Permissions and choose “Allow read tools”. The default “Allow low-risk tools” lets ChatGPT decide on its own what is low risk. When the assistant asks, click “Allow once”, not “Always allow”.

   

   

6. Step 06

   Test with one record

   Ask something you know the answer to, such as your five largest open deals by close date. Then let the assistant update one record. The assistant shows the change and asks first. Check the record’s property history in HubSpot: the change shows the connector as its source. Moving a deal to won also sets the close date to today, even if the assistant reports the old date.

   

   

   

Which permissions to give the AI

Give everyone read access and give write access to a few named people. A wrong answer is easy to spot. A wrong change to ten deals shows up weeks later in a report.

• Approve the connector before anyone asks. Otherwise users request it one by one, and someone approves the defaults in a hurry.
• Reconnect after every change. When a Super Admin adds a permission, users only get it after disconnecting and connecting again.
• Watch who can skip approval. Super Admins and users with App Marketplace Access connect without approval, external agencies included. Check “Installed by” under Connected Apps every month, as part of a portal audit.

GDPR and the works council

Once data leaves HubSpot, the assistant’s terms and your GDPR duties apply, not HubSpot’s. In Germany, Austria and Switzerland, settle the plan, the data and the purpose before the roll-out.

• Business plans only. HubSpot controls who may connect, not which assistant plan they use. Someone with a personal ChatGPT Plus or Claude Pro account can connect the company CRM to it. Use ChatGPT Business or Enterprise, Claude Team or Enterprise, or Microsoft 365 Copilot, each with a data processing agreement, and write that into your AI policy. Claude Enterprise can also block connections from accounts outside your domain.
• Training depends on the plan. ChatGPT Business and Enterprise don’t use connector data for training. On ChatGPT Free, Plus and Pro, OpenAI may use it to improve the connector unless the user opts out. Anthropic doesn’t train on data shared through HubSpot unless someone sends feedback or has opted in. Microsoft doesn’t train Copilot’s models on it.
• EU hosting ends at HubSpot. For an account hosted in the EU, requests run through HubSpot’s EU data centre. Where the assistant then processes the data is set by your contract with OpenAI, Anthropic or Microsoft.
• The works council has a say. An assistant that reads every colleague’s emails, calls and notes can be used to judge how people work. In Germany that needs co-determination (section 87(1) no. 6 BetrVG), in Austria a works agreement (section 96a ArbVG). Agree the purpose and the rules first.
• Add the assistant to your records of processing. The assistant is a new recipient of customer data. Name the assistant, its purpose and its vendor in your record of processing activities.
• Check Copilot even if you never planned it. HubSpot is pre-enabled as a Copilot connector, visible to everyone. Decide in the Microsoft 365 admin center whether it stays on.
• Read Microsoft’s consent before installing the agent. HubSpot’s agent for Copilot comes bundled with HubSpot’s Teams app. Installing it asks the admin to grant, for the whole organisation, access to call records, meeting recordings and transcripts, and all users’ profiles.

What the HubSpot MCP is good at, and where it stops

The HubSpot connectors are quick for questions about single records and short lists. The more records an answer needs, the less reliable the answer.

Use it for

• Call preparation. A summary of a contact, company or deal with the last emails, calls and open tasks.
• Notes after a meeting. Paste your notes and let the assistant log the note, create tasks and update the deal, once you’ve checked its proposal.
• Quick lists. Open deals without activity for 14 days, open tickets by priority, the contacts at one company.
• Patterns in the history. Common reasons in closed lost deals, recurring questions in the help desk, email drafts based on what was said before.

Don’t use it for

• Numbers you report. Totals over many records can be wrong: the connector reads up to 200 records per search and picks the properties itself. For pipeline totals and forecasts, use HubSpot reports. If you ask anyway, name the exact property and period and compare the result with a report.
• Bulk clean-ups. Ten records per write and no undo. Use an import, a workflow or the HubSpot API, with a backup first.
• Building the setup. Data model, pipelines, properties and automation need someone who knows how the business works. Let the AI list what exists and draft options; let a person decide.
• Several portals at once. Claude and Copilot connect one HubSpot account at a time. ChatGPT can hold several, but then asks which one you mean. Agencies keep one assistant account per client, or switch deliberately.

HubSpot MCP errors and how to fix them

These are the problems we see most often with the HubSpot connectors, what causes them and what fixes them.

How we set up AI assistants with HubSpot

Most teams already use ChatGPT or Claude, often on personal accounts. So we don’t start with the connector. We start with who uses what, and what the AI should be allowed to change.

1. Step 01

   Take stock

   Which assistants and plans people use, who is Super Admin or has App Marketplace Access, which connectors are already installed, and whether Sensitive Data is on.
2. Step 02

   Agree the rules

   Plan, purpose, read and write levels and the protected fields, agreed with the data protection officer and, where there is one, the works council.
3. Step 03

   Approve and connect

   The connector approved with only the permissions needed and write tools on “Needs approval”, then one short session per team with the questions people actually ask.
4. Step 04

   Check after a month

   Who connected, what was changed through the connector, and which answers didn’t match the reports.

Checklist before the first user connects

• Approve the connector for specific users and teams, not everyone.
• Approve “View only” first. Write permissions, once approved, apply to every user.
• In Claude, leave write tools on “Needs approval”. In ChatGPT, set Permissions to “Allow read tools”.
• Allow only ChatGPT Business or Enterprise, Claude Team or Enterprise, or Microsoft 365 Copilot, and write that into your AI policy.
• Decide whether HubSpot’s pre-enabled Copilot connector stays on.
• Agree the purpose with the data protection officer and, where there is one, the works council.
• Add the assistant to your record of processing activities.
• Check “Installed by” under Connected Apps every month.

Frequently asked questions