HubSpot

io.github.ohneben/hubspot-mcp

HubSpot API: 1,000+ endpoints as safety-categorized, hub- and plan-aware MCP tools, stdio or HTTP.

Connect this server

Add this to your MCP client config — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor).Suits: Claude Desktop · Cursor.

{
  "mcpServers": {
    "hubspot-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/ohneben/hubspot-mcp:2.0.1"
      ],
      "env": {
        "MCP_TRANSPORT": "<your MCP_TRANSPORT>",
        "HUBSPOT_ACCESS_TOKEN": "<your HUBSPOT_ACCESS_TOKEN>",
        "HUBSPOT_TOOL_MODE": "discovery",
        "HUBSPOT_READ_ONLY": "false",
        "HUBSPOT_CAPABILITY_CHECK": "true",
        "MCP_AUTH_TOKEN": "<your MCP_AUTH_TOKEN>"
      }
    }
  }
}
Environment variables
  • MCP_TRANSPORTrequiredServer transport. Set to 'stdio' for local MCP clients; the image otherwise starts the Streamable HTTP transport.
  • HUBSPOT_ACCESS_TOKENrequiredsecretHubSpot service key or legacy private app token (pat-...), from Settings -> Integrations. An OAuth access token also works.
  • HUBSPOT_TOOL_MODE'discovery' (default) exposes 3 meta-tools that search, inspect and call all 1,076 endpoints; 'all' exposes the ~690 endpoint tools directly.
  • HUBSPOT_READ_ONLYSet to 'true' to expose only read-only tools.
  • HUBSPOT_CAPABILITY_CHECKRead the token's scopes and probe paid-tier or beta API groups at startup (read-only, up to about 30 API calls). Set to 'false' to skip.
  • MCP_AUTH_TOKENsecretOnly for MCP_TRANSPORT=http: bearer token required on /mcp. Without it a non-loopback bind refuses to start.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Developer Tools
Version
2.0.1
Registry
active
Published
9/15/2026
Browse all Developer Tools →

Add the badge to your site

Show visitors that HubSpot is listed here — it’s also the link we check for a free listing.

HubSpot — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-ohneben-hubspot-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="HubSpot — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![HubSpot — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-ohneben-hubspot-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.