You can connect HubSpot to Claude using the Model Context Protocol (MCP), and once it’s connected, Claude can look up a contact, check a deal’s stage, or pull marketing data without you switching tabs into the CRM. This guide covers what HubSpot’s MCP server does, both ways to connect it — directly or through a gateway — and one thing worth knowing before you try: HubSpot’s OAuth isn’t currently open to every client that asks.
What the HubSpot MCP server actually does
HubSpot publishes a remote MCP server at mcp.hubspot.com. It exposes your portal’s contacts, deals, and marketing data as tools Claude can call directly, so prompts like these work against your live CRM:
- “Pull up the contact record for this email and summarize their activity.”
- “Which deals in the pipeline haven’t moved stage in 30 days?”
- “What’s the last note logged on this account?”
- “List open deals over $10k closing this quarter.”
Claude reads and, depending on the tools you allow, writes through the same permissions your HubSpot user already has — it isn’t a separate export or a read-only mirror, it’s your account acting on your behalf.
The catch: HubSpot’s OAuth isn’t open to every client yet
Some servers in gate’s directory — Notion, Linear, Stripe — let any AI client register itself and go straight through a one-click OAuth consent screen. HubSpot’s MCP endpoint is one of a handful where that isn’t the case today: the vendor’s OAuth currently only admits clients HubSpot has allow-listed in advance, rather than opening registration to any client that shows up. In practice, that can mean a connection attempt from a new or less-common client fails at the authorization step, even though the server itself is real and documented.
This is the same gap covered in MCP OAuth scopes explained: a server supporting OAuth in principle isn’t the same claim as every client being able to walk through it today. If you hit an “unauthorized client” error connecting HubSpot, that’s the most likely reason — not a mistake in your setup. Whether a given client can connect changes as vendors expand their allow-list over time, so it’s worth checking again later if it doesn’t work on your first attempt.
Option 1: Connect HubSpot to Claude directly
If the client you’re using is one HubSpot currently admits, the setup is:
- Open Claude’s connector or MCP settings.
- Add a remote server pointing at HubSpot’s MCP endpoint.
- Sign in with your HubSpot account when prompted — standard OAuth, so Claude never sees your HubSpot password, and you can revoke access from HubSpot’s own integrations settings at any time.
That’s enough if Claude is the only AI client you use with HubSpot. The tradeoff shows up once you add a second client or a second person on the team: each one needs its own attempt at the same OAuth step, with the same chance of hitting the allow-list wall independently.
Option 2: Connect it once, through a gateway
If you’re already juggling more than one MCP server or more than one AI client, wiring each pair directly gets old fast — that’s the connection sprawl covered in what an MCP gateway is. The idea is to connect HubSpot (and everything else) to one gateway URL, then point every AI client at that single URL instead of reconfiguring each one and re-running the OAuth step per client.
With gate specifically, connecting HubSpot looks like this: add gate’s gateway URL to Claude once, then pick HubSpot from the HubSpot server page in the directory and sign in the same way you would directly. gate’s catalog tracks each server’s current connectivity status — including cases like this one, where a vendor’s OAuth is still allow-listed — so you know what to expect before you try, instead of finding out mid-flow. See the full list of servers on the MCP servers page.
What to check before you connect a CRM
A HubSpot portal usually holds more than the one pipeline you’re thinking of when you connect it — every contact, every deal, and every marketing list the account can reach. A few things worth checking before or right after you connect:
- Read, or read and write? A connection that can summarize a deal can also update its stage or amount — know which tools are enabled before handing Claude a prompt like “clean up stale deals in the pipeline.”
- What can it actually see? Contact and company records often carry personal data; a prompt about one deal can surface fields you didn’t expect to show up in the answer.
- Who else on the team connects it? If more than one person wires up HubSpot to their own client, a shared, revocable setup beats everyone holding their own grant — the same question covered in MCP access control for teams.
You can run a quick, no-signup check on any server’s tool list with gate’s free MCP security scanner, which looks for prompt injection and hidden instructions in tool descriptions before you rely on a server day to day.
Troubleshooting the connection
- “Unauthorized client” or the OAuth screen never appears. Most likely the allow-list issue above — the client you’re using may not be one HubSpot currently admits for this endpoint.
- Sign-in succeeds but Claude can’t see a record you know exists. HubSpot’s tools respect your user’s own permissions in the portal; a pipeline or object type you don’t have access to won’t show up any more than it would in the HubSpot app itself.
- Tools disappear after a HubSpot update. Remote servers can change their tool list without warning. If you’re connected through a gateway, that kind of change is exactly what drift detection is meant to catch — see how MCP rug pulls work for why a one-time review isn’t enough.
The bottom line
Connecting HubSpot to Claude with MCP is a normal OAuth flow when the client you’re using is one HubSpot currently allows — direct if it’s your only client, or once through a gateway if you want the same access shared across every AI client on the team. If the connection fails at the authorization step, that’s worth reading as “not allow-listed yet” rather than a broken setup, and worth trying again as HubSpot opens this up over time.