If you're searching for "HubSpot MCP", you're asking one of two things: does HubSpot have an MCP server? or how do I connect HubSpot to an AI assistant via the Model Context Protocol?
✅ HubSpot has an official MCP server. Details in the setup section below.
What Is MCP?
Model Context Protocol (MCP) is an open standard developed by Anthropic that lets AI assistants — like Claude — connect to external tools, APIs, and data sources in a standardised way.
Before MCP, every AI integration required bespoke tooling: custom prompts, custom API wrappers, and custom glue code to pass context back and forth. MCP replaces that with a common interface: the AI asks the MCP server for data or actions, the server returns structured results, and the AI uses them to answer your question or complete a task.
In plain terms: MCP is how you give an AI assistant live access to HubSpot — not just knowledge about it, but real, up-to-date data from your account.
What a HubSpot MCP Integration Does
Once HubSpot is connected via MCP, your AI assistant can:
- Read live data — pull records, metrics, activity, and status directly from HubSpot
- Take actions — create, update, or log records based on your instructions
- Cross-reference context — combine HubSpot data with other connected tools mid-conversation
The key difference from a standard chatbot: the assistant is not working from training data or memory. It is reading your actual HubSpot instance, in real time.
Practical HubSpot MCP Use Cases
Live deal context in every conversation
Ask your AI assistant to pull up a deal's current stage, last activity, and open tasks — then draft a follow-up or coaching note — without switching out of your chat interface.
Contact and account enrichment
Have the assistant look up a contact in HubSpot mid-conversation and return structured fields: company, role, pipeline stage, and recent notes — to inform the current task.
Pipeline summaries on demand
"What deals are stalled in proposal stage?" The assistant queries HubSpot directly via MCP and returns a readable summary with suggested next actions.
CRM record creation from conversation
During a call debrief, the assistant captures structured output (contact, company, notes, next steps) and writes it back to HubSpot — one less thing to copy-paste.
How to Connect HubSpot via MCP
There are two main paths:
Option A: Use HubSpot's official MCP server
HubSpot maintains an official HubSpot MCP server. This is the recommended starting point — it's built and maintained by the HubSpot team, so it stays up to date with API changes.
Note: Public beta — available to HubSpot customers. Two server variants: one for users, one for developers.
What the server exposes:
- contacts
- companies
- deals
- tickets
- emails
- engagements
What you'll need:
- An MCP-compatible client (Claude Desktop, OpenClaw, or another host)
- HubSpot credentials configured per the server's setup guide
This path gives you the most control but requires you to handle client configuration and credential management yourself.
Option B: Use Cody (OpenClaw-based, managed)
Cody is built on OpenClaw and supports MCP-compatible integrations out of the box. You connect HubSpot once from the Cody dashboard — no server to run, no code to write — and Cody handles authentication, context passing, and write-back actions with appropriate guardrails.
Cody works where your team already operates: Slack, Telegram, or the web chat. The HubSpot connection is available to your entire team without each person setting up their own MCP client.
Want HubSpot Connected to AI Without Running Your Own MCP Server?
Cody has HubSpot integration built in. Query deals, contacts, and pipeline health from Slack without any API configuration.
MCP vs Other AI Integration Patterns
| Approach | What it is | Tradeoff |
|---|---|---|
| MCP | Standardised protocol for live tool access | Requires an MCP server; most powerful when set up correctly |
| RAG (retrieval) | Pre-index HubSpot content and retrieve it | Good for static docs; not suitable for live/transactional data |
| Manual copy-paste | Paste HubSpot output into ChatGPT/Claude | Fast to start; breaks for anything recurring or at scale |
| Custom API wrappers | Bespoke integration code per tool | Full control; high maintenance overhead |
MCP wins when you need live data from HubSpot and want to avoid rebuilding integrations as APIs change.
Common Mistakes
- Using training data when live data is needed — if the AI doesn't have an MCP connection, it will answer from memory, which is often outdated or wrong for account-specific questions
- No write-back guardrails — MCP can write to HubSpot, so it's worth adding an approval step for any action that modifies records
- Too many tools exposed at once — give the AI access to the HubSpot actions it actually needs; a scoped connection is easier to reason about and audit
- Skipping structured outputs — ask the AI to return structured JSON or clear fields when writing back to HubSpot; free-form output is harder to validate
Related MCP Guides
Want the full workflow picture? See: HubSpot AI Automation and How to Connect HubSpot to OpenClaw.