Skip to main content
mcpFirst-partyLow risk Safety Privacy
HubSpot logo

Hubspot MCP Server for Claude

Access and manage HubSpot CRM data including contacts, companies, and deals

HarnessClaude CodeCodexCursorClaude Desktop

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://developers.hubspot.com/ai-tools/mcp, https://github.com/JSONbored/awesome-claude/blob/main/content/mcp/hubspot-mcp-server.mdx
Brand
HubSpot
Brand domain
hubspot.com
Brand asset source
brandfetch
Package URL
/downloads/mcp/hubspot-mcp-server.mcpb
Package SHA256
a3d5e18765768e67f645b91f89c67d7163ebb763932652f693d85d1a260949c8
Safety notes
Scope HubSpot CRM permissions and test writes against non-critical objects before enabling contact, company, or deal updates.
Privacy notes
Contacts, companies, deals, tickets, communication history, and CRM metadata may be exposed through tool calls.
Author
HubSpot
Claim status
unclaimed
Last verified
2025-09-18

Decision playbook

Ready to evaluate for your workflow

Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.

Compare context
Selected

0

Current score

96

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as first-party.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Complete

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    Package marked verified.

    Done
  • Checksum metadata

    SHA-256 hash is present.

    Done

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Package install

Copy-ready — paste the snippet to get started.

2 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

10 to clear

Platforms

4 listed

Difficulty

0/100

Adoption plan

Balanced adoption plan

Current risk score 0/100. Use staged verification before broader rollout.

Risk 0

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    Package verification/checksum metadata is available.

    Done

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (6/6 signals complete).

Risk 0

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Present

Package integrity metadata is present.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

6/6 steps complete with no blocking gaps for this preset.

Risk 0

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is available.

Done

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

10 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.

0/10 ready
Account & credentials4Install & runtime1Network & hosting2Review & approval2General12 minutes

Safety & privacy surface

Safety & privacy surface

1 safety and 1 privacy notes across 2 risk areas. Review closely: permissions & scopes.

2 areas
  • SafetyPermissions & scopesScope HubSpot CRM permissions and test writes against non-critical objects before enabling contact, company, or deal updates.
  • PrivacyData retentionContacts, companies, deals, tickets, communication history, and CRM metadata may be exposed through tool calls.

Safety notes

  • Scope HubSpot CRM permissions and test writes against non-critical objects before enabling contact, company, or deal updates.

Privacy notes

  • Contacts, companies, deals, tickets, communication history, and CRM metadata may be exposed through tool calls.

