About MCP Intercom Server
MCP Intercom Server is a read-only MCP server for LLMs that need to query and analyze Intercom conversations. It supports filters such as dates and state, and returns conversation, contact, and statistics data.
Key features
- 01Search conversations with filters
- 02Filter by creation or update date
- 03Filter by source, state, and read status
- 04Return contact and conversation statistics
- 05Authenticate with an Intercom API key
Use cases
- 01Find conversations in a date range
- 02Review unread or open conversations
- 03Analyze response and reopen statistics
MCP support
The MCP server exposes an Intercom conversation search tool to MCP clients, with optional filters. It provides read-only access to conversations.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEMCP Intercom Server
A Model Context Protocol (MCP) server that provides access to Intercom conversations and chats. This server allows LLMs to query and analyze your Intercom conversations with various filtering options.
Features
- Query Intercom conversations with filtering options:
- Date range (start and end dates)
- Customer ID
- Conversation state
- Secure access using your Intercom API key
- Rich conversation data including:
- Basic conversation details
- Contact information
- Statistics (responses, reopens)
- State and priority information
Installation
- Clone the repository:
git clone https://github.com/fabian1710/mcp-intercom.git
cd mcp-intercom
- Install dependencies:
npm install
- Set up your environment:
cp .env.example .env
- Add your Intercom API key to
.env:
INTERCOM_API_KEY=your_api_key_here
- Build the server:
npm run build
Usage
Running the Server
Start the server:
npm start
Using with Claude for Desktop
- Add the server to your Claude for Desktop configuration (
~/Library/Application Support/Claude/claude_desktop_config.jsonon macOS or%AppData%\Claude\claude_desktop_config.jsonon Windows):
{
"mcpServers": {
"intercom": {
"command": "node",
"args": ["/path/to/mcp-intercom/dist/index.js"],
"env": {
"INTERCOM_API_KEY": "your_api_key_here"
}
}
}
}
- Restart Claude for Desktop
Available Tools
search-conversations
Searches Intercom conversations with optional filters.
Parameters:
createdAt(optional): Object withoperator(e.g., ">", "<", "=") andvalue(UNIX timestamp) for filtering by creation date.updatedAt(optional): Object withoperator(e.g., ">", "<", "=") andvalue(UNIX timestamp) for filtering by update date.sourceType(optional): Source type of the conversation (e.g., "email", "chat").state(optional): Conversation state to filter by (e.g., "open", "closed").open(optional): Boolean to filter by open status.read(optional): Boolean to filter by read status.
Example queries:
- "Search for all conversations created after January 1, 2024"
- "Find conversations updated before last week"
- "List all open email conversations"
- "Get all unread conversations"
Security
- The server requires an Intercom API key to function
- API key should be stored securely in environment variables
- The server only provides read access to conversations
- All API requests are made with proper authentication
Development
- Start development mode with auto-recompilation:
npm run dev
- Run linting:
npm run lint
Contributing
- Fork the repository
- Create a new branch for your feature
- Make your changes
- Submit a pull request
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.