intercom

The Intercom MCP server exposes a standardized interface for AI tools to securely access and interact with your Intercom data (conversations, contacts, and related resources). By using the MCP remote endpoint, AI agents can run universal tools like search and fetch, as well as direct API tools such as search_conversations, get_conversation, search_contacts, and get_contact to locate and retrieve data with rich filtering and context. Authentication is supported via OAuth (recommended) or a Bearer token, ensuring actions are authorized for your workspace. To begin, configure an MCP client to point at https://mcp.intercom.com/mcp, authenticate, and then invoke the available tools through the channel you’ve chosen (for example, the mcp-remote utility). The server maintains a live connection to push updates when needed, enabling dynamic context for ongoing conversations and workflows.

Prerequisites:

• Node.js and npm installed on your machine
• Access to the Intercom MCP endpoint (requires region permissions and appropriate tokens)

Step 1: Install Node.js (if not already installed)

• Follow the instructions at https://nodejs.org/ to install Node.js and npm for your platform.

Step 2: Run the MCP server client configuration You don’t need to install a server package for the Intercom MCP server itself; instead you connect to the remote MCP server using the mcp-remote utility via npx. This requires no global installation beyond Node.js.

Step 3: Configure authentication (example using OAuth or Bearer token)

• OAuth (recommended): no extra credentials may be needed in the command if your provider handles it through the browser flow.
• Bearer token: supply the token in the auth header as shown in the example below.

Step 4: Launch the MCP client

• Use the following command to start using the Intercom MCP server:

npx mcp-remote https://mcp.intercom.com/mcp

If you need to pass a Bearer token:

npx mcp-remote https://mcp.intercom.com/mcp --header "Authorization:Bearer YOUR_TOKEN"

You can also embed this configuration in an mcp_config.json file (as shown in the examples) and reference it from your MCP client tooling.

Notes and tips:

• The Intercom MCP server supports two authentication methods: OAuth Flow (recommended) and Bearer Token. Ensure your token includes the required scopes: Read and list users and companies, and Read conversations.
• Available tools include universal tools (search, fetch) and direct API tools (search_conversations, get_conversation, search_contacts, get_contact). Use the search tool with a properly structured object_type (conversations or contacts) and field-based queries for filtering.
• If you encounter authentication or rate limiting issues, verify token permissions and reduce request frequency as needed. Use the MCP Inspector (npx @modelcontextprotocol/inspector) to verify connectivity and tool availability.
• For debugging, you can test connections with mcp-remote directly and inspect active connections via process checks or logs.
• The MCP server is region-specific (US hosted workspaces); ensure you are connecting to the correct URL and that your workspace permissions are valid.