HubSpot MCP server: setup, tools, and what a marketing agent can do with it

HubSpot's MCP server is one of the better ones in the marketing category: official, remote, OAuth, and it appears in Claude's connector directory so a marketer can connect it without touching a terminal. This guide covers the setup for each client, what the server exposes, and the workflows that make it worth having. General client instructions live in Claude Code, Cursor and Claude Desktop.

Connecting

Claude (web and desktop). Settings, Connectors, find HubSpot, Connect, sign in to HubSpot and approve the scopes. Enable it in a conversation's tools menu.

Claude Code.

claude mcp add --transport http hubspot https://mcp.hubspot.com/mcp

Then /mcp in a session to authenticate. Check HubSpot's developer docs for the current URL; vendors move endpoints.

Cursor. Add to mcp.json with the url field and enable; Cursor runs the OAuth flow.

ChatGPT. Available as a connector on eligible plans, or through developer mode as a custom MCP server.

Whichever client, the server acts as the HubSpot user who signed in, with that user's permissions. For a team, a dedicated HubSpot user with a restricted role is better than a marketing manager's super-admin login.

What it exposes

The server is organised around CRM objects and engagements:

• Objects: contacts, companies, deals, tickets, and custom objects, with search, get, create and update.
• Engagements: notes, calls, emails, meetings and tasks attached to records.
• Associations: which contacts belong to which company, which deals to which contact.
• Properties: the schema, so the agent can use your custom fields correctly.

Ask the agent to list its tools after connecting; coverage expands with HubSpot's releases.

Workflows that pay off

• Lead triage. "New contacts from the last 7 days with no owner: summarise each from their form submissions and suggest an owner by territory."
• Pipeline hygiene. "Deals in Proposal stage with a close date in the past. List them with the last activity."
• Account prep. "Everything we know about Acme before the call at 14:00: contacts, open deals, last five engagements."
• Marketing to revenue. With Google Ads in the same session: "Which campaigns did contacts who became customers this quarter first convert on?"
• Data quality. "Companies missing industry or country, grouped by owner."

Turn the recurring ones into skills so the whole team gets the same triage or prep routine.

Controlling writes

The server can create and update records. Updates are reversible but noisy; bulk updates by a misdirected agent are a cleanup afternoon. The standard controls:

• Approval on create and update tools; auto-allow only search and get.
• A restricted HubSpot role for the connected user.
• Sessions that read inbound content (form submissions, emails, tickets) treated as untrusted, per MCP security best practices.

For a team, those rules belong in a gateway rather than in each user's settings. Walma AI Hub runs HubSpot alongside the other approved marketing servers behind one policy and one log, in the customer's own EU region. Book a walkthrough if you are rolling agents out to a sales or marketing team.