How to integrate Intercom MCP with Claude Agent SDK

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Intercom Logo
Claude Agent SDK Logo
divider

Introduction

This guide walks you through connecting Intercom to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Intercom agent that can add tag 'vip' to contact john doe, assign open conversation #123 to support team, create note for contact emily about refund, close all resolved conversations from today through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Intercom account through Composio's Intercom MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Intercom
  • Configure an AI agent that can use Intercom as a tool
  • Run a live chat session where you can ask the agent to perform Intercom operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the Intercom MCP server, and what's possible with it?

The Intercom MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Intercom account. It provides structured and secure access to your customer engagement platform, so your agent can perform actions like managing conversations, tagging contacts, creating articles, and updating company records on your behalf.

  • Conversation management and assignment: Let your agent assign conversations to teams or admins, create new conversations, and close them when resolved, streamlining your support workflow.
  • Contact tagging and note creation: Effortlessly tag contacts with relevant labels or add detailed notes for context, making customer follow-ups more organized and actionable.
  • Automated company and contact updates: Enable your agent to attach contacts to companies, create or update company records, and keep your Intercom data clean and up to date.
  • Article and collection creation: Let your agent publish new articles or create help center collections to expand your self-serve support resources without manual effort.
  • Subscription and message preferences management: Allow your agent to add or manage subscriptions for contacts, helping you personalize communication and respect user preferences automatically.

Supported Tools & Triggers

Tools
Add subscription to a contactYou can add a specific subscription to a contact.
Add tag to a contactYou can tag a specific contact.
Assign conversationAssigns a conversation to a specific admin or team in intercom
Attach a contact to a companyYou can attach a company to a single contact.
Close conversationCloses a conversation in intercom, marking it as resolved
Create a collectionYou can create a new collection by making a post request to `https://api.
Create an articleYou can create a new article by making a post request to `https://api.
Create a noteYou can add a note to a single contact.
Create conversationCreates a new conversation in intercom
Create or update a companyYou can create or update a company.
Delete a collectionYou can delete a single collection by making a delete request to `https://api.
Delete a companyYou can delete a single company.
Delete a contactYou can delete a single contact.
Delete an articleYou can delete a single article by making a delete request to `https://api.
Detach a contact from a companyYou can detach a company from a single contact.
Get a contactYou can fetch the details of a single contact.
Get conversationRetrieves a specific conversation by id with all messages and details
Identify an adminYou can view the currently authorised admin along with the embedded app object (a "workspace" in legacy terminology).
List all activity logsYou can get a log of activities by all admins in an app.
List all adminsYou can fetch a list of admins for a given workspace.
List all articlesYou can fetch a list of all articles by making a get request to `https://api.
List all collectionsYou can fetch a list of all collections by making a get request to `https://api.
List all companiesYou can list companies.
List all help centersYou can list all help centers by making a get request to `https://api.
List all notesYou can fetch a list of notes that are associated to a contact.
List attached companies for contactYou can fetch a list of companies that are associated to a contact.
List attached contactsYou can fetch a list of all contacts that belong to a company.
List attached segments for companiesYou can fetch a list of all segments that belong to a company.
List attached segments for contactYou can fetch a list of segments that are associated to a contact.
List conversationsLists conversations from intercom with filtering and pagination support
List subscriptions for a contactYou can fetch a list of subscription types that are attached to a contact.
List tags attached to a contactYou can fetch a list of all tags that are attached to a specific contact.
Merge a lead and a userYou can merge a contact with a `role` of `lead` into a contact with a `role` of `user`.
Remove subscription from a contactYou can remove a specific subscription from a contact.
Remove tag from a contactYou can remove tag from a specific contact.
Reopen conversationReopens a closed conversation in intercom
Reply to conversationSends a reply to an existing conversation in intercom
Retrieve a collectionYou can fetch the details of a single collection by making a get request to `https://api.
Retrieve a company by idYou can fetch a single company.
Retrieve a help centerYou can fetch the details of a single help center by making a get request to `https://api.
Retrieve an adminYou can retrieve the details of a single admin.
Retrieve an articleYou can fetch the details of a single article by making a get request to `https://api.
Retrieve companiesYou can fetch a single company by passing in `company id` or `name`.
Scroll over all companiesThe `list all companies` functionality does not work well for huge datasets, and can result in errors and performance problems when paging deeply.
Search conversationsSearches for conversations using query string with support for filtering and sorting
Search for articlesYou can search for articles by making a get request to `https://api.
Set an admin to awayYou can set an admin as away for the inbox.
Update a collectionYou can update the details of a single collection by making a put request to `https://api.
Update a companyYou can update a single company using the intercom provisioned `id`.
Update a contactYou can update an existing contact (ie.
Update an articleYou can update the details of a single article by making a put request to `https://api.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Intercom account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Intercom functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Intercom
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["intercom"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Intercom
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Intercom tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Intercom
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Intercom and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Intercom
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["intercom"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Intercom tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Intercom through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Intercom MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Intercom MCP with OpenAI Agents SDK

Google ADK

Google ADK

Use Intercom MCP with Google ADK

LangChain

LangChain

Use Intercom MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Intercom MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Intercom MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Intercom MCP with LlamaIndex

CrewAI

CrewAI

Use Intercom MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Intercom MCP?

With a standalone Intercom MCP server, the agents and LLMs can only access a fixed set of Intercom tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Intercom and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Claude Agent SDK?

Yes, you can. Claude Agent SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Intercom tools.

Can I manage the permissions and scopes for Intercom while using Tool Router?

Yes, absolutely. You can configure which Intercom scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Intercom data and credentials are handled as safely as possible.

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free