HubSpot Developer MCP or CRM MCP? Choose for the question you need answered

Choose the right HubSpot MCP connection for app development, CRM access or HubSpot–Stripe analysis. Includes a decision table and a free SQL exercise.

By the Combined team · September 14, 2026

Choose Combined when your agent needs to analyze HubSpot alongside Stripe or other business sources. It gives the agent scoped, read-only SQL over synced datasets. HubSpot also offers two different MCP servers: Developer MCP for building apps and CMS assets, and remote CRM MCP for interacting with HubSpot account data. Pick the connection for the task, then check the actual tools and data available to your agent.

Three connections, three starting points

Choose by workload, then verify the required data
Your task	Start here	First check
Compare open CRM pipeline with paid Stripe invoices	Combined MCP	Both sources synced, required datasets granted and customer mapping available
Build a HubSpot app or CMS content asset locally	HubSpot Developer MCP	The development tools needed by your project are exposed
Query or perform supported operations on HubSpot account records	HubSpot remote CRM MCP	Your installed tools and user permissions cover the operation

HubSpot explicitly distinguishes the Developer server from the remote CRM server in its MCP documentation. Seeing “HubSpot MCP connected” is therefore not enough to identify what an agent can do. Inspect the configured server and its tool list before changing permissions or rewriting a prompt.

For a concrete comparison before connecting anything, open the free CRM/billing join lab. It shows why two valid source responses can still produce an incorrect combined total.

What the direct HubSpot CRM route requires

HubSpot documents its remote CRM endpoint at https://mcp.hubspot.com. Its setup uses an MCP auth app and an OAuth client with PKCE support. Match the client's redirect URL to the app's configuration, select the intended HubSpot account and review the permissions during authorization.

The current server supports reads and selected writes; access follows the installed tools and the user's permissions. Check HubSpot's current supported-data list for your objects. Do not assume that installing a development server provides the same CRM access, or that a successful login exposes every object.

Use the direct route when the required work fits those HubSpot tools. For a recurring analysis that also needs billing or product records, decide where the shared dataset, customer mapping and calculation will live. That is the role Combined takes in the next workflow.

Use Combined for HubSpot plus Stripe analysis

A question such as “Which companies have open deals but no matched paid invoices in this period?” needs both systems and an explicit definition of a match. Combined collects the selected records and lets the agent query the granted data together. You keep one calculation that can be inspected and repeated.

Connect HubSpot and Stripe in Combined and complete each source's authorization.
Select the required datasets and fields, run the initial sync and inspect them in Explore.
Provide a maintained mapping from Stripe customer IDs to HubSpot company IDs.
Grant the agent the relevant datasets through Access.
Add the account-specific Combined MCP endpoint to the agent client.

https://platform.trycombined.com/mcp?account_id=ACCOUNT_UUID

Replace ACCOUNT_UUID with the account ID from Combined. It identifies the account and is not a credential. Use the product-generated connection instructions and the MCP reference for authentication. The Cursor walkthrough provides downloadable configuration; the Claude Code guide covers the CLI client.

Copy a question with the matching rules included

Use Combined to discover my permitted HubSpot and Stripe datasets.
Compare current open pipeline with paid invoices for the UTC
period I specify, grouped by mapped company and currency.

Inspect relation names and fields before writing SQL.
Use my maintained Stripe-customer-to-HubSpot-company mapping.
Report missing or ambiguous mappings separately.
Aggregate deals and invoices separately before joining the totals.
Keep currencies separate. Do not call invoice amount paid MRR.
Include source freshness, the query receipt and coverage limits.
If the period or mapping is missing, ask for it before calculating.

A company with two deals and three invoices produces six rows in a naive join. Summing those joined rows can repeat each deal three times and each invoice twice. Aggregate both sources to company and currency before joining. The worked HubSpot–Stripe tutorial includes the SQL and expected results for a fixed sample.

Download the account-free HubSpot–Stripe SQL fixture to inspect the calculation without connecting production data. Its names and records are illustrative; use discovery to adapt it to your own datasets.

Fix the mismatch before adding another connector

The agent only sees development tools: Check which HubSpot server you installed. Select a CRM-data connection for a CRM-record question.
Combined connects, but no HubSpot source is visible: Verify the account ID, agent identity and source grant. A working MCP transport does not grant dataset access.
Both sources appear, but totals look too large: Check mapping uniqueness and row grain before the join. Run the free lab to reproduce the duplication pattern.
The agent needs to change a CRM record: Combined's documented MCP data surface is read-only. Use an authorized action tool for a supported write and keep the analysis query as its evidence.

For connection errors, follow the MCP authentication troubleshooting guide. For the broader product choice, compare direct MCP with a managed data layer.

Sources and further reading

Explore the documentation behind this guide. Product details checked on September 14, 2026.