# HubSpot MCP server: connect Claude, ChatGPT and Claude Code

Canonical URL: https://www.martechdevs.com/blog/hubspot-mcp-server

By [Jafrin Akter Alo](https://www.martechdevs.com/authors/jafrin-akter-alo)

Data Engineer and Co-founder, martechdevs

Published: 2026-01-29

Last updated: 2026-10-02

HubSpot’s remote MCP server gives compatible AI applications access to supported HubSpot data and actions. Most users should begin with HubSpot’s official connector for their AI application. Developers can configure a custom connection. In either case, inspect the available tools and permissions, test a known CRM record and require review before changes that affect customers or workflows.

A connected assistant can prepare a pipeline review from HubSpot records. The quality of that review still depends on the pipeline, stage definitions, date filters and permissions it uses. Without those details, two reasonable prompts can produce two different totals.

Start with the report your team already checks. Our [CRM and lifecycle implementation work](https://www.martechdevs.com/crm-lifecycle) connects the data and rules behind that report so the assistant has a repeatable task to perform.

## Which HubSpot connection do you need?

Use the official end-user connector for normal CRM work in Claude or ChatGPT. Use a custom remote MCP connection when you are building an application or need a configuration the packaged connector does not provide.

HubSpot also has a local Developer MCP server. Its purpose is development work on the HubSpot platform. Confirm which product a tutorial describes before following its setup instructions.

HubSpot’s [Spring 2026 announcement](https://developers.hubspot.com/changelog/spring-2026-spotlight) confirms general availability of both servers and expanded remote-server access. That release established CRM write support for specified objects. The tool set has continued to change, so a launch announcement is useful history rather than a complete inventory of today’s capabilities.

Use this decision sequence:

![Choose a chat connector, an OAuth-based remote MCP connection, or local developer tooling according to the HubSpot task; inspect tools and account access for the first two paths.](https://www.martechdevs.com/assets/blog/hubspot-mcp-server.svg)

If you are still deciding what MCP adds, the [MCP guide for marketing teams](https://www.martechdevs.com/blog/what-is-an-mcp-server) explains the connection and its limits.

## How do you connect HubSpot to Claude?

Use Claude’s connector settings, then authorise the intended HubSpot account. HubSpot’s [Claude setup guide](https://knowledge.hubspot.com/integrations/set-up-and-use-the-hubspot-connector-for-claude) gives the current sequence:

1. Open Claude’s **Settings**, then **Connectors**.
2. Browse for HubSpot and choose **Connect**.
3. Sign in and select the HubSpot account.
4. Review the requested permissions and connect the app.
5. In the connector’s tool settings, set write tools to **Needs Approval** for a workflow that requires review.

Your HubSpot administrator may need to approve installation and data access first. HubSpot currently documents conditional property and pipeline-stage validation for the Claude connector, while association-label validation has a separate limitation. Check that behaviour in a test record if your workflow depends on it.

After connecting, ask for the current account and available capabilities before asking for analysis. Then retrieve a record you can already inspect in HubSpot. A correct record establishes that you are testing the right account and access path.

## How do you connect HubSpot to ChatGPT?

Find the official HubSpot integration in ChatGPT’s app or plugin directory, connect it and complete HubSpot authorisation. Workspace controls may require an administrator to enable it first.

OpenAI’s [connected apps guidance](https://help.openai.com/en/articles/11487775-connected-apps-in-chatgpt) explains that app permissions are separate from general settings such as retention and model-improvement choices. Review both for the workspace you use.

HubSpot maintains a separate [ChatGPT connector guide](https://knowledge.hubspot.com/integrations/connect-your-hubspot-account-to-chatgpt). Its available tools, upgrade steps and limits should be checked separately from the Claude integration. Client names on settings screens can change; use the official HubSpot listing and the current connection flow shown in your account.

Once connected, test the same CRM question you used in Claude or your existing report. Keep the input identical: account, object, date window and filters. If results differ, compare the returned records and tool scope before comparing the assistants’ explanations.

## How do you connect HubSpot to Claude Code?

Anthropic documents an HTTP connection for HubSpot in its [Claude Code MCP guide](https://code.claude.com/docs/en/mcp). A project-local starting configuration is:

```bash
claude mcp add --transport http hubspot --scope local https://mcp.hubspot.com/anthropic
```

Open Claude Code in the intended project, use `/mcp` to inspect the server and complete authentication when requested. Local scope makes the connection specific to that project for your user. Check your organisation’s managed settings if adding servers is restricted.

The `/anthropic` address is the client-specific route shown in Anthropic’s example. HubSpot’s custom-developer documentation uses its base server address. Follow the instructions for the connection you are building rather than swapping endpoints between tutorials.

Keep a short project reference describing the HubSpot account, permitted tasks, pipeline definitions and output format. Do not put client secrets or access tokens in that reference. The [context engineering guide](https://www.martechdevs.com/blog/context-engineering-marketing) shows how to organise operating instructions without loading unrelated company material.

## What if you need a custom remote connection?

HubSpot’s [developer setup documentation](https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server) currently uses **Development → MCP Connectors → Create MCP connector**. Configure the redirect URL for your client, then use the generated OAuth credentials with a client supporting PKCE. The base server address is `https://mcp.hubspot.com`.

After authorisation, run `get_user_details` to inspect account and tool access. HubSpot determines available scopes from the tools and permissions granted at installation; new scopes can require reinstalling the connector. Sensitive Data settings can block activity and conversation access.

For engineering acceptance, test the login flow, token refresh and revoked access. A connection that works immediately after setup may still fail after credentials expire. Save the implementation version and a repeatable connection test with the project.

## What can the assistant read or change?

The useful answer is the tool list available to your authenticated user. Subscription, permissions, account configuration and connector version can affect what appears.

HubSpot’s [Claude connector product page](https://www.hubspot.com/claude/connector) describes CRM record access, engagement history and actions such as creating tasks or updating records, with some capabilities tied to particular hubs or tiers.

Make a task-specific inventory rather than enabling everything for convenience:

- **Pipeline reporting:** deals, owners, stages and the relevant amounts and dates.
- **Account preparation:** company details and selected activity context.
- **Data hygiene review:** the properties and associations being checked.
- **Follow-up preparation:** the records that justify the task and the intended owner.

A content-publishing action has a different effect from a CRM lookup. A property update may trigger an existing workflow. Before allowing a write, identify the automation attached to the changed property and the communication it could start.

## What should your first prompt include?

Specify the object, business definition, time window, evidence and stop condition. That makes the result easier to check and gives the assistant less room to choose an unintended interpretation.

For example:

> Read the new-business pipeline for the last complete calendar month in our reporting time zone. Use deal creation date, exclude renewals and show total deal value by owner. List the included deal links and flag missing amounts or currencies. Show any retrieval limits. Make no changes.

Replace the business terms with your actual HubSpot configuration before using this. If renewals are not reliably labelled, the assistant should return that limitation instead of inventing an exclusion rule.

Save the successful prompt beside a manually checked output. That pair becomes a useful regression check after a connector or pipeline change.

## Which prompts are worth saving for recurring work?

These are starter prompts to adapt and test. Their feasibility depends on the tools and fields exposed in your connection. Start each session by confirming the account and requiring the assistant to report unavailable data.

### Pipeline and deal reviews

1. **Weekly creation:** “Show deals created in the last complete week in our new-business pipeline. Group by owner and include record links, amount, currency and missing-value counts.”
2. **Overdue close dates:** “Find open deals whose close date has passed. Show stage, owner, amount and last recorded activity. Make no updates.”
3. **Missing next steps:** “List open deals without a next activity. Show the fields used to determine that and separate unknown values.”
4. **Large deal preparation:** “Prepare a briefing for this deal using permitted CRM fields and activity history. Separate recorded facts from questions we still need answered.”
5. **Period comparison:** “Compare deal value created in these two equal date windows using identical filters. Show the deal sets behind each total.”

### CRM hygiene

6. **Owner gaps:** “Find companies in this saved scope without an assigned owner. Return the evidence and a proposed review list.”
7. **Duplicate candidates:** “Identify contacts sharing the same email address in this scope. Present candidates for review and make no merge decisions.”
8. **Stage requirements:** “Check these deals against our supplied stage-entry checklist. Flag missing evidence without moving any deal.”
9. **Association review:** “Find deals in this pipeline without an associated company. Report missing associations separately from retrieval failures.”
10. **Date consistency:** “Inspect these records for close dates before creation dates. Show both values and the record link.”

### Account and customer preparation

11. **Meeting brief:** “Summarise this company’s permitted deals, contacts and recent activities for a meeting. Cite the underlying records.”
12. **Renewal preparation:** “List accounts with the supplied renewal-date property in next month’s window. Flag accounts where that property is missing.”
13. **Support context:** “Summarise accessible tickets for this account. State any permissions or Sensitive Data limits affecting the result.”
14. **Contact coverage:** “For these target companies, show which of our defined buying roles have associated contacts. Use the role property we specify.”
15. **Evidence gaps:** “Review this account brief and identify statements the available HubSpot records cannot support.”

### Reviewable operational changes

16. **Task proposals:** “Prepare follow-up tasks for these approved deals. Show owner, due date, task text and reason before creating anything.”
17. **Property correction proposals:** “Compare these records with the approved reference file. Show current and proposed values, and wait for review.”
18. **Meeting note draft:** “Draft a CRM note from this supplied meeting summary. Keep decisions, questions and next actions separate.”
19. **Post-change check:** “Read back the records in this approved change list and compare their current values with the intended values.”
20. **Weekly exception brief:** “Combine the missing-owner, overdue-close-date and missing-next-step results. Preserve source links and avoid counting the same deal twice in the overall record count.”

The prompts ask for evidence because operational work needs a result someone can trace. They also keep “prepare” separate from “apply,” so a useful draft can be reviewed before it changes the CRM.

## Why do connected answers sometimes disagree with HubSpot reports?

The two views may be using different records, dates, permissions or aggregation rules. Compare those inputs before deciding that either total is wrong.

Common checks include:

- **Creation date versus close date:** these describe different business events.
- **Deal amount versus recurring revenue:** the properties may represent different measures.
- **Pipeline scope:** renewal and new-business deals may be mixed.
- **Currency:** adding amounts across currencies without conversion produces a misleading total.
- **Permissions:** the connected user may see a smaller record set.
- **Retrieval completeness:** pagination or tool limits may leave the answer partial.
- **Historical changes:** today’s stage value may not reproduce a past snapshot.

Ask the assistant to show the exact record set and calculation. If it cannot retrieve the history needed for a trend, use an approved historical dataset. Reconstructing the past from current fields needs explicit assumptions.

## Where does HubSpot alone run out of evidence?

It runs out when the question requires information that has not been brought into the CRM or is represented there differently from its source.

An account’s deal value does not automatically establish the amount it paid. A “customer” lifecycle stage does not tell you whether an invoice failed yesterday. A last-login property may say little about whether the customer reached the product’s activation milestone.

**Illustrative example:** a 15-person SaaS team asks for customers with declining usage and an upcoming renewal. HubSpot contains the account owner and renewal date, but usage sits in the product database. The team first defines a usage summary and matches product accounts to CRM companies. The assistant can then explain the joined result through an [internal MCP server](https://www.martechdevs.com/blog/internal-mcp-server).

Assume preparing this review manually takes 100 minutes each week. If the connected workflow needs 35 minutes of review and 15 minutes of average upkeep, it saves 50 minutes. At an assumed $60 an hour, that is $50 weekly before software costs. Measure those inputs during the pilot rather than treating the example as a benchmark.

## What should you check before using it routinely?

- [ ] The connection points to the intended HubSpot account.
- [ ] The authenticated user and available tools are recorded.
- [ ] A known record matches what the same user sees in HubSpot.
- [ ] A record outside the user’s permitted scope remains unavailable.
- [ ] The report’s pipeline, date, currency and exclusions are explicit.
- [ ] Missing values and partial retrievals appear in the answer.
- [ ] Write tools require the intended level of review.
- [ ] Existing HubSpot workflows have been checked for side effects.
- [ ] One disposable record has been used for any write test.
- [ ] The source record confirms the result of the test.
- [ ] The team knows how to disconnect and revoke access.

Use the broader [MCP security checklist](https://www.martechdevs.com/blog/mcp-security-checklist) before adding customer exports or actions that trigger external communication.

At Martechdevs, we build the data access, definitions and working instructions behind repeatable AI workflows. Start with the [free martech AI audit](https://www.martechdevs.com/martech-ai-audit), or explore an [AI assistant built around your approved workflows](https://www.martechdevs.com/custom-martech-ai-agent).

## Frequently asked questions

### Does HubSpot have an official MCP server?

Yes. HubSpot provides a remote server for supported account data and a separate local server for developer work. Use the remote connector path for the CRM workflows described here.

### What is the HubSpot MCP server URL?

HubSpot documents its base remote address as `https://mcp.hubspot.com`. Anthropic’s Claude Code example uses `https://mcp.hubspot.com/anthropic`. Follow the documented route and authentication flow for your client.

### Why are expected scopes or tools missing?

Check the installed connector version, granted permissions, subscription and account configuration. Compare a missing capability with the current documentation for that specific connector. If a scope was added after installation, the connection may need a fresh authorisation flow.

### Can it calculate MRR from my deals?

Only if the available data and agreed calculation support that measure. Deal amount, subscription value and paid revenue can differ. For subscription reporting, start with the billing model and the account mapping covered in our [Stripe and HubSpot guide](https://www.martechdevs.com/blog/stripe-hubspot).

### Does it cost anything?

Separate the HubSpot subscription, the AI application’s plan and any custom hosting or implementation work. Available capabilities can depend on the product tier. Check the current connector and plan documentation before assuming that an existing licence covers the whole workflow.

## Sources

1. HubSpot, [Spring 2026 Spotlight](https://developers.hubspot.com/changelog/spring-2026-spotlight), 2026.

2. HubSpot, [Set up and use the HubSpot connector for Claude](https://knowledge.hubspot.com/integrations/set-up-and-use-the-hubspot-connector-for-claude), updated September 2026.

3. OpenAI, [Connected apps in ChatGPT](https://help.openai.com/en/articles/11487775-connected-apps-in-chatgpt), current documentation, accessed October 2026.

4. HubSpot, [Set up and use the HubSpot connector for ChatGPT](https://knowledge.hubspot.com/integrations/connect-your-hubspot-account-to-chatgpt), current documentation, accessed October 2026.

5. Anthropic, [Connect Claude Code to tools via MCP](https://code.claude.com/docs/en/mcp), current documentation, accessed October 2026.

6. HubSpot, [Integrate AI tools with the HubSpot MCP server](https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server), updated September 2026.

7. HubSpot, [HubSpot connector for Claude](https://www.hubspot.com/claude/connector), product documentation, accessed October 2026.