Intercom

Intercom's hosted MCP server provides customer-support context through conversations, contacts, search, and retrieval tools.

Connection specification

Remote endpoint
https://mcp.intercom.com/mcp
Browser access
Not yet measured
Declared MCP transport
Streamable HTTP
Live-validated MCP transport
Not yet verified — Latest validation did not verify a transport
Declared authentication
OAuth 2.1
Detected authentication
OAuth 2.1 detected or retained from publisher evidence
Alternative authentication
Bearer token
Protocol lifecycle
Not yet negotiated
Required header
Authorization — Optional Intercom access token alternative: Bearer <INTERCOM_ACCESS_TOKEN>
Category
Communication

Product documentation · Source repository · Official listing documentation

Provider guidance

  • Authorization could not be started in the 2026-08-24 audit: Intercom returned HTTP 401 without resource_metadata and both standard protected-resource metadata fallbacks returned HTTP 404. This is provider-side discovery evidence. Use the documented Intercom access-token alternative directly.

Browse all MCP servers · Test this endpoint in the MCP Playground

Authorization setup

Registration requirements not verified

The OAuth authorization and app-registration requirements for this exact endpoint have not been verified. A compatible client will request authorization, but follow the publisher documentation and do not guess client credentials or callbacks.

Publisher evidence reviewed .

Publisher documentation

Connect this server to your client

Claude Code setup

Run in a terminal. This user-scoped entry is available across projects.

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

Registration requirements not verified: The OAuth authorization and app-registration requirements for this exact endpoint have not been verified. A compatible client will request authorization, but follow the publisher documentation and do not guess client credentials or callbacks.

  • Using live-validated endpoint: https://mcp.intercom.com/mcp
  • Registration requirements not verified: The OAuth authorization and app-registration requirements for this exact endpoint have not been verified. A compatible client will request authorization, but follow the publisher documentation and do not guess client credentials or callbacks.
  • Publisher evidence (reviewed 2026-08-24): https://developers.intercom.com/docs/guides/mcp
  • Optional bearer token alternative: Store INTERCOM_ACCESS_TOKEN in your operating system keychain, secret manager, or protected environment; never commit the value. The Authorization header syntax is Bearer <INTERCOM_ACCESS_TOKEN>.
  • Provider guidance: Authorization could not be started in the 2026-08-24 audit: Intercom returned HTTP 401 without resource_metadata and both standard protected-resource metadata fallbacks returned HTTP 404. This is provider-side discovery evidence. Use the documented Intercom access-token alternative directly.
  • After adding the server, open Claude Code, run /mcp, select the server, and follow the browser flow to authenticate.

Claude Code MCP documentation

Codex CLI setup

Run in a terminal; Codex stores the entry in ~/.codex/config.toml.

codex mcp add 'intercom' --url 'https://mcp.intercom.com/mcp'
codex mcp login 'intercom'

Registration requirements not verified: The OAuth authorization and app-registration requirements for this exact endpoint have not been verified. A compatible client will request authorization, but follow the publisher documentation and do not guess client credentials or callbacks.

  • Using live-validated endpoint: https://mcp.intercom.com/mcp
  • Registration requirements not verified: The OAuth authorization and app-registration requirements for this exact endpoint have not been verified. A compatible client will request authorization, but follow the publisher documentation and do not guess client credentials or callbacks.
  • Publisher evidence (reviewed 2026-08-24): https://developers.intercom.com/docs/guides/mcp
  • Optional bearer token alternative: Store INTERCOM_ACCESS_TOKEN in your operating system keychain, secret manager, or protected environment; never commit the value. The Authorization header syntax is Bearer <INTERCOM_ACCESS_TOKEN>.
  • Provider guidance: Authorization could not be started in the 2026-08-24 audit: Intercom returned HTTP 401 without resource_metadata and both standard protected-resource metadata fallbacks returned HTTP 404. This is provider-side discovery evidence. Use the documented Intercom access-token alternative directly.

Codex MCP documentation

Cursor setup

Add to .cursor/mcp.json for this project, or ~/.cursor/mcp.json for all projects.

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

Registration requirements not verified: The OAuth authorization and app-registration requirements for this exact endpoint have not been verified. A compatible client will request authorization, but follow the publisher documentation and do not guess client credentials or callbacks.

  • Using live-validated endpoint: https://mcp.intercom.com/mcp
  • Registration requirements not verified: The OAuth authorization and app-registration requirements for this exact endpoint have not been verified. A compatible client will request authorization, but follow the publisher documentation and do not guess client credentials or callbacks.
  • Publisher evidence (reviewed 2026-08-24): https://developers.intercom.com/docs/guides/mcp
  • Optional bearer token alternative: Store INTERCOM_ACCESS_TOKEN in your operating system keychain, secret manager, or protected environment; never commit the value. The Authorization header syntax is Bearer <INTERCOM_ACCESS_TOKEN>.
  • Provider guidance: Authorization could not be started in the 2026-08-24 audit: Intercom returned HTTP 401 without resource_metadata and both standard protected-resource metadata fallbacks returned HTTP 404. This is provider-side discovery evidence. Use the documented Intercom access-token alternative directly.

Cursor MCP documentation

VS Code setup

Add to .vscode/mcp.json, or run “MCP: Open User Configuration” for a private user-level entry.

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

Registration requirements not verified: The OAuth authorization and app-registration requirements for this exact endpoint have not been verified. A compatible client will request authorization, but follow the publisher documentation and do not guess client credentials or callbacks.

  • Using live-validated endpoint: https://mcp.intercom.com/mcp
  • Registration requirements not verified: The OAuth authorization and app-registration requirements for this exact endpoint have not been verified. A compatible client will request authorization, but follow the publisher documentation and do not guess client credentials or callbacks.
  • Publisher evidence (reviewed 2026-08-24): https://developers.intercom.com/docs/guides/mcp
  • Optional bearer token alternative: Store INTERCOM_ACCESS_TOKEN in your operating system keychain, secret manager, or protected environment; never commit the value. The Authorization header syntax is Bearer <INTERCOM_ACCESS_TOKEN>.
  • Provider guidance: Authorization could not be started in the 2026-08-24 audit: Intercom returned HTTP 401 without resource_metadata and both standard protected-resource metadata fallbacks returned HTTP 404. This is provider-side discovery evidence. Use the documented Intercom access-token alternative directly.

VS Code MCP documentation

Latest validation evidence

Validation status
Online when last tested
Validation checked at
Aug 24, 2026 at 2:00 AM
Validation detail
Authorization could not be started: HTTP 401 omitted resource_metadata and both standard protected-resource metadata fallbacks returned HTTP 404; bearer-token alternative is available