Prerequisites

  • HubSpot account (sign up at https://www.hubspot.com if needed)
  • OAuth authentication support (required for secure access to HubSpot CRM data)
  • HTTP transport support (remote MCP server at https://mcp.hubspot.com/anthropic)
  • Internet connection (remote HubSpot API access required)
  • Understanding of HubSpot API rate limits (110 requests per 10 seconds for OAuth apps, 4 requests per second for Search API)
  • Understanding of OAuth scopes (contacts access for contacts, content access for deals)
  • Understanding of CRM concepts (contacts, companies, deals, pipeline stages)
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • Understanding of data privacy regulations (GDPR, CCPA compliance when handling customer data)
  • Understanding of error rate management (keep error rate below 5% for marketplace compliance)

Schema details

Install type
package
Reading time
1 min
Difficulty score
0
Troubleshooting
Yes
Breaking changes
No
Package metadata
Package verified
Yes
SHA-256
a3d5e18765768e67f645b91f89c67d7163ebb763932652f693d85d1a260949c8
Collection metadata
Estimated setup
2 minutes
Difficulty
beginner
Full copyable content
{
  "hubspot": {
    "url": "https://mcp.hubspot.com/anthropic",
    "transport": "http"
  }
}

About this resource

Content

Seamlessly connect Claude to your HubSpot CRM to manage contacts, companies, and deals through natural language commands. Create and update CRM records, search customer data, track sales pipeline progress, and generate comprehensive reports—all while maintaining proper data privacy and compliance standards.

Features

  • Fetch and update contact records
  • Manage companies and deals pipeline
  • Create and update CRM records
  • Search CRM data with filters
  • Generate sales and marketing reports
  • Advanced HubSpot CRM and marketing automation with contact management, deal tracking, and campaign analytics
  • Batch operations support for efficient bulk contact operations, deal management, and marketing automation with automatic rate limit handling and retry logic
  • Real-time CRM synchronization capabilities with webhook integration support for monitoring HubSpot events and triggering automated workflows

Use Cases

  • Update contact information in bulk
  • Create new deals in the pipeline
  • Track sales pipeline progress
  • Generate customer reports and insights
  • Manage marketing lists and segments
  • Build automated CRM workflows that sync external systems with HubSpot for real-time customer relationship management and marketing automation

Installation

Claude Code

  1. claude mcp add --transport http hubspot https://mcp.hubspot.com/anthropic
  2. Authenticate with your HubSpot account when prompted (OAuth flow)
  3. Verify installation: claude mcp list
  4. Test connection: claude mcp status hubspot

Claude Desktop

  1. Open your Claude Desktop configuration file (see configPath below)
  2. Add the HubSpot server configuration with HTTP transport pointing to https://mcp.hubspot.com/anthropic
  3. Restart Claude Desktop
  4. Authenticate with your HubSpot account when prompted (OAuth flow will open in browser)

Requirements

  • HubSpot account (sign up at https://www.hubspot.com if needed)
  • OAuth authentication support (required for secure access to HubSpot CRM data)
  • HTTP transport support (remote MCP server at https://mcp.hubspot.com/anthropic)
  • Internet connection (remote HubSpot API access required)
  • Understanding of HubSpot API rate limits (110 requests per 10 seconds for OAuth apps, 4 requests per second for Search API)
  • Understanding of OAuth scopes (contacts access for contacts, content access for deals)
  • Understanding of CRM concepts (contacts, companies, deals, pipeline stages)
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • Understanding of data privacy regulations (GDPR, CCPA compliance when handling customer data)
  • Understanding of error rate management (keep error rate below 5% for marketplace compliance)

Configuration

{
  "hubspot": {
    "url": "https://mcp.hubspot.com/anthropic",
    "transport": "http"
  }
}

Examples

Create a new contact for John Doe

Common usage pattern for this MCP server

Ask Claude: "Create a new contact for John Doe"

Update deal stage to closed-won

Common usage pattern for this MCP server

Ask Claude: "Update deal stage to closed-won"

Find all contacts from Microsoft

Common usage pattern for this MCP server

Ask Claude: "Find all contacts from Microsoft"

Generate pipeline report

Common usage pattern for this MCP server

Ask Claude: "Generate pipeline report"

Create Contact with Properties

Create a new HubSpot contact with email and custom properties

// Create HubSpot contact with custom properties
const contact = await hubspot.contacts.create({
  properties: {
    email: "contact@example.com",
    firstname: "John",
    lastname: "Doe",
    company: "Example Corp",
  },
});

Security

  • OAuth authentication for secure access
  • Respect data privacy regulations
  • Monitor API usage and limits
  • Regular data audits recommended
  • HubSpot API keys and private app access tokens must be securely stored and never exposed in client-side code or public repositories - use environment variables and secure credential management
  • HubSpot OAuth access tokens should be used for third-party integrations to ensure proper access control, token lifecycle management, and automatic token refresh
  • HubSpot contact, deal, and company IDs may expose customer data and business information - ensure HubSpot resource identifiers are kept private and not shared in public configurations
  • Rate limiting and API quota management are critical for HubSpot MCP servers - implement proper rate limit handling, retry logic, and quota monitoring to prevent service disruption
  • HubSpot webhook configurations and payloads may contain sensitive customer data and business information - ensure webhook endpoints are properly secured with authentication and HTTPS encryption

Troubleshooting

HTTP 429 error: rate limit exceeded on API calls

OAuth apps limited to 110 requests per 10 seconds per account. Wait for rate limit window to reset. Implement throttling with max 11 requests/second to stay within burst limit.

Search API hitting rate limit with only few requests

Search endpoints limited to 4 requests per second per token. Add 250ms delays between search operations. Consider caching search results to reduce API calls.

HTTP 401 unauthorized - OAuth token invalid

Check access token expiration (look at expires_in parameter). Re-authenticate to get new OAuth token. Verify token has correct scopes for HubSpot API access (contacts, deals, etc).

HTTP 403 forbidden when accessing CRM objects

Verify OAuth token has required scopes. Contacts access needed for contacts, content access for deals. Check account permissions in HubSpot settings and re-authenticate with correct scopes.

Error rate exceeds 5% causing marketplace issues

Reduce failed requests by implementing proper error handling. Validate input before API calls. Check API responses and fix 4xx errors in your code to lower error rate below 5%.

HubSpot MCP server authentication errors with API keys

Verify API key is valid and not expired. Check API key permissions match required operations. Ensure API key format is correct (Bearer token in Authorization header). For OAuth integrations, verify token refresh logic is working correctly.

HubSpot rate limit errors when processing multiple requests

Implement exponential backoff retry logic with jitter. Use HubSpot API rate limit headers to monitor usage. Reduce concurrent requests. Cache frequently accessed contact data. HubSpot allows 100 requests per 10 seconds per API key.

HubSpot contact or deal access denied errors

Verify API key has access to the contact or deal. Check account permissions and user role. Ensure API key has required scopes (contacts, deals, companies) for target operations.

HubSpot MCP server connection timeouts or network errors

Check network connectivity and firewall settings. Verify HubSpot API endpoints are accessible. Increase request timeout values. Implement connection pooling and retry mechanisms with exponential backoff.

Source citations

Add this badge to your README

Show that Hubspot MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/hubspot-mcp-server.svg)](https://heyclau.de/entry/mcp/hubspot-mcp-server)

How it compares

Hubspot MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Source provenance).

Field

Access and manage HubSpot CRM data including contacts, companies, and deals

Open dossier

Access customer conversations, tickets, and user data in real-time

Open dossier

Manage monday.com boards, items, and CRM activities

Open dossier

Interact with Asana workspaces to manage projects and tasks

Open dossier
Next steps
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage verifiedPackage verifiedPackage verifiedPackage verified
Source provenanceDiffersSource-backedNo submission linkNo submission linkNo submission link
Submitter
Install riskLow riskLow riskLow riskLow risk
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
BrandHubSpot logoHubSpotIntercom logoIntercomMonday.com logoMonday.comAsana logoAsana
Categorymcpmcpmcpmcp
Sourcefirst-partyfirst-partyfirst-partyfirst-party
AuthorHubSpotIntercomMonday.comAsana
Added2025-09-182025-09-182025-09-182025-09-18
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo
Safety notesScope HubSpot CRM permissions and test writes against non-critical objects before enabling contact, company, or deal updates.Restrict Intercom workspace access and review outbound message or ticket changes before using it on live customer support data.Scope the Monday API token to intended boards and review item, CRM, or automation changes before using live workflows.Use a least-privilege Asana token and test task or project writes in a non-critical workspace before connecting production workflows.
Privacy notesContacts, companies, deals, tickets, communication history, and CRM metadata may be exposed through tool calls.Customer conversations, emails, user profiles, tickets, company records, and support metadata may be sent through model context.Board items, CRM records, comments, custom fields, users, and workspace automation metadata may be sent through tool calls.Asana task text, project metadata, comments, assignees, due dates, and workspace details may be sent through model context.
Prerequisites
  • HubSpot account (sign up at https://www.hubspot.com if needed)
  • OAuth authentication support (required for secure access to HubSpot CRM data)
  • HTTP transport support (remote MCP server at https://mcp.hubspot.com/anthropic)
  • Internet connection (remote HubSpot API access required)
  • Intercom workspace account (sign up at https://www.intercom.com if needed)
  • Intercom Access Token (for private apps) or OAuth credentials (for public apps) - get from Intercom Developer Hub
  • HTTP/SSE transport support (remote MCP server at https://mcp.intercom.com/sse)
  • Internet connection (remote Intercom API access required)
  • monday.com workspace account (Member role required, not Guest)
  • Personal V2 API token (generate from Developer Center or Administration tab) or OAuth credentials for hosted service
  • SSE transport support (remote MCP server at https://mcp.monday.com/sse or local npx installation)
  • Internet connection (remote monday.com API access required)
  • OAuth 2.0 authentication (required for MCP server via SSE transport)
  • Asana account with access to at least one workspace
  • Workspace membership with Member role or higher (Guest role insufficient for task creation)
  • Internet connection for accessing Asana API (https://app.asana.com)
Install
claude mcp list && claude mcp status hubspot
claude mcp list && claude mcp status intercom
claude mcp list && claude mcp status monday
claude mcp list && claude mcp status asana
Config
{
  "mcpServers": {
    "hubspot": {
      "url": "https://mcp.hubspot.com/anthropic",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "intercom": {
      "url": "https://mcp.intercom.com/sse",
      "type": "sse"
    }
  }
}
{
  "mcpServers": {
    "monday": {
      "url": "https://mcp.monday.com/sse",
      "type": "sse"
    }
  }
}
{
  "mcpServers": {
    "asana": {
      "url": "https://mcp.asana.com/sse",
      "type": "sse"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.