HubSpot MCP Agent Guide
HubSpot says its APIs and MCP server are live for agent-ready CRM workflows. Before you let Claude, ChatGPT, Gemini, Copilot, or a custom agent touch records, map every read and write action to scopes, consent, auditability, and HubSpot's updated developer terms.
Fast setup decision
Start with a private integration or approved connector for one customer, one object group, and one workflow. Expand only after the agent has proven it can read the right context, ask for approval before risky writes, and leave a clear audit trail.
Data access
Contacts, companies, deals, conversations, tickets, and activity need explicit scope review.
Action control
Create, update, delete, email, and workflow-trigger actions need separate guardrails.
Terms alignment
Agentic and MCP-based access is covered by HubSpot's developer terms.
HubSpot agent workflow map
| Workflow | Minimum access | Write guardrail | Approval rule |
|---|---|---|---|
| Deal risk review | Read companies, deals, owners, activities | Only add notes or tasks until validated | Human approval before changing stage or amount |
| Lead qualification | Read contacts, forms, conversations, lifecycle stage | Use allowlisted lifecycle transitions | Approve before enrolling in campaigns |
| Ticket triage | Read tickets, conversations, knowledge articles | Draft replies before sending | Auto-send only for low-risk categories |
| CRM cleanup | Read duplicate records and property history | Export merge plan before mutation | Approve every merge or delete batch |
Permission checklist before launch
- List every HubSpot object the agent can read.
- List every property the agent can write.
- Separate read-only analysis from write actions.
- Require human approval for deletes, merges, emails, deal-stage changes, and workflow enrollment.
- Store audit logs for prompt length, action type, record ID, user, and outcome without storing raw customer data in model logs.
- Document whether the integration is private, single-customer, or commercial multi-customer.
- Confirm that HubSpot data is not used to train, fine-tune, or improve external AI models unless a permitted exception applies.
Use the template version
If you need a one-page review artifact for a founder, customer, or implementation partner, use the checklist template. It turns the guide into review rows you can copy into Notion, Linear, or a client onboarding doc.
Open permission checklistFAQ
Is HubSpot MCP live?
HubSpot says its APIs and MCP server are live as part of its open agent-ready platform. Exact capabilities still depend on HubSpot account access, scopes, and the API surface available for the object or workflow you want to automate.
Can ChatGPT or Claude update HubSpot CRM records?
Yes, an agent can operate HubSpot only through authorized connectors, MCP access, APIs, or private integrations. Treat every write action as a scoped integration, not as a generic chat permission.
Can HubSpot API data be used to train an AI model?
HubSpot's May 4, 2026 developer changelog says it added a restriction on using API-accessed data to train, fine-tune, or improve AI or machine learning models, with a carve-out for legitimate single-customer use cases and an exemption for technology partners in good standing.
What should teams review before enabling a CRM agent?
Review scopes, object-level write permissions, user consent, audit logs, data retention, model-training restrictions, human approval for irreversible actions, and a rollback process for bad updates.