HubSpot MCP Server

A Model Context Protocol server that provides access to the HubSpot API. This server enables LLMs to interact with HubSpot contacts, deals, and engagement data. A Model Context Protocol server that provides access to the HubSpot API. This server enables LLMs to interact with HubSpot contacts, deals, and engagements.

Components

Tools

The server implements several tools for HubSpot interaction:

Contact Tools

• get_contact_by_id: Retrieve a contact by their HubSpot ID (supports both string and integer IDs)
• get_contact_by_email: Find a contact by their email address
• search_contacts: Search for contacts based on property criteria

Deal Tools

• get_deal_by_id: Retrieve a deal by its HubSpot ID
• get_contact_deals: Get all deals associated with a contact
• get_deal_contacts: Get all contacts associated with a deal

Engagement Tools

• get_latest_marketing_campaign: Get information about recent marketing campaigns
• get_campaign_engagement: Get contacts who engaged with a specific campaign
• get_page_visits: Get contacts who visited a specific page
• get_contact_analytics: Get analytics data for a specific contact
• get_scheduled_meetings: Get meetings scheduled within a time period
• get_meeting_details: Get detailed information about a specific meeting

Resources

• hubspot://contacts/schema: Information about the contact object structure
• hubspot://deals/schema: Information about the deal object structure

Configuration

The server requires the following environment variables:

• HUBSPOT_API_KEY (required): Your HubSpot API key

Quickstart

Install

uv pip install hubspot-mcp-server

Claude Desktop Configuration

Add this to your Claude Desktop configuration file:

On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json

Installing via Smithery

To install HubSpot MCP Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @isaacraja/hubspot-mcp-server --client claude

Development Configuration

"mcpServers": {
  "hubspot": {
    "command": "uv",
    "env": {
      "HUBSPOT_API_KEY": "your_hubspot_api_key"
    },
    "args": [
      "--directory",
      "{{PATH_TO_REPO}}",
      "run",
      "hubspot-mcp-server"
    ]
  }
}

Replace {{PATH_TO_REPO}} with the path to your cloned repository and your_hubspot_api_key with your actual HubSpot API key.

Development/Unpublished Server Configuration

{
  "mcpServers": {
    "hubspot-mcp-server": {
      "command": "uv",
      "env": {
        "HUBSPOT_API_KEY": "your-api-key"
      },
      "args": [
        "--directory",
        "{{PATH_TO_REPO}}/src/hubspot_mcp_server",
        "run",
        "server.py"
      ]
    }
  }
}

Published Server Configuration

{
  "mcpServers": {
    "hubspot-mcp-server": {
      "command": "uvx",
      "env": {
        "HUBSPOT_API_KEY": "your-api-key"
      },
      "args": [
        "hubspot-mcp-server"
      ]
    }
  }
}

Replace your-api-key with your HubSpot API key.

Development

Building and Publishing

1. Sync dependencies and update lockfile:

uv sync

2. Build package distributions:

uv build

This will create source and wheel distributions in the dist/ directory.

3. Publish to PyPI:

uv publish

Note: You’ll need to set PyPI credentials via environment variables or command flags:

• Token: --token or UV_PUBLISH_TOKEN
• Or username/password: --username/UV_PUBLISH_USERNAME and --password/UV_PUBLISH_PASSWORD

Testing

Install test dependencies:

uv sync --extra test

Run tests:

# Run all tests
pytest

# Run with coverage
pytest --cov=server

Debugging

Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we recommend using the MCP Inspector.

You can launch the MCP Inspector via npm with this command:

npx @modelcontextprotocol/inspector uv --directory {{PATH_TO_REPO}} run hubspot-mcp-server

Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.

License

MIT