MCP field guide / HubSpot
// mcp field guide · crm
A CRM MCP where the two edges you'd brace for are both absent: there's no delete/archive tool, and no way to send email or messages to customers (email tooling is drafts only). So the real risk isn't a deletion or a rogue send — it's a bulk mutation quietly overwriting many live customer records with no undo. Here's the sourced read.
GUARD FIT · READS
PASS-THROUGHSearch/get contacts, companies, deals, tickets, properties, campaign analytics — the majority of calls, no state change.
GUARD FIT · BULK / RECORD WRITES
MODERATE→STRONGBatch create/update can overwrite dozens–hundreds of customer records at once, with no version history and no undo.
Overall fit: MODERATE → STRONG — concentrated on bulk mutations; there are no deletes or sends to guard.
HubSpot ships two official variants: a remote hosted server at mcp.hubspot.com (GA since Apr 2026, OAuth 2.1 + PKCE, all plans) and a local beta (@hubspot/mcp-server v0.4.0, MIT, private-app token). Both let an agent read and write CRM data — contacts, companies, deals, tickets, engagements (notes, tasks, calls, meetings, logged emails), associations and properties — scoped to the authenticated user's existing HubSpot permissions.12
| Tier | Tools |
|---|---|
| read-only | search_crm_objects/get_crm_objects, get_user_details, search_properties/get_properties, search_owners, campaign analytics, search_conversations (local: hubspot-search-objects, hubspot-list-associations, etc.) |
| mutating | manage_crm_objects (create/update contacts, companies, deals, tickets, activities); batch: hubspot-batch-create-objects/hubspot-batch-update-objects; manage_properties; "Manage marketing email" = draft create/update/clone only |
| destructive | none exposed — no delete/archive tool, and no customer-facing send |
The two absences (verified against both the npm README and the remote-server docs): (1) no delete or archive tool in either variant — CRM record deletion isn't available through the official MCP, so the usual archive-vs-permanent question is moot here. (2) no customer-facing send — marketing email is limited to drafts, conversations are read-only, so the "irreversible sent email" scenario isn't reachable through the official tools today. If HubSpot later ships a send/publish tool, that jumps to strong.
Sales intelligence in chat. "Summarize all deals in 'Decision maker bought in' > $1,000" or "summarize the last five tickets for Alex Smith" — read/search over the pipeline.
Record hygiene. Create a contact and associate it to a company, or update an address — mutating writes to customer records.
Follow-up orchestration. Add a task or note to a contact/deal, list overdue tasks — engagement writes.
Reads → pass through. They dominate and are low-risk.
Writes touch live customer records → moderate-to-strong. manage_crm_objects and the batch tools overwrite contacts, companies, deals and tickets with no version history and no undo. The single sharpest edge is bulk mutation — one batch call fanning out across dozens or hundreds of records — exactly where an impact diff plus one approval earns its keep.
Honest, in both directions: we're not going to invent a scary delete or a rogue-send scenario — neither exists on this server. The genuine risk is a property overwrite at scale. And note the compensation asymmetry: a created record is cleanly reversible (create → delete/archive via API), but an update is only compensable if the pre-image was captured first — HubSpot's MCP won't hand you a rollback. That's the compensation-is-not-undo line for CRM data: gate the bulk write, and snapshot before you overwrite.
ChronoMCP passes HubSpot reads through and holds bulk create/update for a human — with an honest note that overwrites need a pre-image to be reversible.
Read the quickstart → More MCP profiles@hubspot/mcp-server (local beta, v0.4.0, tool table): npmjs.com/package/@hubspot/mcp-serverProfiles describe third-party software from its public sources; ChronoMCP is not affiliated with HubSpot. A few remote tool names appear as display labels in the docs and may differ from literal identifiers; the GA toolset is expanding. Risk groupings are our classification. Sources current as of Aug 2026 — check the source links.