Install command
Provided
Access and manage HubSpot CRM data including contacts, companies, and deals
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.
0
96
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as first-party.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
Package marked verified.
Checksum metadata
SHA-256 hash is present.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Install command
Provided
Config snippet
Provided
Copy snippet
Provided
Prerequisites
10 to clear
Platforms
4 listed
Difficulty
0/100
Adoption plan
Current risk score 0/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
Package verification/checksum metadata is available.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (6/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is present.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
6/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is available.
rollout
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
10 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.
Safety & privacy surface
1 safety and 1 privacy notes across 2 risk areas. Review closely: permissions & scopes.
{
"hubspot": {
"url": "https://mcp.hubspot.com/anthropic",
"transport": "http"
}
}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.
{
"hubspot": {
"url": "https://mcp.hubspot.com/anthropic",
"transport": "http"
}
}
Common usage pattern for this MCP server
Ask Claude: "Create a new contact for John Doe"
Common usage pattern for this MCP server
Ask Claude: "Update deal stage to closed-won"
Common usage pattern for this MCP server
Ask Claude: "Find all contacts from Microsoft"
Common usage pattern for this MCP server
Ask Claude: "Generate pipeline report"
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",
},
});
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 endpoints limited to 4 requests per second per token. Add 250ms delays between search operations. Consider caching search results to reduce API calls.
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).
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.
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%.
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.
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.
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.
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.
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 status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trust | Package verified | Package verified | Package verified | Package verified |
| Source provenanceDiffers | Source-backed | No submission link | No submission link | No submission link |
| Submitter | — | — | — | — |
| Install risk | Low risk | Low risk | Low risk | Low risk |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | ||||
| Category | mcp | mcp | mcp | mcp |
| Source | first-party | first-party | first-party | first-party |
| Author | HubSpot | Intercom | Monday.com | Asana |
| Added | 2025-09-18 | 2025-09-18 | 2025-09-18 | 2025-09-18 |
| Platforms | Claude CodeCodexCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓Scope 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 notes | ✓Contacts, 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 |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.