How to integrate Sendbird MCP with Claude Agent SDK

Framework Integration Gradient
Sendbird Logo
Claude Agent SDK Logo
divider

Introduction

This guide walks you through connecting Sendbird to the Claude Agent SDK 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 Claude Agent SDK 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 Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Sendbird
  • Configure an AI agent that can use Sendbird as a tool
  • Run a live chat session where you can ask the agent to perform Sendbird 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 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:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Sendbird 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 Sendbird 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 Sendbird
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["sendbird"]
    )

    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 Sendbird
  • 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 Sendbird 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 Sendbird
  • 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 Sendbird 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 Sendbird
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["sendbird"]
    )

    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 Sendbird 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 Sendbird 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 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 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 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.