Intercom MCP Server is Intercom's official remote MCP entry point for support, customer, and Help Center context. The recommended Streamable HTTP endpoint is https://mcp.intercom.com/mcp, with legacy SSE kept only for backwards compatibility. Intercom's guide describes MCP as a secure standardized way for AI tools to find and retrieve Intercom data, access Intercom functionality, and keep workspace context available while working with AI assistants.
The strongest use case is support-aware agent work: searching conversations and contacts, retrieving contact and company details, listing and searching Help Center articles, and creating or updating articles when the token has the right permissions. That makes it useful for support operations, customer-success research, Fin and Help Center workflows, and internal agents that need to answer questions against real conversation history or support documentation instead of stale exports.
Keep the permission model visible in CMS copy. Intercom supports OAuth as the recommended browser-based flow and bearer-token authentication for direct API-token use. Required permissions include reading and listing users and companies, reading conversations, and reading or writing articles, so teams should scope tokens carefully before exposing support data to AI clients. The docs also describe pagination for larger search and list results, so copy should avoid implying one prompt can safely fetch every customer record. Avoid reliability, resolution-time, or answer-quality claims unless aicoolies runs separate hands-on tests.
