HubSpot MCP
Official HubSpot integration, in beta under HubSpot's Early Adopter Program terms.
Official HubSpot MCP — public beta. Contacts, companies, deals CRUD, activity history, engagement timelines. Community implementations add vector caching to overcome rate limits.
- Pull up a contact's full history before your next sales call
- Get a snapshot of your sales pipeline by deal stage
- Search for all companies in a specific industry in your CRM
Official HubSpot integration, in beta under HubSpot's Early Adopter Program terms. Lets AI clients read CRM data and create or update records — contacts, companies, deals, tickets, and associations — through natural language instead of the HubSpot API.
Sales and marketing teams using HubSpot CRM who want contact and deal data accessible from Claude.
https://www.npmjs.com/package/@hubspot/mcp-server
By HubSpot
How to Get It
npx -y @hubspot/mcp-server
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Once it’s connected, paste this into Claude:
Help me pull up a contact's full history before my next sales call
Trust Signals Reviewed
Not yet scanned. Learn how to check this tool yourself.
Data & Access
Community Pulse Active
Discussed on Hacker News, Reddit
- Maton MCP Server: Connect your SaaS tools like HubSpot and Salesforce — Reddit · 9 pts
- HubSpot MCP Server – Enables AI models to interact with HubSpot CRM data and ope — Reddit · 9 pts
- We tested the official HubSpot MCP Server; what are your thoughts? — Reddit · 5 pts
3 mentions across 1 sources
Reviewer notes
Reviewed review. These are observations, not a security certification.
audit 2026-07-05 stale-eval refresh: Scored from trust signals (evidence-eval-v1): 0 GitHub stars; contributors unknown; commit recency unknown; license MIT.
2026-04-02: LIMITATION: Still beta with intentionally limited scope — no Notes, Forms, or Meetings access. Write operations limited. Installation failures reported via Smithery CLI.
2026-03-29: SECURITY FINDING (JJ Englert, Mar 2026): Cowork connectors are scoped at the Anthropic account level, NOT the workspace level. A connector added in one Cowork workspace is accessible in ALL workspaces under the same Anthropic account. This means: (1) connectors with sensitive access (email, calendar, CRM) bleed across all projects/workspaces; (2) multi-tenant setups sharing an Anthropic account are NOT isolated at the connector level; (3) evaluate connector blast radius across the full account, not just the workspace being configured. Source: https://github.com/JJenglert1/getting-started-with-claude-cowork
Things to check
- Public beta with rate limits; community vector-caching workarounds suggest API throttling can block bulk operations. Requires HubSpot API credentials and appropriate user permissions.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
audit 2026-07-05 stale-eval refresh: Scored from trust signals (evidence-eval-v1): 0 GitHub stars; contributors unknown; commit recency unknown; license MIT.