HubSpot launches the first CRM Deep Research Connector with ChatGPT via a remote MCP server
HubSpot's previous local MCP server required manual token creation and client configuration, limiting CRM AI access to technical developers. In parallel, HubSpot's public APIs were not originally designed to enforce user-level permissions, making a secure user-scoped AI connector difficult to deliver at scale across thousands of APIs maintained by hundreds of teams.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · User authenticates via OAuth
A user connects to HubSpot from within ChatGPT using OAuth authentication through the browser.
HubSpot shipped a browser-accessible remote MCP server that democratizes AI-powered CRM access for more than 250,000 businesses with enterprise-grade security and user-level permissions enforced, delivered as a production-ready feature in a matter of weeks.
What failed first
The prior local MCP server approach, published on NPM, required users to manually create Private App Access Tokens and configure MCP clients, introducing friction that blocked non-technical users and limited adoption.