MCP Server for Intercom
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INTERCOM_ACCESS_TOKEN | Yes | Your Intercom API token (available in your Intercom account settings) |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_conversations_by_customerA | Searches for conversations by customer email or ID with optional date filtering. Required: customerIdentifier (email/ID) Optional: startDate, endDate (DD/MM/YYYY format) Optional: keywords (array of terms to filter by) Use when looking for conversation history with a specific customer. |
| search_tickets_by_statusA | Searches for tickets by status with optional date filtering. Required: status (one of: open, pending, resolved) Optional: startDate, endDate (DD/MM/YYYY format) Use when analyzing support workload or tracking issue resolution. |
| list_conversationsA | Retrieves Intercom conversations within a specific date range. Required: startDate, endDate (DD/MM/YYYY format, max 7-day range) Optional: keyword, exclude (for content filtering) Always ask for specific dates when user makes vague time references. |
| search_tickets_by_customerB | Searches for tickets by customer email or ID with optional date filtering. Required: customerIdentifier (email/ID) Optional: startDate, endDate (DD/MM/YYYY format) Use when analyzing a customer's support history. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/raoulbia-ai/mcp-server-for-intercom'
If you have feedback or need assistance with the MCP directory API, please join our Discord server