返回 MCP 目录
public公开dns本地运行

HubSpot数据桥

该服务器将 AI 模型与您的 HubSpot 帐户连接起来,让您直接访问联系人、公司和互动数据。内置的向量存储和缓存机制有助于克服 HubSpot API 的限制,同时缩短响应时间。

article

README

HubSpot MCP Server

Docker Hub License: MIT

Overview

A Model Context Protocol (MCP) server that enables AI assistants to interact with HubSpot CRM data. This server bridges AI models with your HubSpot account, providing direct access to contacts, companies, and engagement data. Built-in vector storage and caching mechanisms help overcome HubSpot API limitations while improving response times.

Our implementation prioritizes the most frequently used, high-value HubSpot operations with robust error handling and API stability. Each component is optimized for AI-friendly interactions, ensuring reliable performance even during complex, multi-step CRM workflows.

Why MCP-HubSpot?

  • Direct CRM Access: Connect Claude and other AI assistants to your HubSpot data without intermediary steps
  • Context Retention: Vector storage with FAISS enables semantic search across previous interactions
  • Zero Configuration: Simple Docker deployment with minimal setup

Example Prompts

Create HubSpot contacts and companies from this LinkedIn profile:
[Paste LinkedIn profile text]
What's happening lately with my pipeline?

Available Tools

The server offers tools for HubSpot management and data retrieval:

| Tool | Purpose | |------|---------| | hubspot_create_contact | Create contacts with duplicate prevention | | hubspot_create_company | Create companies with duplicate prevention | | hubspot_get_company_activity | Retrieve activity for specific companies | | hubspot_get_active_companies | Retrieve most recently active companies | | hubspot_get_active_contacts | Retrieve most recently active contacts | | hubspot_get_recent_conversations | Retrieve recent conversation threads with messages | | hubspot_search_data | Semantic search across previously retrieved HubSpot data |

Performance Features

  • Vector Storage: Utilizes FAISS for efficient semantic search and retrieval
  • Thread-Level Indexing: Stores each conversation thread individually for precise retrieval
  • Embedding Caching: Uses SentenceTransformer with automatic caching
  • Persistent Storage: Data persists between sessions in configurable storage directory
  • Multi-platform Support: Optimized Docker images for various architectures

Setup

Prerequisites

You'll need a HubSpot access token with these scopes:

  • crm.objects.contacts (read/write)
  • crm.objects.companies (read/write)
  • sales-email-read

Quick Start

# Install via Smithery (recommended)
npx -y @smithery/cli@latest install mcp-hubspot --client claude

# Or pull Docker image directly
docker run -e HUBSPOT_ACCESS_TOKEN=your_token buryhuang/mcp-hubspot:latest

Docker Configuration

For manual configuration in Claude desktop:

{
  "mcpServers": {
    "hubspot": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-e", "HUBSPOT_ACCESS_TOKEN=your_token",
        "-v", "/path/to/storage:/storage",  # Optional persistent storage
        "buryhuang/mcp-hubspot:latest"
      ]
    }
  }
}

Building Docker Image

To build the Docker image locally:

git clone https://github.com/buryhuang/mcp-hubspot.git
cd mcp-hubspot
docker build -t mcp-hubspot .

For multi-platform builds:

docker buildx create --use
docker buildx build --platform linux/amd64,linux/arm64 -t buryhuang/mcp-hubspot:latest --push .

Development

pip install -e .

License

MIT License

help

运行方式说明

cloud

托管运行

托管运行通常表示这个 MCP Server 由服务方环境承载,用户一般按页面提供的连接方式或授权流程接入,不需要在本地长期启动一个 MCP 进程

  1. 打开服务方连接页
  2. 完成授权或复制端点
  3. 在 MCP 客户端中连接
terminal

本地运行 / 其它方式

本地运行通常需要用户在自己的电脑或服务器上安装依赖,把 server_config 复制到 MCP 客户端,并按 env_schema 补齐环境变量、密钥或其它配置

  1. 复制 server_config
  2. 安装所需依赖
  3. 补齐环境变量后重启客户端