MCP-compliant server for retrieving customer support tickets from Intercom
For Intercom MCP server exists for a simple reason — assistants are far more useful when they can act on For Intercom directly instead of describing what you should do. MCP-compliant server for retrieving customer support tickets from Intercom.
An MCP-compliant server that enables AI assistants to access and analyze customer support data from Intercom.
Once For Intercom is connected, these are the calls the assistant has available:
Prerequisites — The Prerequisites tool exposed by this serverThe server ships on npm as mcp-server-for-intercom, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
You will need one environment variable: INTERCOM_ACCESS_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. For Intercom's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by raoulbia-ai; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against For Intercom's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
{
"mcpServers": {
"server-for-intercom": {
"command": "npx",
"args": ["-y", "mcp-server-for-intercom"],
"env": {
"INTERCOM_ACCESS_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| INTERCOM_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.