Does HubSpot provide more than one MCP server?
Yes. HubSpot documents a remote CRM MCP server and a separate local Developer MCP server.
Connects AI clients to HubSpot CRM contacts, companies, deals, engagements, and developer workflows.
Looking for more MCP servers? Browse the full MCP tools directory or explore more tools in CRM.
HubSpot MCP is a CRM control surface, not a simple contact lookup. The remote server can provide read and write access to contacts, companies, deals, engagements, and related objects, while the developer MCP server is a separate local CLI-based surface for HubSpot Developer Platform work. That distinction is the architecture: CRM data and developer-platform administration must not be treated as interchangeable permissions. A natural-language request to “update this deal” can alter pipeline state, ownership, stage, forecast, lifecycle history, and downstream automation, so the agent needs object ID, portal, object type, property name, association context, and permission scope before writing. Use HubSpot's OAuth-backed remote endpoint for CRM data, grant only the scopes required, separate read from write sessions, and require a diff before any record mutation. A silent failure occurs when the OAuth session is valid but points to a different HubSpot portal, user-level application, or object scope; the response looks correct while describing an unintended CRM context. Require portal ID, OAuth application, user identity, object type, record ID, and property scope in every preflight response. HubSpot MCP is strongest when CRM operations remain auditable and portal-scoped rather than becoming invisible side effects of conversational automation.
Choose HubSpot MCP Server when you want an MCP server focused on CRM and need tighter integration with your existing tools.
Good fit
Use the following configuration as a starting point for Claude Desktop or any compatible MCP client, then replace placeholder credentials with your own values.
{
"mcpServers": {
"hubspot": {
"url": "https://mcp.hubspot.com/"
}
}
}These setup steps cover the typical installation flow for this MCP server.
Choose the correct HubSpot MCP surface: the remote CRM server or the local developer MCP server.
Create a user-level HubSpot application on the new Developer Platform and grant only the CRM scopes required.
Configure the remote MCP endpoint and authenticate through OAuth.
Verify portal ID, user identity, scopes, and object access before retrieving or updating CRM data.
Test read-only contact, company, deal, and engagement queries before enabling writes.
Pro-Tip: Never let an agent write CRM properties without a reviewed diff; require portal ID, object type, record ID, property names, current values, proposed values, and association context before execution.
Common questions for HubSpot MCP Server.
Yes. HubSpot documents a remote CRM MCP server and a separate local Developer MCP server.
Yes, depending on the OAuth scopes and enabled tools. Write operations should require a reviewed diff and clear record and property context.
The session can authenticate to a valid HubSpot portal or application that is not the intended one. Fix it by exposing portal ID, OAuth application, user identity, scopes, object type, and record ID.
Require association type, source object, target object, current association state, and proposed change before creating or deleting associations.
| Feature | HubSpot MCP Server | Competitor |
|---|---|---|
| CRM Read/Write | ✅ Supports secure remote access to CRM objects through OAuth | ❌ Generic spreadsheet CRM connectors |
| Portal Scoping | ✅ Uses HubSpot portal, user, application, and scope context | ❌ Shared private-app access tokens |
| Developer Platform | ✅ Provides a separate local Developer MCP surface | ❌ One combined production-admin token |
| Association Awareness | ✅ Can reason over CRM objects and associations | ❌ Flat contact-export automation |