# How to connect Sendbird to Hermes Agent (paste one key, 37 tools) > Connect Sendbird to Hermes with ClawLink: paste your Sendbird key once and 37 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/sendbird Most guides for giving Hermes Agent Sendbird access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Sendbird setup: pair once in the browser and your always-on Hermes agent can act on Sendbird for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to Sendbird. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Sendbird** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect sendbird # connect Sendbird (browser OAuth) npx -y @useclawlink/cli actions sendbird # list available actions npx -y @useclawlink/cli run sendbird --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect Sendbird in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Sendbird API key once. Verify the connection by asking Hermes: > Pull the relevant data from Sendbird, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The Hermes 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: ```bash npx -y @useclawlink/cli login ``` `login` 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Sendbird MCP for Hermes Looking for a Sendbird MCP server for Hermes Agent? ClawLink connects Sendbird to Hermes Agent and exposes 37 Sendbird tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Sendbird integration](https://claw-link.dev/openclaw/sendbird) works the same way. ## What the Hermes Agent Sendbird integration can do 37 Sendbird tools are ready for Hermes Agent 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 Hermes | 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 | ## Example prompts **Get Count Preference Of Channel** > Pull the relevant data from Sendbird, summarize it in plain English, and point out anything that needs attention. **Get Number Of Channels By Join Status** > Pull the relevant data from Sendbird, summarize it in plain English, and point out anything that needs attention. **Get Number Of Unread Items** > Pull the relevant data from Sendbird, summarize it in plain English, and point out anything that needs attention. **List Banned Members** > List the relevant items in Sendbird, group them by priority, and recommend what Hermes 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 Hermes Agent. 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 Hermes Agent 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Sendbird Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### 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. ### Is there a Hermes Agent Sendbird integration? Yes. ClawLink is the fastest way to connect Hermes to Sendbird: link your Sendbird account once in the browser and Hermes Agent can call the Sendbird API through 37 ready-made tools — no custom code or token handling. ### How do I connect Sendbird to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Sendbird in the dashboard and Hermes can use it 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 Hermes Agent? About two minutes. Sign in, click Connect next to Sendbird in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Sendbird working from chat. ### Hermes paired but still can't use Sendbird Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [Connect SendGrid](https://claw-link.dev/hermes/sendgrid) — Deliver transactional and marketing emails - [Dialpad](https://claw-link.dev/hermes/dialpad) — Business phone, messaging, and video conferencing - [Discord Bot](https://claw-link.dev/hermes/discord-bot) — Automate Discord server actions with bot-specific permissions