HubSpot MCP Server: Remote, Developer and Alternatives

HubSpot MCP Server: Remote, Developer and Alternatives

The HubSpot MCP server connects AI clients such as Claude, ChatGPT or Gemini to a HubSpot account through the Model Context Protocol (MCP), the open standard for letting AI clients call tools in other systems. HubSpot runs two different MCP servers: a remote server for working with CRM and marketing data, and a local developer server for building HubSpot apps and CMS content.

This guide summarizes both from HubSpot's developer documentation as of 27 September 2026 and compares them with a CRM whose MCP server is part of the product. Disclosure: Customermates, the second CRM discussed here, publishes this guide.

At a glance

Remote HubSpot MCP server

Reads and writes CRM records, activities and marketing content at mcp.hubspot.com. Generally available to all HubSpot accounts since April 2026.

Developer MCP server

Runs locally through the HubSpot CLI and helps with app and CMS development.

Main limits

No deletes, activity data blocked when sensitive data is on, and paged results.

Built-in alternative

A CRM with its own MCP endpoint, such as Customermates, connects without creating an app; the trade-off is that it has no marketing features.

The remote HubSpot MCP server

HubSpot announced on 13 April 2026 that its remote MCP server had graduated from beta and was generally available to all HubSpot accounts. It runs at https://mcp.hubspot.com.

What it can read. According to the integration guide, CRM records such as contacts, companies, deals, tickets and custom objects, activities such as calls, emails, meetings, notes and tasks, and marketing content such as campaigns, landing pages, blog posts and marketing emails, plus conversations and account details.

What it can write. Create and edit contacts, companies, deals, tickets, leads, line items and products, log activities, create follow-up tasks, draft or log emails, and work with content, campaigns, pipelines, custom properties and segments.

Limits HubSpot documents.

• delete operations are not supported;
• if the account has sensitive data turned on, activity and conversation data is blocked;
• searches return at most 200 results per page, and fetches take up to 100 IDs per request;
• some tools need specific subscriptions, such as quote management on a Professional or Enterprise revenue tier and AEO metrics on Marketing Hub Professional or higher.

Permissions. HubSpot states that every action respects the user's existing HubSpot permissions, so people can only read or change what they could already see or edit.

How to connect it

1. In HubSpot, create an MCP auth app (connector) in the Development area, with a name and a redirect URL.
2. Copy its client ID and client secret.
3. Configure your MCP client with those credentials and the server address https://mcp.hubspot.com.
4. Complete the OAuth flow, choose the account and grant the requested permissions.

The client must support OAuth with PKCE. HubSpot names MCP Inspector, Claude, ChatGPT and Gemini as examples.

The HubSpot developer MCP server

The developer MCP server runs locally and is set up with the HubSpot CLI (hs mcp setup, CLI version 8.2.0 or later). It helps coding assistants such as Claude Code, Codex CLI, Cursor, Gemini CLI, VS Code and Windsurf scaffold HubSpot apps, work with CMS assets and look up developer documentation. It is a development tool, not a way for sales teams to work with CRM data.

What the HubSpot MCP server is good for

For teams already on HubSpot, the remote server is a strong option: it covers both CRM and marketing objects, it is available on every account, and permissions carry over from HubSpot. Typical uses are asking an AI client for a summary of a deal's recent activity, logging notes after a call, drafting a follow-up email or updating properties in bulk from a conversation.

The trade-offs are the setup step (someone creates the auth app), the missing delete operations, and the fact that sensitive-data accounts lose activity access through MCP. Features that depend on paid hubs stay tied to those subscriptions.

A CRM with a built-in MCP server

Customermates takes a different route: the MCP endpoint is part of the CRM on every cloud plan and on self-hosted installations. For Claude and ChatGPT you add it as a custom connector, paste the endpoint URL and sign in; for command-line and editor clients you use an API key. A connected client discovers 49 tools for contacts, organizations, deals, services, tasks, custom fields, dashboards and webhooks, and on plans with messaging for the unified inbox across email, LinkedIn, WhatsApp, Instagram and Telegram.

Because deletes and sends are possible, the confirmation question matters. The Customermates MCP server instructions tell clients to confirm before deletes and sends, but the confirmation happens in the client; once an authorized client calls a tool, the server executes it. Check how your client handles approvals and start with reads and drafts. The agentic CRM guide covers this in detail.

When to use which

• You run HubSpot and it stays: use the remote HubSpot MCP server. Start with read-heavy tasks and a small group of users.
• You build on HubSpot: add the developer MCP server to your coding assistant.
• You want a CRM that AI clients operate from day one, with a unified inbox and an open-source core: a CRM with a built-in MCP server is the shorter path. See the HubSpot alternative comparison.
• You use Salesforce: the Salesforce MCP guide explains its hosted and developer servers.

Frequently asked questions