Intercom MCP Server
Intercom data accessibility for your AI models using authorized connections.
Data last scanned today · Reviewed today
Overview
The Intercom MCP Server provides a standardized interface for AI assistants to interact directly with your workspace data. It enables models to search across conversations and contacts using a query DSL, allowing for specific filtering by status, source, or custom field criteria. Beyond search capabilities, the server includes a fetch tool to retrieve full, detailed resource information once a target ID is identified. Supported by Intercom's official infrastructure, the server utilizes authenticated remote connections to manage requests while maintaining context within your customer support ecosystem.
Our verdict
This server carries a high risk rating with a security score of 44/100, primarily due to the lack of an explicit open-source license and the absence of a read-only mode, which grants full write-capable access to your environment. While it is maintained by the official vendor and supports OAuth, potential users should proceed with caution given the lack of recent code updates—with the last commit occurring over 300 days ago—and the significant single-contributor bus factor.
- Maintained directly by the official Intercom organization
- Uses OAuth authentication for managed access control
- Zero direct dependencies minimize supply-chain exposure
- Supports detailed object retrieval via specific resource IDs
- High-risk profile with no defined software license
- No read-only mode limits granular permission management
- Last repository update occurred over 313 days ago
- Restricted currently to US-hosted workspaces only
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›Which Intercom workspaces are supported by this MCP server?
The Intercom MCP server is currently supported only in US-hosted workspaces.
›Does the server support different connection protocols?
The recommended connection method is Streamable HTTP via the URL https://mcp.intercom.com/mcp, while the Legacy SSE URL is maintained only for backwards compatibility.
›What authentication methods can be used to connect to the server?
The server supports two authentication approaches: an automatic browser-based OAuth flow, which is recommended, or direct authentication using a Bearer token.
›Are there specific requirements for using a Bearer token?
If using a Bearer token, you must ensure that your access token includes all required scopes necessary for the server to access your workspace data.
›How do I perform searches using the Universal search tool?
You must specify whether you are searching for conversations or contacts using the object_type parameter, and you can utilize a query DSL to perform field-based or free-text searches.
Badge
Maintain this server? Add the live badge to your README.