How to integrate Sendbird MCP with Mastra AI

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Sendbird logo
Mastra AI logo
divider

Introduction

This guide walks you through connecting Sendbird to Mastra AI 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 through natural language commands.

This guide will help you understand how to give your Mastra AI 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.

Also integrate Sendbird with

TL;DR

Here's what you'll learn:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes Sendbird tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Sendbird tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your Sendbird agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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 UserCreates a new user in Sendbird.
Delete Group ChannelPermanently deletes a Sendbird group channel.
Delete MessagePermanently deletes a specific message from 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.
Get User Group Channel Count by Join StatusRetrieves the number of group channels for a user, categorized by join status (joined, invited, etc.
Sendbird Get Unread Item CountTool to retrieve a user's unread item counts including unread messages, mentions, and pending invitations across group channels.
Issue Session TokenIssues a session token for authenticating a Sendbird user.
Leave Group ChannelsTool to leave group channels for a user.
List Banned MembersTool to list banned members in a group channel.
Sendbird List Group Channel MessagesTool to list (paginate) messages in a group channel when you only know the channel_url.
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 Sendbird UsersRetrieves a paginated list of users from your Sendbird application.
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 TypeRegisters one or more users as operators for all channels with a specified 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.
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.
Sendbird View MessageTool to view a specific message in a 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 Composio SDK?

Composio's Composio SDK 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 Composio SDK

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

How the Composio SDK works

The Composio SDK 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:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Sendbird through MCP.

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_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 your requests to Composio
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session

Create a Tool Router session for Sendbird

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["sendbird"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Sendbird MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "sendbird" for Sendbird access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the Sendbird toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "sendbird-mastra-agent",
    instructions: "You are an AI agent with Sendbird tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

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

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        sendbird: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Sendbird toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

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

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["sendbird"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      sendbird: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "sendbird-mastra-agent",
    instructions: "You are an AI agent with Sendbird tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { sendbird: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Sendbird through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows

How to build Sendbird MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Sendbird MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Sendbird MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Sendbird MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Sendbird MCP with Claude Cowork

Codex logo

Codex

Use Sendbird MCP with Codex

OpenClaw logo

OpenClaw

Use Sendbird MCP with OpenClaw

Hermes logo

Hermes

Use Sendbird MCP with Hermes

CLI logo

CLI

Use Sendbird MCP with CLI

Google ADK logo

Google ADK

Use Sendbird MCP with Google ADK

LangChain logo

LangChain

Use Sendbird MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Sendbird MCP with Vercel AI SDK

LlamaIndex logo

LlamaIndex

Use Sendbird MCP with LlamaIndex

CrewAI logo

CrewAI

Use Sendbird MCP with CrewAI

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 Mastra AI?

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

Get started for freeGet a demo↗