The HubSpot MCP server lets Claude, Cursor, ChatGPT, and AI agents read and act inside HubSpot. Here's the official setup, the real security risks, and how to deploy it with DLP-grade redaction at the MCP layer.
The HubSpot MCP server is a Model Context Protocol implementation that exposes HubSpot's API as a standardized set of tools to AI agents. Once connected, an agent like Claude can perform CRM search, contact get, company get, engagement list on the authenticated user's behalf — turning HubSpot's API surface into AI-actionable capabilities.
Refer to the official HubSpot MCP server documentation for the current tool list, OAuth scopes, and rate-limit behavior. The setup pattern is consistent with other MCP integrations: an OAuth client ID/secret, a custom connector in Claude (or another MCP-aware AI client), and the server starts serving tool calls.
From the user's perspective, the AI agent suddenly knows their HubSpot. From the security perspective, the AI agent now has read access — and often write access — to every record the user can touch in HubSpot.
That's the value. It's also where security teams need a control layer.
The risks fall into four categories that every healthcare, fintech, and enterprise security team should price into the deployment.
1. Every CRM record is PII. HubSpot Contacts and Companies are personal data by definition. search_crm and get_contact return names, emails, phone numbers, addresses, and every custom property to the agent.
2. Engagement history is a deep PII archive. list_engagements returns logged emails, call transcripts, and meeting notes — years of customer correspondence, much of it regulated.
3. Deal notes hold financial data. Sales reps paste pricing, contract terms, bank details, and card-on-file references into deal notes. The agent reads them all.
4. List exports multiply the exposure. A single tool call backed by a HubSpot list can return thousands of contact records — a bulk PII pull with no inspection in the path.
The traditional DLP a company already runs — at the network edge, on the file share, inside the SaaS-native rule engine — does not sit in the MCP path. The tool response goes straight from HubSpot into the AI agent's context window. That gap is where Strac HubSpot MCP DLP lives.
Strac's HubSpot MCP DLP sits between AI agents and the HubSpot MCP server. Every tool call passes through Strac's MCP-layer inspection before content reaches the AI agent's context window. Sensitive content is redacted, tokenized, or vaulted depending on policy. Non-sensitive content flows through untouched.
What this looks like in practice:
The same Strac MCP DLP layer covers Claude Cowork, Slack MCP, and other surfaces — one control plane across every place AI agents touch your regulated data.
MCP DLP protects the AI-agent surface. Strac's native HubSpot DLP protects the direct-user surface — the same HubSpot workspace, but inspected at the point where humans share, upload, send, and grant access. Most enterprises run both: native DLP for the user-driven actions, MCP DLP for the agent-driven actions. Together they cover every path regulated data can take in and out of HubSpot.
What Strac's native HubSpot DLP includes:
Deep dives and integration pages:
For the broader integration catalog — every SaaS, cloud, browser, and endpoint surface Strac covers — see strac.io/integrations.
The screenshot below shows Strac's MCP DLP redacting sensitive data from a real Claude session — patient identifiers, customer emails, and credit card numbers tokenized inline before the model received the prompt. The same inspection pattern runs on every HubSpot MCP tool call routed through Strac.
Setup is agentless and takes under 10 minutes.
.webp)
json
"mcpServers": {
"hubspot": {
"url": "https://mcp.strac.io/hubspot",
"auth": { "type": "bearer", "token": "<your-strac-token>" }
}
}
For Cursor, OpenAI Agents, custom agents — same endpoint, same auth.The same Strac HubSpot MCP DLP control produces evidence mapped to every major compliance framework.
For the broader AI-data-governance program this sits inside, see the AI Data Governance framework.
The HubSpot MCP server is a Model Context Protocol implementation that lets AI agents (Claude, Cursor, ChatGPT, Perplexity, custom agents) read and act inside HubSpot via standardized tool calls. It's how an AI assistant gets contextual access to every Contact, Company, Deal, Ticket, engagement, and note the authorizing app scope can read.
By itself, no — not without an additional DLP layer. The HubSpot MCP server honors the authorizing user's permissions but returns whatever that user can see, including PII, PHI, credentials, source code, and other regulated content. For enterprise use with regulated data, you need an MCP-layer DLP control like Strac HubSpot MCP DLP that inspects and redacts every tool response before content reaches the AI model.
HubSpot's built-in protections operate at the storage and policy layer — sensitivity labels, retention policies, native DLP rules at posting/sharing time. None of those sit in the MCP tool-call path by default. Strac is purpose-built for the MCP layer: it inspects every tool response before content reaches the AI agent's context window, with detection breadth (PII / PHI / PCI / secrets / source code / OCR-in-images) that goes well beyond most native rule engines.
Yes. Strac exposes a standard MCP endpoint, so any MCP-aware AI client routes tool calls through it with one configuration change. No SDK changes, no application code changes.
PII (SSN, driver's license, passport, address, phone, email), PHI (clinical notes, MRN co-occurrence, ICD-10 codes adjacent to identifiers, lab values), PCI (full and partial card numbers via Luhn check), credentials (API keys, AWS / GCP / Azure access keys, OAuth tokens, JWTs, SSH keys, private keys — 48+ patterns), proprietary content (M&A keywords, source code fingerprints), and custom detectors trained on your internal data classifications. Detection runs across text, files, images (OCR), and structured fields.
Under 10 minutes for the first workspace. OAuth Strac into HubSpot, paste the Strac MCP endpoint into your AI client's config, pick a policy template, done. No agents to install, no HubSpot re-permissioning, no application code changes.
Redacted content is replaced inline in the tool response. Optionally, sensitive content can be vaulted — replaced with a short-lived retrieval link that only authorized users can resolve, so the original data is retrievable for legitimate use without ever entering the AI context. Vaulted data is stored encrypted at rest in your Strac tenant; you control retention.
Yes. Strac produces a per-call audit log: timestamp, AI client identity, user, tool invoked, resource accessed, data classes detected, redactions applied, vault references, disposition. The log is queryable in the Strac console and exportable to your SIEM. This is the evidence trail SOC 2, HIPAA, PCI, and GDPR auditors will ask about for AI-agent activity in HubSpot.
The HubSpot MCP server is rapidly becoming the way AI agents read into HubSpot. That surface contains every category of regulated and proprietary data your organization has. Running HubSpot MCP in 2026 without an MCP-layer DLP control is not a question of if the first incident reaches your security team; it's when.
Strac HubSpot MCP DLP gives you the protection layer, the audit evidence, and the framework-agnostic compliance coverage so you can let your team use HubSpot with Claude, Cursor, Cowork, ChatGPT, and any future AI client without making each one a separate security exception.
If you are running — or about to run — HubSpot MCP in production, book a 30-minute demo. We'll walk through the architecture, the policy templates, and a deployment plan for your specific HubSpot workspace and AI clients.
For the broader MCP DLP control plane across every SaaS surface, see the MCP DLP pillar. For more SaaS-specific deep dives: Slack MCP, Google Workspace MCP, Gmail MCP, Google Drive MCP, Microsoft 365 MCP, Notion MCP, Jira MCP.
.avif){kind=icon}
.gif)
