How to integrate Sendbird MCP with CrewAI

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Sendbird Logo
CrewAI Logo
divider

Introduction

This guide walks you through connecting Sendbird to CrewAI 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 CrewAI 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 a Composio API key and configure your Sendbird connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Sendbird
  • Build a conversational loop where your agent can execute Sendbird operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

  • Agent Roles: Define specialized agents with specific goals and backstories
  • Task Management: Create tasks with clear descriptions and expected outputs
  • Crew Orchestration: Combine agents and tasks into collaborative workflows
  • MCP Integration: Connect to external tools through Model Context Protocol

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, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Sendbird connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python

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

bash
pip install composio crewai crewai-tools[mcp] python-dotenv
What's happening:
  • composio connects your agent to Sendbird via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] includes MCP helpers
  • python-dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_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 with Composio
  • USER_ID scopes the session to your account
  • OPENAI_API_KEY lets CrewAI use your chosen OpenAI model

Import dependencies

python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • CrewAI classes define agents and tasks, and run the workflow
  • MCPServerHTTP connects the agent to an MCP endpoint
  • Composio will give you a short lived Sendbird MCP URL

Create a Composio Tool Router session for Sendbird

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["sendbird"])

url = session.mcp.url
What's happening:
  • You create a Sendbird only session through Composio
  • Composio returns an MCP HTTP URL that exposes Sendbird tools

Initialize the MCP Server

python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
What's Happening:
  • Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
  • MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
  • Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
  • Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
  • Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.

Create a CLI Chatloop and define the Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

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

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

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
What's Happening:
  • Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
  • Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
  • Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
  • Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
  • Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
  • Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

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

from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["sendbird"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

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

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

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Sendbird through Composio's Tool Router. The agent can perform Sendbird operations through natural language commands.

Next steps:

  • Add role-specific instructions to customize agent behavior
  • Plug in more toolkits for multi-app workflows
  • Chain tasks for complex multi-step operations

How to build Sendbird MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Sendbird MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Sendbird MCP with Claude Agent SDK

Google ADK

Google ADK

Use Sendbird MCP with Google ADK

LangChain

LangChain

Use Sendbird MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Sendbird MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Sendbird MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Sendbird MCP with LlamaIndex

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 CrewAI?

Yes, you can. CrewAI 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.

Book a call↗Get started for free