Sendbird MCP integration for AI agents.
Connect AI agents to Sendbird through 28 structured actions, including get number of channels by join status, add members group channel, ban user from group…
- ACTION CONTRACTS
- 28
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Sendbird integration exposes
The Sendbird Agent App exposes 28 provider-backed actions for communication and developer tools work. Its current contract lets an authorized agent get sendbird group channel counts grouped by join status, invite members into an existing sendbird group channel, and ban a user from a sendbird group channel. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Sendbird account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Sendbird capabilities.
Showing 12 of 28 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_number_of_channels_by_join_statusREADGet Sendbird group channel counts grouped by join status.
INPUTS: user_id / super_mode / public_mode / distinct_mode / hidden_mode
add_members_group_channelWRITEInvite members into an existing Sendbird group channel.
INPUTS: channel_url / user_ids / hide_existing_messages / seconds
ban_user_from_group_channelHIGH IMPACTBan a user from a Sendbird group channel.
INPUTS: channel_url / user_id / seconds / description / agent_id
issue_session_tokenREVIEWIssue a Sendbird session token for a user.
INPUTS: user_id / expires_at
create_channelWRITECreate a Sendbird group channel with common JSON body fields.
INPUTS: name / channel_url / user_ids / operator_ids / cover_url
create_userWRITECreate a Sendbird user with common profile and metadata fields.
INPUTS: user_id / nickname / profile_url / metadata / issue_access_token
delete_channelHIGH IMPACTDelete a Sendbird group channel.
INPUTS: channel_url
delete_messageHIGH IMPACTDelete a Sendbird group channel message.
INPUTS: channel_url / message_id
delete_userHIGH IMPACTDelete a Sendbird user.
INPUTS: user_id / hard_delete
get_number_of_unread_itemsREADGet unread message, mention, and invitation counts for a Sendbird user.
INPUTS: user_id / item_keys / custom_types
leave_group_channelsREVIEWMake a Sendbird user leave one or more joined group channels.
INPUTS: user_id / should_leave_all / channel_urls / custom_type
list_banned_membersREADList banned users from a Sendbird group channel.
INPUTS: channel_url / limit / token
INPUT CONTRACTS
Know what the action needs before it runs.
get_number_of_channels_by_join_status
user_idREQUIRED- The Sendbird user ID.
super_modeOPTIONAL- Filter by whether the channel is a supergroup.
public_modeOPTIONAL- Filter by whether the channel is public.
distinct_modeOPTIONAL- Filter by whether the channel is distinct.
hidden_modeOPTIONAL- The hidden-mode filter supported by the official API.
add_members_group_channel
channel_urlREQUIRED- The unique URL of the target group channel.
user_idsREQUIRED- A list of non-empty strings.
hide_existing_messagesOPTIONAL- Whether to hide previous messages from the invited users.
secondsOPTIONAL- The hide-existing-messages duration in seconds when required by Sendbird.
ban_user_from_group_channel
channel_urlREQUIRED- The unique URL of the target group channel.
user_idREQUIRED- The Sendbird user ID.
secondsOPTIONAL- The ban duration in seconds. Omit for a permanent ban.
descriptionOPTIONAL- The moderation reason to record.
agent_idOPTIONAL- The moderator ID performing the action.
issue_session_token
user_idREQUIRED- The Sendbird user ID.
expires_atOPTIONAL- A Unix timestamp in milliseconds.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Number Of Channels By Join Status
Get Sendbird group channel counts grouped by join status. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_number_of_channels_by_join_statusControl Add Members Group Channel
Invite members into an existing Sendbird group channel. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_members_group_channelVerify with Add Members Group Channel
Invite members into an existing Sendbird group channel. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
add_members_group_channelSAFETY BOUNDARY
Operate Sendbird with explicit limits
- Authorize Sendbird with API key and grant only the provider access required by the selected actions.
- 12 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `ban_user_from_group_channel`, `delete_channel`, and `delete_message` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Sendbird rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Sendbird task completed successfully.
CONNECTION MODEL
API key
Sendbird API token used with the Api-Token header. Find it in Sendbird Dashboard under Settings > Application > General > API tokens: https://sendbird.com/docs/chat/platform-api/v3/prepare-to-use-api.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 8
- WRITE SIGNALS
- 7
- HIGH IMPACT
- 5
- REVIEW SIGNALS
- 8
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Sendbird.