Table of contents
Is there an official HubSpot MCP server? Yes - HubSpot runs an official remote Model Context Protocol (MCP) server at mcp.hubspot.com, which reached general availability in April 2026 with read and write access to core CRM objects and engagements. It sits alongside a separate, local Developer MCP Server aimed at a different job entirely: building HubSpot apps and CMS assets rather than reading or writing CRM records.
This information is correct as of September 2026.
For marketing teams already using HubSpot’s Loop Marketing Playbook or syncing deals into delivery tools via the HubSpot ClickUp integration, an MCP server is the piece that lets an AI agent actually read and act on that CRM data directly, rather than you copying numbers between tabs. Here’s what HubSpot ships, how to set it up, and how it compares to the alternatives.
What HubSpot’s remote MCP server actually does
The remote CRM MCP server authenticates over OAuth 2.1 (PKCE plus single-use refresh tokens) and exposes a small, purpose-built tool set rather than a raw mirror of HubSpot’s full REST API. It has read and write access to core CRM objects - contacts, companies, deals, tickets, carts, products, orders, line items, invoices, quotes, and lists - plus engagements such as calls, emails, meetings, notes, and tasks. Organisational context (users, teams, reporting structures, owners, roles, and seats) and marketing content (campaigns and campaign metrics, landing pages, website pages, and blog posts) are read-only.
The one gap worth flagging before you plan a workflow around it: custom objects aren’t part of that list. If your portal relies on a non-standard data model, an AI agent using this server alone can’t see or write to those objects, and you’ll need the direct API or a community server that fills that gap. HubSpot also blocks the server from reading custom Sensitive Data Properties, so PII flagged that way stays out of an agent’s context by design.
Remote CRM MCP vs the Developer MCP Server
HubSpot ships two separate MCP servers, and the names get conflated constantly:
- Remote CRM MCP server (
mcp.hubspot.com, GA April 2026) - for agent-to-CRM data access. This is the one marketing and sales teams want. - Developer MCP Server (local, CLI-based via
hs mcp setup, GA February 2026) - gives coding tools like Claude Code, Cursor, and VS Code access to HubSpot’s developer platform for building apps and CMS content. It is not for reading or writing CRM data.
If your goal is pulling deal data into an AI conversation or having an agent update a contact record, you want the remote CRM server, not the Developer MCP Server.
Setup: two paths depending on who’s connecting
There are two practical ways to connect, and which one you want depends on whether the person connecting is technical:
- HubSpot’s packaged Claude connector (easiest, no code): in Claude, go to Settings (or Organization settings for Team/Enterprise) > Connectors > Browse connectors, select HubSpot, click Connect, then log in to HubSpot and approve the requested scopes. A HubSpot Super Admin or a user with App Marketplace permissions needs to complete the first connection for the organisation; teammates then connect their own accounts afterwards. The connector itself is free on every HubSpot tier including the free CRM; the paid requirement sits on the Claude side, since custom connectors need a Pro, Max, Team, or Enterprise plan.
- Generic OAuth setup for any MCP client (Cursor, custom agents, other MCP-compatible tools): create a user-level application in HubSpot with read (and write, if needed) scopes for the CRM objects you want to expose, then use those OAuth credentials to connect to the
mcp.hubspot.comendpoint from your MCP client of choice.
Either way, permissions are inherited from the connecting HubSpot user, not expanded, so an agent can only see what that user’s account can see.
Marketing-team use cases
Once connected, the practical value for a marketing team looks like:
- Lead scoring and enrichment - an agent reads recent engagement history (emails, meetings, form fills) alongside deal stage to flag which leads are warming up, without a manual export.
- Campaign brief to CRM sync - pulling live campaign and landing page performance into a planning conversation instead of switching to the HubSpot dashboard (read-only, so an agent can report on it but not edit it directly).
- Pipeline and deal queries via AI agents - asking an agent “which deals in this quarter’s target list haven’t been contacted in two weeks” and getting an answer sourced from live CRM data, not a stale report.
- Contact and company updates from other tools - an agent that already has context from a call transcript or a support ticket can update the relevant HubSpot record directly, using the same write scopes granted at setup.
HubSpot MCP server options compared
| Remote CRM MCP server | Developer MCP Server (local) | Community option (e.g. axonops/hubspot-mcp) | |
|---|---|---|---|
| Status | Official, GA since April 2026 | Official, GA since February 2026 | Independent, actively maintained forks vary |
| Purpose | Agent-to-CRM data access | Building HubSpot apps and CMS assets | Agent-to-CRM data access, often including custom objects |
| Hosting | Remote, hosted by HubSpot | Local (CLI-based) | Self-hosted (local or your own deployment) |
| Auth | OAuth 2.1 (PKCE, rotating refresh tokens) | HubSpot CLI login | Private app token or per-user OAuth, depending on the project |
| Tool set | Small, object-typed: read/write on contacts, companies, deals, tickets, line items, products, quotes, lists, and engagements; read-only on marketing content and org data | CLI commands for app and CMS scaffolding | Varies by project; some cover custom objects and marketing automation the official server doesn’t |
| Setup effort | Minimal for the packaged Claude connector; a short OAuth app setup for other clients | Requires the HubSpot CLI and developer platform familiarity | Requires deployment and ongoing maintenance |
| Best for | Most marketing and sales teams | Developers building on HubSpot’s platform | Teams needing custom object support or headless, unattended access |
For most marketing teams, the official remote server is the right starting point: it needs no infrastructure, HubSpot maintains it, and the packaged Claude connector gets a non-technical user connected in minutes. Teams with a heavily customised HubSpot instance, or that need an agent to run without a person present to approve OAuth, are better served checking an actively maintained community server, in the same way the community alternative fills gaps left by Notion’s own local server once you outgrow the official happy path.
See the full MCP servers list for how HubSpot’s server fits alongside the other tools in a marketing team’s stack.
About Growth Method
A HubSpot MCP server gets an AI agent read and write access to your CRM data. Growth Method is the agentic marketing platform for B2B teams: plan a campaign’s hypothesis, launch it, and let AI agents pull the after-numbers straight from your connected analytics and CRM, so a HubSpot deal or contact update becomes part of a measured campaign rather than a one-off automation. Connect your martech stack, including HubSpot, and both your team and its agents can plan, launch, and analyse campaigns from the same live data your CRM already holds.
Get started to connect your stack and run your next campaign from live CRM data, not a static export.
Frequently asked questions
Is there an official HubSpot MCP server?
Yes. HubSpot runs an official remote MCP server at mcp.hubspot.com, which reached general availability in April 2026 with read and write access to core CRM objects and engagements. It’s separate from HubSpot’s local, CLI-based Developer MCP Server, which is for building apps and CMS assets rather than reading or writing CRM data.
What’s the difference between the remote and Developer MCP servers?
The remote CRM MCP server at mcp.hubspot.com is for agent-to-CRM data access: contacts, companies, deals, tickets, and engagements. The Developer MCP Server, set up locally via the HubSpot CLI (hs mcp setup), gives coding tools like Claude Code, Cursor, and VS Code access to HubSpot’s developer platform for building apps and CMS content. The two are easy to conflate but serve different jobs.
Is HubSpot MCP free?
The MCP server and HubSpot’s packaged Claude connector are free to use on every HubSpot tier, including the free CRM. The paid requirement sits on the AI client side: Claude’s custom connectors need a Pro, Max, Team, or Enterprise plan, since free Claude accounts can’t use connectors at all.
What CRM data can AI agents access?
The remote MCP server has read and write access to core CRM objects (contacts, companies, deals, tickets, carts, products, orders, line items, invoices, quotes, and lists) and engagements (calls, emails, meetings, notes, tasks), plus read-only access to marketing content (campaigns, landing pages, website pages, blog posts) and organisational context (users, teams, owners, roles). The confirmed gap is custom objects, which aren’t supported yet, so accounts with a non-standard data model need the direct API or a community server instead.
Can it run headlessly without a user present?
No, not the official remote server. Its OAuth 2.1 flow is designed around an authenticated user approving access, so it isn’t built for fully unattended use. For scheduled or agent-triggered workflows without a person present, teams typically reach for a community server authenticated with a stored private-app token instead.