How to add Intercom MCP to Cursor

Intercom's hosted MCP server: search and fetch conversations and contacts from your US workspace over OAuth. Paste the config into ~/.cursor/mcp.json and restart Cursor.

Last updated June 14, 2026 · 7★ · http · oauth · official

Cursor config for Intercom MCP

npx mcp-remote https://mcp.intercom.com/mcp

{
  "mcpServers": {
    "intercom-mcp": {
      "url": "https://mcp.intercom.com/mcp",
      "type": "streamable-http"
    }
  }
}

Remote server — no local install needed. Restart the client after saving the config.

Setup steps

1Open Cursor → Settings → MCP → Add new MCP server (or edit ~/.cursor/mcp.json directly).
2Paste the Intercom MCP config below into the "mcpServers" object.
3Fill in placeholder secrets, then save.
4Cursor reloads MCP servers automatically — check Settings → MCP for a green status dot.
5Ask Cursor to use one of Intercom MCP's tools to confirm it's connected.

Before you start

An Intercom workspace hosted in the US region (other regions not yet supported)
OAuth login in the browser, or an Intercom access token with 'read users and companies' and 'read conversations' scopes
Node.js/npx if your client is stdio-only and needs the mcp-remote bridge (e.g. Claude Desktop)

What Intercom MCP can do in Cursor

search

Universal query-DSL search across conversations or contacts (object_type required, field operators, pagination).

fetch

Retrieve the full record for an ID returned by search, including conversation parts and custom attributes.

search_conversations

Search conversations with filters for source type, author, state, and timing statistics.

get_conversation

Get a single conversation by ID with all parts and metadata.

search_contacts

Search contacts by ID, name, email, phone, custom attributes, or email domain.

get_contact

Get complete contact info including custom attributes, location, and activity timestamps.

Security

Hosted by Intercom with OAuth (recommended) or a bearer API token; a token needs read scopes for users/companies and conversations, so treat it as production support-data access and keep it out of shared configs. Tools are read-only — the server cannot send or modify anything — and only US-hosted workspaces are supported.

Intercom MCP + Cursor FAQ

Where is the Cursor config file?

Cursor reads MCP servers from ~/.cursor/mcp.json. Paste the Intercom MCP config there under the "mcpServers" key and restart the client.

Is Intercom MCP safe to use with Cursor?

Is the Intercom MCP server free and safe to connect?

There is no separate charge — it is part of the Intercom platform, gated by your existing workspace login and standard API rate limits. Safety-wise it is read-only (search and fetch only), OAuth-scoped to conversation and contact reads, and hosted by Intercom, so no customer data flows through third-party infrastructure.

Can it reply to customers or update records?

No. All six tools read data — search and fetch conversations and contacts. Sending replies, creating tickets, or editing attributes still requires the Intercom app or REST API; the MCP server is built for lookup, triage, and analysis.

Why can't my workspace connect?

Most likely region: only US-hosted Intercom workspaces are currently supported, so EU and AU workspaces cannot use the server yet. If you are US-hosted and still stuck, kill stale bridges (pkill -f mcp-remote), clear ~/.mcp-auth, and check that a bearer token carries the two required read scopes.

View repo Full Intercom MCP page