Can the Intercom server update conversations?

Intercom's server is read-oriented: it exposes search and fetch tools for conversations and contacts so an agent can pull context. For writing back to a CRM record, HubSpot's server supports searching, reading, and updating CRM objects.

Do both require a local install?

No. Both are official remote servers over OAuth, so each user authorizes their own HubSpot or Intercom account in the client and there is no local process to run.

HubSpot vs Intercom

HubSpot MCP and Intercom MCP both connect an agent to customer data over an official remote OAuth server, but they front different systems of record. HubSpot is a CRM, and its server lets an agent search, read, and update CRM objects — contacts, companies, deals — along with properties, owners, and campaign analytics. Intercom is a customer-communication and support platform, and its server is read-oriented: search and fetch conversations and contacts so an agent can pull support history and context. Both are official, hosted, and OAuth-authenticated, so each user authorizes their own account with no local process to run. The split is less about transport and more about which side of the customer relationship each tool governs. Here is a balanced look at how they differ on data domain, write access, and the kind of customer work each suits best.

How they compare

Dimension	HubSpot	Intercom
System of record	CRM: contacts, companies, deals, and pipelines — the structured record of accounts and revenue.	Support/messaging: conversations and contacts — the record of customer communication and support history.
Write access	Read and write: the agent can search, read, and update CRM objects and manage properties.	Read-oriented: the agent searches and fetches conversations and contacts rather than mutating support data.
Analytics	Includes campaign analytics, asset metrics, and owner lookups for marketing and sales context.	Focused on retrieving conversation and contact context rather than surfacing campaign or revenue analytics.
Deployment	Official remote server over OAuth; each user authorizes their HubSpot account, no local process.	Official remote server over OAuth; each user authorizes their Intercom workspace, no local process.
Best-fit task	Driving sales and marketing workflows: enrich and update records, pull deal context, and read campaign performance.	Surfacing support context: let an agent read a customer's conversation history and contact details to inform a reply or summary.

Verdict

Pick by which customer system you want the agent to act on. Reach for HubSpot MCP when the work is CRM-centric — updating contacts and deals, pulling pipeline context, or reading campaign analytics — and you want write access to keep records current. Reach for Intercom MCP when the work is support-centric and the agent mainly needs to read conversation history and contact context to summarize, triage, or draft replies. Many teams run both: Intercom to understand what a customer has said and HubSpot to act on the account record. If your priority is updating the source of truth for accounts and revenue, HubSpot; if it is retrieving support conversations and contact context, Intercom.

FAQ

Can the Intercom server update conversations?: Intercom's server is read-oriented: it exposes search and fetch tools for conversations and contacts so an agent can pull context. For writing back to a CRM record, HubSpot's server supports searching, reading, and updating CRM objects.
Do both require a local install?: No. Both are official remote servers over OAuth, so each user authorizes their own HubSpot or Intercom account in the client and there is no local process to run.