BUSINESS SYSTEMS AND DEVELOPMENT / HubSpot
HubSpot MCP Server
Query CRM context and perform permission-scoped CRM, content and marketing changes.
“… this remote server acts as a bridge between AI systems and HubSpot’s APIs …”
01 / THE REASONING
Why this made the selection.
- Official hosted integration with documented authentication and account permissions.
- Investigate a bounded set of deals or customer records and their associated activities.
- HubSpot’s developer page says the remote MCP server acts only within the connecting user’s existing permissions, and that OAuth uses PKCE.
- The product page says the CRM server can read and write standard records but does not allow access to custom sensitive-data properties.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server
- https://developers.hubspot.com/ai-tools/mcp
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.
Our findings
- The September 30 publisher guide documents current write surfaces and Sensitive Data restrictions; this record does not carry forward older read-only claims.
- The remote CRM service is distinct from the local HubSpot developer MCP for building apps and CMS assets.
- The integration guide says every action respects existing HubSpot user permissions, so users can only view and modify records they can already access.
- OAuth uses PKCE for all authentication flows. If the client does not handle PKCE, the page says the integrator has to implement it.
- The product page says the CRM MCP server provides read and write access to contacts, deals, and engagements, and that it does not allow access to custom sensitive-data properties, including personal health information.
- Available scopes are determined by the server tools and user permissions, and existing installations must be reinstalled to approve newly introduced scopes.
Not established by this review
- Server startup, authentication, live tool execution and security isolation were not tested.
- Published package/container parity with a source revision and hosted implementation internals were not tested.
- The resource was not executed and its tools were not called.
- The server was not called. A source review is not a runtime or security certification.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
- Create an MCP connector under Development > MCP Connectors. Its scopes follow the server’s tools and the permissions the installing user grants.
- Point the MCP client at https://mcp.hubspot.com and complete the OAuth flow with PKCE.
- Review which tools are billable or tier-gated before enabling write tools.
Before you start
- A HubSpot account on the new Developer Platform.
- An MCP client supporting OAuth 2.0 with PKCE.
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server
Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports
https://developers.hubspot.com/ai-tools/mcp
Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports