hubspot-mcp-server

A production-grade, read-only MCP server for HubSpot CRM: list and fetch contacts, companies, deals, and tickets (or any custom object), full-text search, walk the CRM's association graph, and discover an object's property schema — from Claude Desktop, Claude Code, or any MCP client — with HubSpot's rate limits handled properly and no live portal required to run the test suite.

Read-only by construction: the HTTP layer this server is built on (hubspot_mcp.client.HubSpotClient) exposes exactly two verbs — get, and post. The only post calls this server ever makes are to HubSpot's CRM Search API (POST /crm/v3/objects/{object}/search), which HubSpot itself models as a POST purely because the search filter body is too large for a query string — it is a read, not a write. The client hard-allowlists this: post() rejects any path that doesn't end in /search with a ValueError before a request is ever sent. There is no put, patch, or delete method anywhere in the codebase.

The server can read whatever the token's scopes allow. A HubSpot Private App access token's granted scopes are the actual security boundary — this server enforces nothing beyond what the token itself is permitted to see. Grant only the read scopes you need (e.g. crm.objects.contacts.read, not every crm.objects.*.read scope) — see the setup walkthrough below.

hubspot-mcp-server is not affiliated with, endorsed by, or sponsored by HubSpot, Inc.

Quickstart

Requires uv and a HubSpot portal to point at. Don't have one? developers.hubspot.com lets you create a free developer account and a test portal in a couple of minutes — no cost, no credit card.

Install and run

This project will be published to PyPI as the distribution hubspot-mcp; its console script is named hubspot-mcp-server (a different, unrelated package already holds the hubspot-mcp-server PyPI name). Because of that mismatch, once published you must tell uvx which distribution to pull the script from — uvx hubspot-mcp-server alone would fetch the wrong package:

uvx --from hubspot-mcp hubspot-mcp-server

That starts the server over stdio. In practice you'll point an MCP client at it instead of running it directly — for Claude Code:

Note: hubspot-mcp is not yet published to PyPI either, so --from hubspot-mcp below won't resolve. Until it's published, replace it with the from-source form uvx --from git+https://github.com/inogen-ai/hubspot-mcp-server hubspot-mcp-server.

claude mcp add hubspot \
  -e HUBSPOT_MCP_ACCESS_TOKEN=<your-private-app-token> \
  -- uvx --from hubspot-mcp hubspot-mcp-server

For Claude Desktop, add to claude_desktop_config.json:

{
  "mcpServers": {
    "hubspot": {
      "command": "uvx",
      "args": ["--from", "hubspot-mcp", "hubspot-mcp-server"],
      "env": {
        "HUBSPOT_MCP_ACCESS_TOKEN": "<your-private-app-token>"
      }
    }
  }
}

Create a Private App and access token

1. In your HubSpot portal, click the Settings gear icon (top nav).
2. In the left sidebar, go to Integrations > Private Apps.
3. Click Create a private app, give it a name (e.g. "hubspot-mcp-server").
4. Open the Scopes tab and select the read scopes for what you want this server to access — for example crm.objects.contacts.read, crm.objects.companies.read, crm.objects.deals.read, crm.objects.tickets.read, and crm.schemas.contacts.read (and the matching crm.schemas.<object>.read scopes for whichever objects you use list_properties on). Grant only what you actually need — see the scope warning above.
5. Click Create app, confirm, then copy the access token shown — HubSpot only displays it once. Store it somewhere safe; it's a secret.

Tools

Object model cheat sheet

object_type accepts a standard HubSpot object name — contacts, companies, deals, tickets — or a custom object's name, everywhere it appears above. Record ids are always plain numeric strings (e.g. "12345"), never HubSpot's hs_object_id formatted any other way; get_record rejects anything that isn't purely digits before making a request. search_records' query is plain search text — it goes straight into the search request's JSON query field, never string-interpolated into a filter expression.

Environment variables

All settings are prefixed HUBSPOT_MCP_ and can be set in the environment or a .env file (see .env.example).

HUBSPOT_MCP_ACCESS_TOKEN unset fails startup immediately with a message naming the env var to fix, rather than failing obscurely on the first tool call.

Rate limits

HubSpot Private Apps are subject to daily and per-second API call limits. This server reads HubSpot's X-HubSpot-RateLimit-* headers off every response and appends a warning to a tool's result once daily usage crosses 90% used (10% or less of the daily quota remaining), so a client sees it coming rather than hitting a hard stop mid-session. A 429 is retried honoring Retry-After (clamped to at most 60s, up to 3 retries, exponential 1→2→4s backoff when no header is sent) — except when HubSpot's error body names the DAILY policy, which is not retried (retrying can't fix a quota that only resets at midnight portal time) and instead returns an actionable message immediately.

Security notes

• Read-only by construction, not by policy — see the warning at the top of this README. The Private App token's granted scopes, not this server, decide what's actually readable.
• Rate-limit aware. See "Rate limits" above.
• Credentials never appear in error messages, logs, or exceptions raised to an MCP client — failures are reduced to plain, credential-free sentences before they leave the client layer.
• Not affiliated with, endorsed by, or sponsored by HubSpot, Inc.

Development

Requires Python 3.11+ and uv.

uv sync
uv run pytest -q
uv run ruff check .

No live HubSpot portal is needed for the test suite — the CRM API is faked at the httpx.MockTransport boundary, and a committed stdio integration gate drives the real server process against an in-process fake CRM API. See docs/manual-verification.md for the live-portal check a maintainer runs before releases.

Contributing

Contributions welcome — see CONTRIBUTING.md for dev setup and PR expectations, and SECURITY.md for reporting vulnerabilities privately.

Not affiliated with, endorsed by, or sponsored by HubSpot, Inc.

Part of InoGen's open-source portfolio: kilnworks (self-hostable RAG assistant) and the read-only MCP connectors m365, servicenow, salesforce, and hubspot.

Built and maintained by InoGen.