CRM and activity access
Read and write contacts, companies, deals, tickets, tasks, meetings, notes, and other supported CRM objects.
Documentation ↗MCP server / CRM / source-linked
HubSpot MCP
HubSpot now documents two distinct servers: a remote CRM MCP server at mcp.hubspot.com and a separate local Developer MCP server for CLI-based platform work. The remote server uses OAuth 2.1 with PKCE, user-level app scopes, and account context; it can read and write CRM objects, activities, content, campaigns, and selected marketing data.
Before you choose.
Identify the implementation and the job it supports.
HubSpot now documents two distinct servers: a remote CRM MCP server at mcp.hubspot.com and a separate local Developer MCP server for CLI-based platform work. The remote server uses OAuth 2.1 with PKCE, user-level app scopes, and account context; it can read and write CRM objects, activities, content, campaigns, and selected marketing data.
Setup and connection.
The documented interface, authentication and installation path.
- Connection / transport
- Remote Streamable HTTP; separate local CLI/stdio Developer MCP
- Authentication
- OAuth 2.1 with PKCE for the remote server; local Developer MCP uses HubSpot CLI authentication.
Create a HubSpot connector/user-level app with the needed scopes, configure the client for https://mcp.hubspot.com, and complete PKCE OAuth. Use hs mcp setup only for the separate local Developer MCP.
Setup reference ↗Documented setup example. Review the source and credentials before running; this command was not executed for this article.
hs mcp setup (Developer MCP only; remote CRM server uses an OAuth connector)What it actually exposes.
Concrete capabilities with maintainer sources.
Content and marketing
Access pages, blog posts, campaigns, analytics, email drafts, and related marketing resources according to scopes.
Documentation ↗Developer platform context
The separate Developer MCP helps scaffold UI extensions and interact with the developer platform through the CLI.
Documentation ↗Evidence and method.
What was checked and what was not tested.
HOW
Source method
Public maintainer documentation and repositories. This is not a hands-on product review.
WHEN
Last checked 2026-10-01
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
Try a specific task.
A bounded evaluation you can reproduce in your own environment.
CRM hygiene review
Suggested evaluation, not an observed test result.
- Create a connector with read-only scopes for the CRM objects needed.
- Ask the agent to identify stale records or pipeline inconsistencies and cite record IDs.
- Review a proposed batch update, then approve writes in small, reversible groups.
What to inspect: A scoped CRM cleanup plan with record-level evidence and a human-approved change set. Proposed workflow; not tested by clawbot.ai.
Workflow reference ↗Permissions and limitations.
Read these constraints before granting access.
PKCE is required for custom remote integrations; a client supporting only older OAuth behavior cannot connect.
Boundary reference ↗Sensitive data and some conversation access can be blocked by account settings; availability is scope and product-plan dependent.
Boundary reference ↗Decide by workflow.
Make the expected output explicit before you connect.
A scoped CRM cleanup plan with record-level evidence and a human-approved change set. Proposed workflow; not tested by clawbot.ai.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Compare the alternatives.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| Airtable MCP | Choose for bases, records, interfaces, and draft automations. | Airtable is table/workspace-centric; HubSpot has richer CRM object semantics and pipelines. Documentation ↗ |
| Zapier MCP | Choose for cross-app actions rather than deep CRM record access. | Zapier offers breadth but less HubSpot-specific object context. Documentation ↗ |
Questions before setup.
Answers specific to this implementation.
Are HubSpot’s two MCP servers the same?
No. The remote CRM server and local Developer MCP serve different data and setup paths.
Documentation ↗
What authentication does remote HubSpot use?
OAuth 2.1 with PKCE through a connector and user-level app scopes.
Documentation ↗
Source trail.
Maintainer documentation used in this record.