Sendbird
Sendbird is a platform that provides chat, voice, and video APIs to help businesses build in-app communication features.
Verdict
Common use cases
- Moderate chat channels during community incidents
- Create support channels from ticket threads
- Archive inactive group conversations monthly
- Pull unread message counts for standup
- Ban abusive users across multiple channels
Integration
- Vendor
- Sendbird
- Category
- communication
- Auth
- API_KEY
- Tools
- 37
- Composio slug
sendbird
Tools
- Add Members To Group Channel
Tool to add members to a group channel. use when you need to invite one or more users into an existing group channel.
- Ban User from Group Channel
Tool to ban a user from a group channel. use when moderating group channels to restrict member access. execute after confirming channel url and user id.
- Create Group Channel
Tool to create a new group channel. use when you need to start a conversation with specific users. execute after specifying users and optional settings.
- Create Sendbird User
Tool to create a new user. use when you need to register a user account in sendbird.
- Delete Group Channeldestructive
Tool to delete a specific group channel. use when you have the channel url and want to permanently remove the channel. execute after confirming the channel exists.
- Delete Messagedestructive
Tool to delete a specific message in a sendbird group channel. use when you need to permanently remove a sent message after confirming deletion permissions.
- Delete Sendbird Userdestructive
Tool to delete a sendbird user. use when you need to remove a user from your sendbird application, optionally permanently.
- Get Count Preference Of Channel
Tool to retrieve a user's count preference for a specific group channel. use after confirming the user and channel exist to determine whether to display all, unread-only, or mention-only counts.
- Issue Session Token
Tool to issue a session token for a user. use when you need to generate or refresh a user's session token.
- Leave Group Channels
Tool to leave group channels for a user. use when you need to make a user exit one or more joined group channels.
- List Banned Members
Tool to list banned members in a group channel. use when you need to see which users are banned from a specific group channel.
- List Group Channel Members
Tool to list members of a group channel. use when you need to paginate through members of a specified group channel.
- List Group Channel Operators
Tool to list operators of a group channel. use after specifying the channel url when needing to paginate through operators.
- List Group Channels
Tool to list group channels. use when you need to fetch paginated group channels with optional filters.
- List Open Channel Operators
Tool to list operators of an open channel. use when you have the open channel url and need to fetch its operators. supports pagination via token and limit.
- List Operators by Custom Channel Type
Tool to list operators of a channel by custom channel type. use when you need to fetch operators for a specific custom channel type with pagination.
- List Users
Tool to retrieve a list of users. use after setting up sendbird api credentials to paginate or filter all users in your application.
- Mark All User Messages As Read
Tool to mark all of a user's messages as read in group channels. use when resetting unread message counts after a user has viewed all messages.
- Mute User
Tool to mute a user in a group channel. use when you need to prevent a user from sending messages for a specified duration.
- Register Group Channel Operators
Tool to register one or more users as operators in a sendbird group channel. use when elevating permissions of existing channel members.
- Register Operators by Custom Channel Type
Tool to register users as operators to channels by custom channel type. use when assigning operator roles for all channels of a specified custom type.
- Register Operators to Open Channel
Tool to register operators to an open channel. use after creating or updating an open channel when you need to assign operator roles.
- Revoke All Session Tokensdestructive
Tool to revoke all session tokens for a user. use when you need to invalidate all active sessions for security.
- Sendbird Get Group Channel Count by Join Status
Tool to retrieve number of group channels by join status for a user. use when you need counts of invited, joined, and total channels for a specific user.
- Sendbird Get Unread Item Count
Tool to retrieve a user's unread item counts. use after you need the total unread messages, mentions, and channel counts for a specific user.
- Sendbird Update Message
Tool to update an existing group channel message in sendbird. use after you need to modify content or metadata of a sent message.
- Sendbird View Group Channel
Tool to view information about a specific group channel. use when you need channel details after confirming the channel url.
- Sendbird View Message
Tool to view a specific message in a group channel. use after confirming channel url and message id.
- Sendbird View User
Tool to view user information. use when retrieving details of a specific sendbird user by id.
- Send Message
Tool to send a message to a group channel. use when you need to post a text, file, or admin message to an existing group channel.
- Unban User from Group Channel
Tool to unban a user from a group channel. use when reinstating a previously banned user. execute after confirming the user is currently banned.
- Unmute User
Tool to unmute a user in a group channel. use when you want to restore a muted user's ability to send messages after confirming they are muted.
- Unregister Operators Custom Channel Type
Tool to unregister operators from channels by custom channel type. use when you need to remove operator roles from users across channels of a specific custom type.
- Update Count Preference Of Channel
Tool to update a user's unread count preference for a specific group channel. use when you want to include or suppress a channel in the user's unread counts.
- Update Group Channel
Tool to update group channel information. use when you need to modify channel attributes such as name, cover image, privacy settings, or operator list after channel creation.
- Update Sendbird User
Tool to update a user's information. use when modifying nickname, profile image url, activation status, or metadata.
- View User
Tool to retrieve information about a specific sendbird user. use when you need to fetch detailed user data by their user id.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations > Add MCP Server. 2. Select Sendbird from the catalog and choose API Key authentication. 3. Log into your Sendbird Dashboard, go to Settings > Application > API Tokens, and generate a new API token with permissions for channels, users, and messages. 4. Paste the token into Switchy's configuration modal and click Connect. 5. Switchy will verify the token and list available tools. 6. Open any Space, type '@Sendbird list my group channels' and send — if you see channel data returned, the connection works. 7. To invoke tools, @mention Sendbird followed by your instruction (e.g. '@Sendbird create a group channel with users alice and bob'). 8. The MCP will prompt for required parameters if you omit them.
What teammates see: by default, memories from Sendbird are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Create Support Channel
@Sendbird create a group channel named 'Support-Case-4521' with users emma@example.com and support-agent-3. Set it to private and enable message history.Open in a Space →
Ban Repeat Offender
@Sendbird ban user ID 'user_12345' from the group channel 'general-chat' with reason 'repeated spam violations'. Set ban duration to 7 days.Open in a Space →
Delete Leaked Message
@Sendbird delete message ID 'msg_98765' from group channel 'product-team-internal'. Confirm the message contains confidential roadmap details before executing.Open in a Space →
Audit Unread Counts
@Sendbird get the count preference for user 'sarah@example.com' in channel 'customer-feedback'. Show whether they're tracking all messages, unread only, or mentions only.Open in a Space →
Bulk Archive Channels
@Sendbird delete the following group channels: 'project-alpha-archive', 'temp-collab-june', 'old-support-overflow'. Confirm each channel has no activity in the last 90 days before removal.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@sendbird list all group channels where user_id 'alice_dev' is a member and show their unread message counts
Based on the Sendbird API, user 'alice_dev' is a member of 3 group channels: 'team-backend' (12 unread messages), 'design-sync' (0 unread), and 'project-launch' (47 unread messages). The 'project-launch' channel was last active 8 minutes ago. This illustrative example shows how the MCP retrieves channel membership and message count data for a specific user across your Sendbird application.
This read-heavy example demonstrates the MCP's ability to query user participation and message state across channels. Requires API key with read permissions for channels and users. Actual channel names and counts depend on your Sendbird application's live data; results shown here are representative.
@sendbird create a new group channel called 'incident-response' with members user_alice, user_bob, and user_charlie, then send an initial message 'Investigating API timeout reports'
Group channel 'incident-response' created successfully with channel_url 'sendbird_group_channel_12345_abcdef'. Added 3 members: user_alice, user_bob, user_charlie. Initial message posted at 2024-01-15 14:32 UTC with message_id 'msg_987654'. All members will receive push notifications if configured. This illustrative example shows the MCP executing channel creation and message posting in sequence.
This write example shows the MCP's ability to provision channels and post messages atomically. Side-effect: creates a persistent channel and sends notifications to all members. User IDs must exist in your Sendbird application before adding them to channels. API key needs channel creation and messaging permissions.
@sendbird review the last 50 messages in channel 'support-escalations', identify any messages mentioning 'refund' or 'billing', and summarize the customer issues by urgency
Retrieved 50 messages from 'support-escalations' spanning the last 6 hours. Found 8 messages containing 'refund' or 'billing' keywords. High urgency (3 cases): customers reporting duplicate charges requiring immediate investigation. Medium urgency (4 cases): refund requests within standard processing timeframe. Low urgency (1 case): general billing question about invoice format. This illustrative synthesis pairs the MCP's message retrieval with AI analysis to surface actionable patterns.
This synthesis example demonstrates combining Sendbird's message history API with the AI's reasoning to extract insights from conversation data. Message retrieval is paginated; the MCP fetches data while the AI performs categorization and summarization. Requires read permissions for channel messages. Rate limits apply to message history queries.
Use-case deep-dives
When Sendbird MCP handles live support handoffs better than Slack
A 6-person support team fields 200+ customer inquiries daily through a web widget. They need to route urgent cases to specialists without losing message history or forcing customers to repeat context. Sendbird MCP wins here because it treats each conversation as a persistent group channel—agents join mid-thread, see full history, and the customer never switches windows. The ban and delete tools let you moderate abusive threads without escalating to engineering. The count preference tool surfaces unread-only counts so agents aren't overwhelmed by read receipts during shift handoffs. If your team already lives in Slack and support volume is under 50 tickets a day, the context-switching tax probably isn't worth a separate chat backend. Above that threshold, Sendbird's channel model keeps support threads cleaner than threading in a general workspace.
Automating cohort channels for new user onboarding at scale
A product team at a B2B SaaS company runs monthly onboarding cohorts—each cohort gets a private group chat for their first 30 days. Manual setup in Intercom or Slack means someone spends 20 minutes per cohort creating channels, inviting users, and setting permissions. Sendbird MCP automates this: trigger Create Group Channel when a cohort starts, Add Members as users complete signup, and Delete Group Channel when the 30-day window closes. The 37 tools cover edge cases like removing a user mid-cohort or deleting spam messages without admin intervention. This works best when you're running 4+ cohorts a month and onboarding is already instrumented in your product. Below that frequency, the API key setup and webhook wiring cost more than the time saved. If you hit this threshold, Sendbird MCP turns onboarding chat into a repeatable playbook instead of monthly toil.
Why Sendbird MCP doesn't replace Figma comments for async design review
A 3-person design team ships 15 feature mocks a week and wants stakeholders to leave feedback without opening Slack or email. Sendbird MCP can technically create a group channel per design file and thread comments there, but it's the wrong tool. Design feedback needs spatial context—comments anchored to specific UI elements, not a linear chat log. Sendbird's channel model treats every message as a timestamped event in a shared stream, which works for support handoffs or onboarding cohorts but breaks down when feedback needs to reference "the button in the top-right corner of screen 3." The Delete Message and moderation tools are overkill for a trusted internal team. If your feedback workflow is already text-heavy and doesn't need visual anchoring—like copy reviews or spec clarifications—Sendbird MCP could work. Otherwise, keep design feedback in the tool where the artifact lives.
Frequently asked
What does the Sendbird MCP let me do in Switchy?
It lets your AI agents create group channels, send messages, manage users, and moderate conversations inside your Sendbird application. You can automate onboarding flows, build support bots that ban spammers, or trigger channel creation when a deal closes in your CRM. The MCP wraps Sendbird's chat API so agents can act on real chat data without you writing integration code.
Do I need admin access to connect Sendbird?
You need a Sendbird API key with permissions matching the tools you want agents to use. Creating users and channels requires write access; reading message counts needs read access. Sendbird issues keys at the application level, so whoever provisions the key controls which operations the MCP can perform. Check your Sendbird dashboard under Settings > Application > API tokens.
Can the MCP read message history or only send new messages?
The representative tools focus on channel management and moderation—creating channels, adding members, banning users, deleting messages. Reading full message history isn't in the listed toolset. If you need agents to analyse past conversations, confirm with Sendbird's API docs whether your key grants message-list access, then check if Switchy's MCP exposes that endpoint.
How is this different from calling Sendbird's API directly?
The MCP gives your AI agents a structured interface to Sendbird without you maintaining auth tokens, retry logic, or rate-limit handling. Agents pick tools by name instead of constructing HTTP requests. You trade flexibility for speed—direct API calls let you hit any endpoint; the MCP covers the 37 most common operations and handles the plumbing.
Who on my team should connect the Sendbird MCP?
Whoever manages your Sendbird application and can generate API keys. That's usually a backend engineer or the person who set up your chat infrastructure. They'll paste the key into Switchy once; after that, any team member with workspace access can build agents that use Sendbird tools, no extra credentials required.