HubSpot MCP Server (Official)Featured

What is HubSpot MCP Server (Official)?

HubSpot MCP is HubSpot's official remote MCP server at https://mcp.hubspot.com, letting AI assistants read and, where permitted, update your CRM records, activities, marketing content and conversations through natural language, with OAuth sign-in.

The server is hosted by HubSpot, so there is nothing to install or run locally. HubSpot also ships a separate, local Developer MCP server for building apps and CMS content with the HubSpot CLI; it does not query CRM data. This page covers the remote HubSpot MCP server.

How to use HubSpot MCP Server (Official)?

Prerequisites: a HubSpot user account and an MCP client that supports OAuth with PKCE (S256). No API key is used; access comes from an OAuth flow.

Option 1: built-in connector (Claude apps). In Claude (web, desktop or mobile), open Settings > Connectors, click Browse, search for HubSpot, click Connect, sign in to your HubSpot account, choose the permissions and click Connect app. This needs a paid Anthropic plan (Pro, Max, Team or Enterprise). Super Admins and users with App Marketplace Access can connect directly; other users need a Super Admin to approve the connector first.

Option 2: any MCP client with your own MCP connector.

1. In HubSpot go to Development > MCP Connectors (https://app.hubspot.com/l/mcp-auth-apps/) and click Create MCP connector.
2. Enter a name and the redirect URL(s) your client uses, then click Create.
3. Copy the client ID and client secret from the connector details page.
4. Configure your client with https://mcp.hubspot.com, the client ID and secret, and the matching redirect URL.
5. Complete the OAuth flow (select the account, grant permissions, authorize), then ask the assistant to run get_user_details to confirm the connection.

Claude Code

The quick form shown on this page:

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

If the client needs your connector's credentials, Claude Code accepts pre-configured OAuth credentials. Register http://localhost:8080/callback as a redirect URL on the connector, then run:

claude mcp add --transport http \
  --client-id YOUR_CLIENT_ID --client-secret --callback-port 8080 \
  hubspot https://mcp.hubspot.com

--client-secret prompts for the secret. Run /mcp in Claude Code to sign in.

Cursor

Add a remote server entry to ~/.cursor/mcp.json (or the project's .cursor/mcp.json):

{
  "mcpServers": {
    "hubspot": {
      "url": "https://mcp.hubspot.com"
    }
  }
}

VS Code

Add the server to .vscode/mcp.json:

{
  "servers": {
    "hubspot": {
      "type": "http",
      "url": "https://mcp.hubspot.com"
    }
  }
}

In Cursor and VS Code, use your MCP connector's client ID, secret and a matching redirect URL if the client asks for OAuth client credentials.

To test with MCP Inspector, use the Streamable HTTP transport with https://mcp.hubspot.com/ and add http://localhost:6274/oauth/callback/debug as a connector redirect URL.

Key features of HubSpot MCP Server (Official)

• Official and hosted: run by HubSpot at https://mcp.hubspot.com, Streamable HTTP transport, no local process.
• OAuth with PKCE: sign in through HubSpot; no tokens to paste into config files.
• Broad CRM read access: contacts, companies, deals, tickets, leads, users, appointments, projects, services, custom objects and segments, plus calls, emails, meetings, notes and tasks.
• Write access where permitted: create and edit CRM records, activities, pipelines, custom properties and static segments; conditional field logic and pipeline stage validations are respected.
• Marketing and content: campaigns, marketing email drafts and analytics, landing pages, website pages and blog posts.
• Conversations: live chat, team email, WhatsApp, SMS, Facebook Messenger and custom channels, depending on inbox configuration.
• Permission-aware: every request runs as the installing user, and Super Admins control the connector's data permissions.

HubSpot MCP Server (Official) tools

Tool availability varies by subscription, permissions and account configuration:

• Account and schema: get_user_details, get_organization_details and discover_hubspot_schema identify the user, the portal and its object model.
• CRM records: search_crm_objects (up to 5 filter groups, 6 filters per group, 200 results per page), get_crm_objects (up to 100 IDs per request), manage_crm_objects and manage_segment.
• Data and properties: query_crm_data for structured queries (call tool_guidance first), plus search_properties, get_properties, manage_custom_properties, manage_custom_pipelines and search_owners.
• Campaigns and marketing: read_campaign_data, manage_campaign_objects, get_campaign_attribution_reports, get_marketing_email_analytics and manage_marketing_email.
• Content: manage_landing_page, manage_website_page, manage_blog_post, render_asset and get_content_analytics_report.
• Conversations and signals: search_conversations, get_conversation_channel_metadata and search_intent_signals.
• AEO: get_aeo_metrics, manage_aeo_prompts and manage_aeo_recommendations (Marketing Hub Professional or Enterprise).

Several write tools, such as manage_crm_objects and manage_blog_post, ask for user confirmation before changing data.

Use cases of HubSpot MCP Server (Official)

• Pipeline review: "Summarize every open deal over $50k that has had no activity in the last 14 days."
• Account research before a call: "Pull the latest notes, emails and meetings for Acme Corp and list open tickets."
• CRM hygiene: "Find contacts at example.com with no owner and assign them to me."
• Logging work: "Log a call with Jane Doe today and create a follow-up task for next Tuesday."
• Marketing analysis: "How did last month's marketing emails perform?"

HubSpot MCP Server (Official) vs alternatives

• HubSpot Developer MCP server (official, local): installed with HubSpot CLI 8.2.0+ via hs mcp setup for Claude Code, Codex CLI, Cursor, Gemini CLI, VS Code and Windsurf. It helps build apps and CMS assets, not query CRM data.
• Community servers: mcp-hubspot (Docker, FAISS-based semantic search over retrieved data) and Shinzo Labs HubSpot MCP (npx or Smithery) authenticate with a HubSpot access token instead of OAuth. They are not maintained by HubSpot.

Troubleshooting HubSpot MCP Server (Official)

• OAuth redirect errors: the redirect URL sent by your client must exactly match one registered on the MCP connector. The first redirect URL listed is the default.
• PKCE or token errors: PKCE is required. The code_verifier must be 43 to 128 characters and the challenge must use code_challenge_method=S256. If a refresh token has expired or been invalidated, rerun the full OAuth flow.
• New tools or data are missing: scopes are granted at install time. After HubSpot adds tools or a Super Admin changes permissions, reinstall or reconnect to grant the new scopes.
• No activity or conversation data: if Sensitive Data is enabled in the account, the MCP server blocks activity and conversation data.