What is a HubSpot Private App token?

A Private App is HubSpot's recommended API credential. You create one in Settings → Integrations → Private Apps, select the CRM and Meetings scopes you need, and copy the token. It is not a public OAuth flow — the token belongs to your HubSpot account and grants access to your portal.

Does this require a paid HubSpot plan?

Contact and company read access is available on the Free plan. Meeting scheduling links require Sales Hub Starter or above. Deal and ticket access requires a CRM Pro or above plan depending on the operation.

How does this differ from the ChatGPT HubSpot App?

The ChatGPT HubSpot App is a one-click OAuth app for chatgpt.com only. The HubSpot MCP server is a proper MCP that works with Claude, Cursor, and any MCP-compatible client — and requires a Private App token rather than OAuth.

HubSpot MCP

Name: Top MCPs — curated MCP directory
Creator: Top MCPs
License: https://creativecommons.org/licenses/by/4.0/

Official

Official HubSpot MCP server — CRM contacts, deals, and meeting scheduling from Claude or Cursor.

Score 54(?)HubSpotProprietaryVerified Jun 28, 2026Top MCPs for Scheduling & Calendar →

Install

Quick answer

What it does

Exposes HubSpot CRM tools: create and read contacts and companies, manage deals and tickets, search the CRM, and for the scheduling surface — retrieve meeting scheduling links, list booked meetings, and look up meetings associated with a contact or deal record.

Best for

B2B sales meeting scheduling tied to CRM context
RevOps workflows that need CRM + meetings in one agent
Looking up booked meetings on a contact or deal
Generating HubSpot meeting scheduling links

Not for

Teams without a HubSpot account
Pure calendar access (no CRM) — use Google Calendar or Outlook instead

Setup recipe

Pick your client, then follow the three steps.

Install

claude_desktop_config.jsonjson

{
  "mcpServers": {
    "hubspot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@hubspot/mcp-server"
      ],
      "env": {
        "HUBSPOT_PRIVATE_APP_TOKEN": "${HUBSPOT_PRIVATE_APP_TOKEN}"
      }
    }
  }
}

Paste under mcpServers. Fully quit and reopen Claude after editing.

CLI or .mcp.jsonshell

# export HUBSPOT_PRIVATE_APP_TOKEN=pat-na1-xxxx
claude mcp add hubspot-mcp -- npx -y @hubspot/mcp-server

Run from your repo. Commit .mcp.json to share with your team.

.cursor/mcp.jsonjson

{
  "mcpServers": {
    "hubspot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@hubspot/mcp-server"
      ],
      "env": {
        "HUBSPOT_PRIVATE_APP_TOKEN": "${HUBSPOT_PRIVATE_APP_TOKEN}"
      }
    }
  }
}

Global path: ~/.cursor/mcp.json. Reload window after editing.

.vscode/mcp.jsonjsonc

{
  "servers": {
    "hubspot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@hubspot/mcp-server"
      ],
      "env": {
        "HUBSPOT_PRIVATE_APP_TOKEN": "${HUBSPOT_PRIVATE_APP_TOKEN}"
      }
    }
  }
}

VS Code uses the "servers" key (not "mcpServers").

~/.codeium/windsurf/mcp_config.jsonjson

{
  "mcpServers": {
    "hubspot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@hubspot/mcp-server"
      ],
      "env": {
        "HUBSPOT_PRIVATE_APP_TOKEN": "${HUBSPOT_PRIVATE_APP_TOKEN}"
      }
    }
  }
}

Open via Cascade → hammer icon → Configure.

cline_mcp_settings.jsonjson

{
  "mcpServers": {
    "hubspot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@hubspot/mcp-server"
      ],
      "env": {
        "HUBSPOT_PRIVATE_APP_TOKEN": "${HUBSPOT_PRIVATE_APP_TOKEN}"
      }
    }
  }
}

Open via the Cline sidebar → MCP Servers → Edit.

~/.continue/config.jsonjson

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "@hubspot/mcp-server"
          ],
          "env": {
            "HUBSPOT_PRIVATE_APP_TOKEN": "${HUBSPOT_PRIVATE_APP_TOKEN}"
          }
        }
      }
    ]
  }
}

Continue uses modelContextProtocolServers with a transport block.

~/.codex/config.tomlshell

# ~/.codex/config.toml
[mcp_servers.hubspot-mcp]
command = "npx"
args = [
  "-y",
  "@hubspot/mcp-server",
]
env = { HUBSPOT_PRIVATE_APP_TOKEN = "${HUBSPOT_PRIVATE_APP_TOKEN}" }

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

~/.config/zed/settings.jsonjsonc

{
  "context_servers": {
    "hubspot-mcp": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@hubspot/mcp-server"
        ]
      },
      "env": {
        "HUBSPOT_PRIVATE_APP_TOKEN": "${HUBSPOT_PRIVATE_APP_TOKEN}"
      }
    }
  }
}

Zed calls them "context_servers". Settings live-reload on save.

ChatGPT → Apps directorynone

HubSpot MCP doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

2
Set required secrets
Set HUBSPOT_PRIVATE_APP_TOKEN in your shell environment before launching your MCP client.
3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Security & scope

Access scope: Read + write
Sandbox: Private App token grants exactly the scopes selected at creation. Use the minimal set — read-only CRM scopes if you only need lookups. Do not add the admin or settings scopes unless required.
Gotchas: The Private App token is a long-lived credential — treat it like a password. Rotate it from the HubSpot settings page if leaked.
Write operations (create contact, update deal) are available on matching scopes; confirm before granting them if the agent should only read.
The MCP server is in public beta — tool surface and behavior may change before GA.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.

Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.

Recommend the best MCP servers for [task: e.g. scheduling & calendar work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-scheduling-calendar

Compare HubSpot MCP against a real alternative. Swap the second MCP in [brackets] if you want a different match.

Compare HubSpot MCP MCP vs [Calendly MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/hubspot-mcp
- top-mcps.com listing for Calendly

Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.

Install the HubSpot MCP MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/hubspot-mcp (fetch https://top-mcps.com/mcp/hubspot-mcp.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (HUBSPOT_PRIVATE_APP_TOKEN) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

Jun 28, 2026
Refreshed install snippets and fact sheet; verified for 2026.
May 1, 2025
Initial directory listing.

More Scheduling & Calendar MCPs

Other tools in the same category worth evaluating.

Google Calendar

Read, create, and manage events across Google Calendar — via Google's official remote MCP or a self-hosted community server.

google-calendarschedulingeventsproductivity

10 minMedium

Calendly

Official hosted MCP for booking-link scheduling — share availability without exposing the raw calendar.

calendarschedulingcalendlybooking

5 minLow

Apple Calendar (CalDAV)

Read and create events in Apple Calendar via CalDAV from any MCP client.

calendarapplecaldavicloud

10 minMedium

Compared with HubSpot MCP

Side-by-side breakdowns for the choices people most often weigh against this MCP.

HubSpot MCPvsCalendly HubSpot MCPvsCal.com HubSpot MCPvsZoho CRM HubSpot MCPvsClose

Exploring Top MCPs for Scheduling & Calendar? See all Scheduling & Calendar MCPs →

Quick answer

What it does

Best for

Not for

Setup recipe

Install

Set required secrets

Try a minimum working prompt

Tools & permissions

Security & scope

Agent prompt pack

Full details

Frequently asked questions

What is a HubSpot Private App token?

Does this require a paid HubSpot plan?

How does this differ from the ChatGPT HubSpot App?

What changed

More Scheduling & Calendar MCPs

Google Calendar

Calendly

Apple Calendar (CalDAV)

Compared with HubSpot MCP