Official (Vendor)★ 4.3by HubSpot

HubSpot

HubSpot's MCP for CRM workflows: contacts, deals, tickets, properties. Distributed via NPM, see the developer docs for install steps.

Homepage

Safety & Trust

Delv Safety Grade: B

Score 74/100 · assessed 2026-04-28

Maintainer92

Permissions65

Supply chain70

Transparency62

Incidents100

HubSpot's official MCP server connects Claude to your CRM data with read and write access across contacts, companies, deals, tickets, and custom properties. The maintainer score is excellent because HubSpot is a major SaaS vendor with established security practices. Permissions are moderately scoped: you get full CRM read/write which is broad but domain-specific, not arbitrary system access. The supply chain score reflects NPM distribution but lacks visible repository or pinned dependency information in the provided metadata. Transparency is adequate with official docs but no public repo link means you cannot audit the code or review issues. The access token requirement is standard OAuth practice. No known security incidents. This is a solid enterprise integration for teams already committed to HubSpot, though the closed-source nature and broad CRM write permissions warrant careful token scoping.

Lethal Trifecta (prompt-injection exposure)

TRIFECTA RISK

All three axes present. This server can read private data, ingest attacker-controlled content, and send data outbound. A poisoned input (a GitHub issue, an email, a webpage) can exfiltrate secrets via this chain. Only install with auditing; avoid on shared or cloud agents.

Private dataYes

Reads secrets, credentials, private files

Untrusted inputYes

Ingests web pages, PRs, issues, emails

External commsYes

Can send data outbound

Same trifecta shape as attio. Marketing automation surface adds breadth on the outbound axis.

Green flags

Official vendor-maintained server from established SaaS company
Domain-specific CRM permissions, not arbitrary system access
Standard OAuth token authentication pattern
NPM distribution suggests professional packaging
No known security incidents or CVEs

Red flags

No public repository link provided for code audit
Broad write access across entire CRM (contacts, deals, tickets, properties)
Access token grants full account permissions without granular scoping
Closed-source implementation limits security review

Permissions requested

Outbound networkAccess secretsDB readDB writeIdentity readIdentity write

Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Review

HubSpot's official MCP server plugs your CRM straight into Claude. You get read and write access to contacts, companies, deals, tickets, and custom properties without leaving your editor or chat. The value proposition is simple: if you're already running sales or support ops in HubSpot, this lets you query deal stages, update contact fields, or pull ticket histories in natural language instead of clicking through tabs. I'd reach for this when I'm triaging support tickets and need to cross-reference a contact's deal history, or when I'm prepping for a call and want to surface recent activity without opening the HubSpot UI. It's particularly good for batch operations: "Find all contacts in the trial stage who haven't been contacted in two weeks" becomes a single prompt instead of a saved filter and export dance. The server respects HubSpot's property schema, so you can work with custom fields if your org has built them out. The setup assumes you've already got a HubSpot account with API access. You'll need to generate a private app token with the right scopes, which means navigating HubSpot's settings if you're not an admin. The server itself is straightforward once the token is in place, but there's no hand-holding around scopes or permissions errors. If your token lacks the right access, you'll get opaque failures until you figure it out. This isn't a replacement for the HubSpot UI if you're doing heavy configuration work or building workflows. It's a query and update layer, not a full admin console. If you're not already living in HubSpot day-to-day, the setup overhead probably isn't worth it. But for teams who are deep in the CRM and want to surface data or make updates without context-switching, it's a legitimate time-saver. The official vendor status means it's likely to stay in sync with HubSpot's API changes, which matters if you're relying on it for production workflows.

Verdict

Install this if you're already running sales or support ops in HubSpot and spend time juggling tabs to cross-reference CRM data. Skip it if you're not a daily HubSpot user or if you don't have admin access to generate API tokens. It's a solid utility for the niche it serves, not a general-purpose tool.

Good at

Official vendor support means it tracks HubSpot's API changes without you chasing updates.
Handles custom properties and objects if your org has built them, not just the default schema.
Batch queries and updates that would take multiple clicks in the UI collapse into single prompts.
Works across contacts, companies, deals, and tickets in one server instead of fragmented integrations.

Watch out

Requires admin or developer access to generate a private app token, which blocks non-technical users.
Scope and permission errors surface as generic failures, so expect some trial and error during setup.
Not a replacement for HubSpot's UI if you need to configure workflows or build automation.
Only useful if you're already deep in HubSpot; the setup overhead isn't justified for casual CRM users.

Getting started

1. Generate a private app access token in HubSpot (Settings > Integrations > Private Apps) with scopes for contacts, deals, tickets, and any custom objects you need. 2. Add the server to your Claude Desktop config with `HUBSPOT_ACCESS_TOKEN` set to your token. The repo README has the exact JSON snippet. 3. Restart Claude Desktop and verify the server appears in the MCP tools list. Try a simple query like "List my recent deals" to confirm it's working. 4. Watch out for scope errors: if you get permission failures, go back to your private app settings and enable the missing scopes. 5. Start with read-only queries until you're confident in the syntax, especially if you're working with production data.

Works with

Claude DesktopClaude CodeCursor