HubSpot CRM Official Remote MCP Server
HubSpot's hosted MCP (mcp.hubspot.com) exposes CRM objects — contacts, companies, deals, tickets — to agents for search, read and write workflows over OAuth 2.1.
中文简介
HubSpot 官方远程 MCP 服务器。AI 代理可通过 OAuth 搜索 CRM 对象(联系人、公司、商机)、读取属性并创建或更新记录。
Maintainer of HubSpot CRM? Claim or update this listing →
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"hubspot": {
"url": "https://mcp.hubspot.com"
}
}
}claude mcp add --transport http hubspot https://mcp.hubspot.com
Or add to .vscode/mcp.json:
{
"servers": {
"hubspot": {
"type": "http",
"url": "https://mcp.hubspot.com"
}
}
}- Open Settings → Connectors (Integrations) → Add Custom Connector.
- Paste the endpoint URL:
https://mcp.hubspot.com - Complete the browser OAuth 2.1 login flow when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"hubspot": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.hubspot.com"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"hubspot": {
"serverUrl": "https://mcp.hubspot.com"
}
}
}Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in your workspace), then reopen Kiro's Agent panel to pick up the server:
{
"mcpServers": {
"hubspot": {
"url": "https://mcp.hubspot.com"
}
}
}Add to ~/.codex/config.toml — Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.hubspot] url = "https://mcp.hubspot.com"
Add to cline_mcp_settings.json (Cline → MCP Servers → Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"hubspot": {
"type": "streamableHttp",
"url": "https://mcp.hubspot.com"
}
}
}Add to ~/.gemini/settings.json under mcpServers — httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"hubspot": {
"httpUrl": "https://mcp.hubspot.com"
}
}
}🧰 HubSpot CRM MCP Tools & Schema (6)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| search_contacts ~68 tok | 🟢 Read | Search CRM contacts by name, email or properties. | query*: stringlimit: number |
| get_contact ~51 tok | 🟢 Read | Get a contact with all properties. | contactId*: string |
| create_contact ~52 tok | 🟠 Write | Create a new CRM contact. | properties*: object |
| search_companies ~47 tok | 🟢 Read | Search CRM companies. | query*: string |
| list_deals ~63 tok | 🟢 Read | List deals with stage and pipeline filters. | pipeline: stringstage: string |
| create_deal ~76 tok | 🟠 Write | Create a new deal in a pipeline. | dealname*: stringpipeline: stringamount: string |
🛡️ Security, Quality & Context Token Audit
Every tool definition (name + description + input schema) is injected into your LLM’s context on every request — Estimate per-call LLM token cost →
- No prompt-injection or hidden-character anomalies detected in tool descriptions
- Streamable HTTP primary endpoint (current 2025-03-26 transport)
- OAuth 2.1 with PKCE S256 enforced
- Official first-party endpoint operated by the vendor
- Manually verified by RemoteMCP.net
🔐 OAuth 2.1 & Security
- Auth type
- OAuth 2.1
- Dynamic Client Registration
- ✅ Supported
- PKCE S256
- ✅ Supported
- Scopes
crm.objects.contacts.readcrm.objects.contacts.writecrm.objects.deals.read- Protected resource metadata
- https://mcp.hubspot.com/.well-known/oauth-protected-resource (expected location)
🧩 Recommended Agent Skills
📖 HubSpot CRM MCP Endpoint Overview & Security Guide
HubSpot CRM MCP — Remote MCP Server
HubSpot's remote MCP opens the CRM graph to agents — search contacts and companies, pull deal pipelines, create activities — so an assistant can answer 'what's the state of the Acme deal' or log a follow-up without a human clicking through the CRM.
Official HubSpot CRM MCP Endpoint & Transport Architecture
- Endpoint URL:
https://mcp.hubspot.com - Transport: Streamable HTTP
Streamable HTTP is the current MCP transport (2025-03-26 spec): a single URL accepts JSON-RPC POSTs and may stream responses over SSE, so one endpoint serves both simple and streaming workloads. HubSpot CRM MCP does not publish a separate legacy SSE endpoint, so your client must speak Streamable HTTP.
Authentication, Scopes & Permission Boundaries
HubSpot CRM MCP uses OAuth 2.1 — the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow — PKCE and Dynamic Client Registration, so no manual client setup is needed — and simply open a browser consent screen.
Of the 6 cataloged tools, 4 are read-only and 2 can write or mutate state (create resources, run SQL, post messages). Grant access only to the accounts and projects you intend agents to act on, and prefer scoped credentials or a dedicated workspace where the provider supports them.
Common Troubleshooting & Connection Tips
- 401 Unauthorized on connect — that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact
WWW-Authenticatechallenge. - "Session expired" / stale
Mcp-Session-Id— just re-sendinitialize; stateless clients can ignore session headers entirely. - Requires a HubSpot user login; scope granularity follows the app's declared scopes.
- Write tools respect HubSpot's property validation — invalid property names fail fast.
🚀 How to Connect
- Copy the HubSpot CRM MCP endpoint URLThe remote endpoint is https://mcp.hubspot.com.
- Add it to your MCP clientClaude Code:
claude mcp add --transport http hubspot https://mcp.hubspot.com. Cursor: add"hubspot": { "url": "https://mcp.hubspot.com" }undermcpServersin ~/.cursor/mcp.json. Other clients work similarly. - Complete the OAuth consentOn first connection your client opens a HubSpot consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
- Verify with the online inspectorPaste https://mcp.hubspot.com into remotemcp.net/inspector, run initialize and tools/list, and confirm HubSpot CRM MCP's 6 tools respond.
❓ FAQ
What is the HubSpot CRM MCP remote MCP endpoint?
The primary endpoint is https://mcp.hubspot.com. It is an official first-party server operated by HubSpot, speaking the Streamable HTTP transport.
How do I authenticate with HubSpot CRM MCP?
HubSpot CRM MCP uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen. Dynamic Client Registration is supported, so compliant clients register themselves automatically.
I'm getting a 401 Unauthorized from HubSpot CRM MCP — what's wrong?
A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.
Which MCP clients work with HubSpot CRM MCP?
Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http hubspot https://mcp.hubspot.com`), VS Code Copilot, ChatGPT connectors, Windsurf, Kiro (`~/.kiro/settings/mcp.json`), and Claude Desktop via the `mcp-remote` bridge.
What tools does HubSpot CRM MCP expose?
6 tools are cataloged in this directory — including `search_contacts`, `get_contact`, `create_contact` and more. Use our online inspector to fetch the live tool list straight from the endpoint.
🔗 Connect Guides
📛 Embed Status Badge in README
Related Servers
Notion's official hosted MCP server. Agents can search your workspace, read and create pages, and query databases over Streamable HTTP or SSE.
Linear's official remote MCP server. Agents can search, create and update issues and query your team's workflow over Streamable HTTP or SSE.
Slack's hosted remote MCP server. Slack's official remote MCP lets agents search channels, read conversation history, post messages and manage canvases inside your Slack workspace. It is protected by OAuth 2.1; compliant clients complete a browser consent flow with PKCE.
Todoist's official remote MCP server. Agents can add, complete and search tasks, manage projects and sections over OAuth 2.1.