Intercom MCP — Remote MCP Server

Intercom's remote MCP lets agents pull conversation context and contact records into support and triage workflows — and reply on your behalf when you approve it. Streamable HTTP transport with OAuth 2.1 authorization.

Endpoint & Transport

• Endpoint URL: https://mcp.intercom.com/mcp
• Transport: Streamable HTTP

Authentication

Intercom MCP uses OAuth 2.1 — the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow — PKCE and Dynamic Client Registration, so no manual client setup is needed — and simply open a browser consent screen.

Available Tools (3)

Connect in 30 Seconds

Claude Code — one command:

claude mcp add --transport http intercom https://mcp.intercom.com/mcp

Cursor — add to ~/.cursor/mcp.json:

{ "mcpServers": { "intercom": { "url": "https://mcp.intercom.com/mcp" } } }

VS Code — add to .vscode/mcp.json:

{ "servers": { "intercom": { "type": "http", "url": "https://mcp.intercom.com/mcp" } } }

Claude Desktop & stdio clients — bridge with mcp-remote:

{ "mcpServers": { "intercom": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.intercom.com/mcp"] } } }

On first connect your client opens a browser OAuth consent screen — approve it and tools become available immediately.

Troubleshooting

• 401 Unauthorized on connect — that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact WWW-Authenticate challenge.
• "Session expired" / stale Mcp-Session-Id — just re-send initialize; stateless clients can ignore session headers entirely.
• reply_to_conversation sends a real message to the customer — clients will typically ask for confirmation.
• Access is scoped to the authorizing teammate's permissions.