How to integrate Sendbird MCP with LangChain

Framework Integration Gradient
Sendbird Logo
LangChain Logo
divider

Introduction

This guide walks you through connecting Sendbird to LangChain using the Composio tool router. By the end, you'll have a working Sendbird agent that can add users to a group chat channel, ban a disruptive user from group chat, get unread message count for a user, create a new group channel with members through natural language commands.

This guide will help you understand how to give your LangChain agent real control over a Sendbird account through Composio's Sendbird 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 OpenAI and Composio API keys
  • Connect your Sendbird project to Composio
  • Create a Tool Router MCP session for Sendbird
  • Initialize an MCP client and retrieve Sendbird tools
  • Build a LangChain agent that can interact with Sendbird
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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

The Sendbird MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Sendbird account. It provides structured and secure access to your in-app chat, voice, and video features, so your agent can perform actions like creating group channels, managing users, moderating conversations, and tracking unread message counts on your behalf.

  • Group channel management: Let your agent create new group channels, add or ban members, and delete channels as needed to keep conversations organized and secure.
  • User account administration: Automatically register new users or remove users from your Sendbird application, simplifying user lifecycle management.
  • Message moderation and cleanup: Empower your agent to delete specific messages—helping enforce community guidelines and remove unwanted content instantly.
  • Unread count and status tracking: Retrieve up-to-date counts of unread messages, mentions, and channel invitations for any user to surface important conversations.
  • Channel preference insights: Access and update user count preferences in group channels, tailoring notification and message delivery based on user needs.

Supported Tools & Triggers

Tools
Add Members To Group ChannelTool to add members to a group channel.
Ban User from Group ChannelTool to ban a user from a group channel.
Create Group ChannelTool to create a new group channel.
Create Sendbird UserTool to create a new user.
Delete Group ChannelTool to delete a specific group channel.
Delete MessageTool to delete a specific message in a sendbird group channel.
Delete Sendbird UserTool to delete a sendbird user.
Get Count Preference Of ChannelTool to retrieve a user's count preference for a specific group channel.
Sendbird Get Group Channel Count by Join StatusTool to retrieve number of group channels by join status for a user.
Sendbird Get Unread Item CountTool to retrieve a user's unread item counts.
Issue Session TokenTool to issue a session token for a user.
Leave Group ChannelsTool to leave group channels for a user.
List Banned MembersTool to list banned members in a group channel.
List Group ChannelsTool to list group channels.
List Group Channel MembersTool to list members of a group channel.
List Operators by Custom Channel TypeTool to list operators of a channel by custom channel type.
List Group Channel OperatorsTool to list operators of a group channel.
List Open Channel OperatorsTool to list operators of an open channel.
List UsersTool to retrieve a list of users.
Mark All User Messages As ReadTool to mark all of a user's messages as read in group channels.
Mute UserTool to mute a user in a group channel.
Register Operators by Custom Channel TypeTool to register users as operators to channels by custom channel type.
Register Group Channel OperatorsTool to register one or more users as operators in a sendbird group channel.
Register Operators to Open ChannelTool to register operators to an open channel.
Revoke All Session TokensTool to revoke all session tokens for a user.
Sendbird View MessageTool to view a specific message in a group channel.
Sendbird View UserTool to view user information.
Send MessageTool to send a message to a group channel.
Unban User from Group ChannelTool to unban a user from a group channel.
Unmute UserTool to unmute a user in a group channel.
Unregister Operators Custom Channel TypeTool to unregister operators from channels by custom channel type.
Update Count Preference Of ChannelTool to update a user's unread count preference for a specific group channel.
Update Group ChannelTool to update group channel information.
Sendbird Update MessageTool to update an existing group channel message in sendbird.
Update Sendbird UserTool to update a user's information.
Sendbird View Group ChannelTool to view information about a specific group channel.
View UserTool to retrieve information about a specific sendbird user.

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 this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • 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-langchain langchain-mcp-adapters langchain python-dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • composio-langchain provides Composio integration for LangChain
  • langchain-mcp-adapters enables MCP client connections
  • langchain is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models

Import dependencies

from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Sendbird functionality through MCP

Initialize Composio client

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))

    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Sendbird tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding

Create a Tool Router session

# Create Tool Router session for Sendbird
session = composio.create(
    user_id=os.getenv("COMPOSIO_USER_ID"),
    toolkits=['sendbird']
)

url = session.mcp.url
What's happening:
  • We're creating a Tool Router session that gives your agent access to Sendbird tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use Sendbird tools as needed

Configure the agent with the MCP URL

client = MultiServerMCPClient({
    "sendbird-agent": {
        "transport": "streamable_http",
        "url": session.mcp.url,
        "headers": {
            "x-api-key": os.getenv("COMPOSIO_API_KEY")
        }
    }
})

tools = await client.get_tools()

agent = create_agent("gpt-5", tools)
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Sendbird MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • get_tools() retrieves all available Sendbird tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model

Set up interactive chat interface

conversation_history = []

print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Sendbird related question or task to the agent.\n")

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ['exit', 'quit', 'bye']:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_history.append({"role": "user", "content": user_input})
    print("\nAgent is thinking...\n")

    response = await agent.ainvoke({"messages": conversation_history})
    conversation_history = response['messages']
    final_response = response['messages'][-1].content
    print(f"Agent: {final_response}\n")
What's happening:
  • We initialize an empty conversation_history list to maintain context across interactions
  • A while loop continuously accepts user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the ainvoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully

Run the application

if __name__ == "__main__":
    asyncio.run(main())
What's happening:
  • We call the main() function using asyncio.run() to start the application

Complete Code

Here's the complete code to get you started with Sendbird and LangChain:

from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    
    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
    
    session = composio.create(
        user_id=os.getenv("COMPOSIO_USER_ID"),
        toolkits=['sendbird']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "sendbird-agent": {
            "transport": "streamable_http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    })
    
    tools = await client.get_tools()
  
    agent = create_agent("gpt-5", tools)
    
    conversation_history = []
    
    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Ask any Sendbird related question or task to the agent.\n")
    
    while True:
        user_input = input("You: ").strip()
        
        if user_input.lower() in ['exit', 'quit', 'bye']:
            print("\nGoodbye!")
            break
        
        if not user_input:
            continue
        
        conversation_history.append({"role": "user", "content": user_input})
        print("\nAgent is thinking...\n")
        
        response = await agent.ainvoke({"messages": conversation_history})
        conversation_history = response['messages']
        final_response = response['messages'][-1].content
        print(f"Agent: {final_response}\n")

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

Conclusion

You've successfully built a LangChain agent that can interact with Sendbird through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

How to build Sendbird MCP Agent with another framework

FAQ

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

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

Can I use Tool Router MCP with LangChain?

Yes, you can. LangChain 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 Sendbird tools.

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

Yes, absolutely. You can configure which Sendbird 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 Sendbird data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
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.