How to connect Sendbird to OpenClaw
Connect Sendbird to OpenClaw with ClawLink: paste your Sendbird key once and 37 tools work from chat. No MCP server to run, nothing stored on your machine.
SendbirdAPI KEYMCPSendbird is a platform that provides chat, voice, and video APIs to help businesses build in-app communication features.. Once connected, OpenClaw can read and act on Sendbird from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Sendbird access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Sendbird setup: install one ClawHub skill, connect Sendbird in the browser, and OpenClaw can call real Sendbird actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Sendbird.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Sendbird
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Sendbird?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Sendbird in the ClawLink dashboard — paste your Sendbird API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Sendbird, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Sendbird is connected in the dashboard, that agent calls the same 37 Sendbird tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Sendbird MCP for OpenClaw
Looking for a Sendbird MCP server for OpenClaw? ClawLink connects Sendbird to OpenClaw and exposes 37 Sendbird tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Sendbird integration works the same way.
What the OpenClaw Sendbird integration can do
37 Sendbird tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 37.
30 of 37 Sendbird tools for OpenClaw
| Tool | What it does |
|---|---|
Get count preference of channel sendbird_get_count_preference_of_channel | Retrieve a user's count preference for a specific group channel |
Get number of channels by join status sendbird_get_number_of_channels_by_join_status | Retrieves the number of group channels for a user, categorized by join status (joined, invited |
Get number of unread items sendbird_get_number_of_unread_items | Retrieve a user's unread item counts including unread messages, mentions, and pending |
List banned members sendbird_list_banned_members | List banned members in a group channel |
List group channel messages sendbird_list_group_channel_messages | List (paginate) messages in a group channel when you only know the channel_url |
List group channels sendbird_list_group_channels | List group channels |
List members group channel sendbird_list_members_group_channel | List members of a group channel |
List operators custom channel type sendbird_list_operators_custom_channel_type | List operators of a channel by custom channel type |
List operators group channel sendbird_list_operators_group_channel | List operators of a group channel |
List operators open channel sendbird_list_operators_open_channel | List operators of an open channel |
List users sendbird_list_users | Retrieves a paginated list of users from your Sendbird application |
View group channel sendbird_view_group_channel | View information about a specific group channel |
View message sendbird_view_message | View a specific message in a group channel |
View user sendbird_view_user | Retrieve information about a specific Sendbird user |
Add members group channel sendbird_add_members_group_channel | Add members to a group channel |
Ban user from group channel sendbird_ban_user_from_group_channel | Ban a user from a group channel |
Create channel sendbird_create_channel | Create a new group channel |
Create user sendbird_create_user | Creates a new user in Sendbird |
Issue session token sendbird_issue_session_token | Issues a session token for authenticating a Sendbird user |
Leave group channels sendbird_leave_group_channels | Leave group channels for a user |
Mark all user messages as read sendbird_mark_all_user_messages_as_read | Mark all of a user's messages as read in group channels |
Mute user sendbird_mute_user | Mute a user in a group channel |
Register operators custom channel type sendbird_register_operators_custom_channel_type | Registers one or more users as operators for all channels with a specified custom channel type |
Register operators group channel sendbird_register_operators_group_channel | Register one or more users as operators in a Sendbird group channel |
Register operators open channel sendbird_register_operators_open_channel | Register operators to an open channel |
Send message sendbird_send_message | Send a message to a group channel |
Unregister operators custom channel type sendbird_unregister_operators_custom_channel_type | Unregister operators from channels by custom channel type |
Update count preference of channel sendbird_update_count_preference_of_channel | Update a user's unread count preference for a specific group channel |
Update group channel sendbird_update_group_channel | Update group channel information |
Update message sendbird_update_message | Update an existing group channel message in Sendbird |
Try it: find the Sendbird tool you need
Browse the 30 Sendbird tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Sendbird, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Sendbird, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Sendbird, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Sendbird, group them by priority, and recommend what OpenClaw should do next.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Sendbird working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Sendbird API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Sendbird account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Sendbird. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Sendbird actions to the runtime in a format your agent can reliably use. | 37 tools for Sendbird are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Sendbird to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Sendbird in the browser, and the 37 tools above work from chat. There is no SDK and no config file, and the Sendbird key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Sendbird skill but can't call the tools
The ClawHub skill teaches OpenClaw about Sendbird, but the calls run through the ClawLink plugin and your connected account. Make sure Sendbird is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Sendbird from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Sendbird tools
Sendbird tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Sendbird call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Sendbird returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Sendbird has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Sendbird integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Sendbird: link your Sendbird account once in the browser and OpenClaw can call the Sendbird API through 37 ready-made tools — no custom code or token handling.
How do I add Sendbird to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Sendbird skill from ClawHub, then you click Connect in the dashboard to authorize Sendbird. OpenClaw calls the tools from the next message — no config files, and the Sendbird key you paste is stored server-side instead of in your environment.
How long does it take to connect Sendbird to OpenClaw?
About two minutes. Sign in, click Connect next to Sendbird in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Sendbird up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Sendbird working from chat.
OpenClaw installed the Sendbird skill but can't call the tools
The ClawHub skill teaches OpenClaw about Sendbird, but the calls run through the ClawLink plugin and your connected account. Make sure Sendbird is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
