[ MCP SERVER SUMMARY ]
Intercom MCP server summary
Intercom hosts a remote MCP server so AI tools can securely access customer support data and workflows. Bifrost connects over Streamable HTTP, manages OAuth, and applies tool allowlists for support and product agents.
| Property | Details |
|---|---|
| Company | Intercom |
| Connection type | HTTP |
| Authentication | OAuth 2.0 |
| Package or endpoint | https://mcp.intercom.com/mcp |
| Capabilities | Customer and conversation data, Support workflows, Secure remote MCP access |
| Official documentation | Intercom MCP documentation |
Before you start
- An Intercom workspace
- OAuth-capable MCP client setup
What you can do with Intercom
- Let support copilots query Intercom through Bifrost governance
- Prefer https://mcp.intercom.com/mcp over legacy SSE
- Separate read vs write support tools by virtual key
[ HOW TO CONNECT ]
Connect Intercom to Bifrost in three steps
Install Bifrost
Start the gateway locally or deploy in your VPC.
npx -y @maximhq/bifrost
Add Intercom in MCP Gateway
Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and choose HTTP. Or register via the API below.
• Recommended: https://mcp.intercom.com/mcp (Streamable HTTP).
• Legacy SSE https://mcp.intercom.com/sse is deprecated.
Point clients at Bifrost /mcp
Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to Intercom.
{
"mcpServers": {
"bifrost": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer vk_your_virtual_key"
}
}
}
}[ EXAMPLE CONFIG ]
Register Intercom via API
Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "intercom",
"connection_type": "http",
"connection_string": "https://mcp.intercom.com/mcp",
"auth_type": "oauth",
"tools_to_execute": [
"*"
]
}'[ WHY BIFROST ]
Run Intercom through one governed gateway
Access control
Virtual keys, RBAC, and tool allowlists per team or agent.
Cost governance
Attribute MCP tool spend alongside LLM usage in one view.
Observability
Log every tool call with latency, server, and virtual key metadata.
Credential isolation
Upstream secrets stay in the gateway — not on every laptop.
[ FAQ ]
Common questions
What does the Intercom MCP server do?
Intercom exposes customer and conversation data, support workflows, secure remote mcp access to MCP-compatible AI clients. Bifrost connects to it as an upstream MCP client and exposes approved tools through one governed /mcp endpoint.
How does Intercom authenticate when used with Bifrost?
Intercom uses OAuth 2.0. Store credentials in Bifrost's environment or credential configuration so they stay at the gateway instead of being copied into every AI client.
Can Claude Desktop, Cursor, or Claude Code use Intercom through Bifrost?
Yes. After registering Intercom in Bifrost, point any HTTP MCP-compatible client at the Bifrost /mcp endpoint and authenticate with a virtual key. The client sees only the tools allowed for that key.
[ RELATED SERVERS ]
More MCP integrations
Slack
Slack’s MCP server gives AI agents secure access to workplace conversations, channels, and collaboration context.
Asana
Connect AI assistants to Asana projects, tasks, teams, and work management workflows through Asana’s MCP server.
Gmail
Connect AI assistants to Gmail to search messages, draft and send email, and automate inbox workflows through Google Workspace MCP.