This MCP server provides a set of Intercom-centric content management and CS workflow tools. It exposes operations for managing Help Center articles and collections, including multilingual support, as well as CS-related actions such as replying to conversations, adding internal notes, closing conversations, and updating tickets. Once configured, you can invoke commands like get_article, list_articles, search_articles, create_article, update_article, list_collections, get_collection, update_collection, delete_collection, and the CS tools to respond to conversations or modify tickets. The server is designed to be used through Claude Code/Claude Desktop integrations, allowing you to run natural language prompts that map to these MCP operations. Expect multilingual content handling and translation capabilities for articles and collections, with the ability to specify translated_content blocks for various locales.

Prerequisites:

• Node.js (v14+ recommended) and npm installed on your system
• Access token and admin ID for Intercom (as required by CS tools)

Installation steps:

1. Clone the repository git clone https://github.com/kaosensei/intercom-mcp.git cd intercom-mcp

2. Install dependencies npm install

3. Build the project npm run build

4. Run the MCP server (example)

   Ensure you replace the absolute path in mcp_config with your actual path

   node dist/index.js

5. (Optional) Run in development mode with environment variables INTERCOM_ACCESS_TOKEN=your_token INTERCOM_ADMIN_ID=your_admin_id node dist/index.js

6. Verify the server starts and is reachable via your configured transport (e.g., Claude integration)

Note: If you are packaging for distribution, ensure the dist/index.js path matches your build output. The MCP expects a Node.js entrypoint that exports the MCP handlers for Intercom articles, collections, and CS workflow actions.

Tips and common issues:

• Ensure INTERCOM_ACCESS_TOKEN has the necessary permissions for Articles and Conversations, and that INTERCOM_ADMIN_ID is provided for CS tools when calling admin-scoped actions.
• If translations are not returning expected content, verify translated_content payloads follow the structure shown in the README's multilingual examples.
• When deploying, keep environment variables secure and avoid hard-coding tokens in code.
• If Claude Desktop integration fails to reflect new capabilities after an update, rebuild the project and restart the MCP server, then refresh Claude’s MCP configuration.
• Check that your Intercom app has the required scopes for both Articles and Conversations to avoid permission errors.
• For testing, use the example payloads in the Tools Reference section of the README to validate each operation before integrating into automated workflows.