# How to connect Revolt to OpenClaw (paste one key, 26 tools) > Connect Revolt to OpenClaw with ClawLink: paste your Revolt key once and 26 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/revolt The usual route to Revolt 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 Revolt setup: install one ClawHub skill, connect Revolt in the browser, and OpenClaw can call real Revolt 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 Revolt. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Revolt** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw 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 revolt # connect Revolt (browser OAuth) npx -y @useclawlink/cli actions revolt # list available actions npx -y @useclawlink/cli run revolt --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 Revolt in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Revolt API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Revolt, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Revolt is connected in the dashboard, that agent calls the same 26 Revolt 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). ## Revolt MCP for OpenClaw Looking for a Revolt MCP server for OpenClaw? ClawLink connects Revolt to OpenClaw and exposes 26 Revolt 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 Hermes instead? The [Hermes Revolt integration](https://claw-link.dev/hermes/revolt) works the same way. ## What the OpenClaw Revolt integration can do 26 Revolt tools are ready for OpenClaw once the account is connected. The 24 below are the ones people reach for most; your agent can call all 26. ### 24 of 26 Revolt tools for OpenClaw | Tool | What it does | |---|---| | **Fetch owned bots** `revolt_fetch_owned_bots` | Fetch all bots that you have control over | | **Fetch sync settings** `revolt_fetch_sync_settings` | Fetch settings from server filtered by keys | | **Fetch user** `revolt_fetch_user` | Fetch detailed information about a user | | **Fetch user flags** `revolt_fetch_user_flags` | Fetch flags associated with a specific user | | **Get API info** `revolt_get_api_info` | Fetch the server configuration for this Revolt instance | | **Get channel** `revolt_get_channel` | Fetch a channel by its ID | | **Get current user** `revolt_get_current_user` | Retrieve your own user information | | **Get invite** `revolt_get_invite` | Fetch detailed information about an invite by its code | | **Get sync unreads** `revolt_get_sync_unreads` | Fetch information about unread state on channels | | **Get user profile** `revolt_get_user_profile` | Retrieve a user's profile data including bio and background | | **Get users default avatar** `revolt_get_users_default_avatar` | Fetch a user's default avatar image based on their ID | | **Get users dms** `revolt_get_users_dms` | Fetch all direct message conversations for the authenticated user | | **Acknowledge policy changes** `revolt_acknowledge_policy_changes` | Acknowledge platform policy changes | | **Add channels messages reactions** `revolt_add_channels_messages_reactions` | Add a reaction to a message in a channel | | **Block user** `revolt_block_user` | Block another user by their ID | | **Create sync settings set** `revolt_create_sync_settings_set` | Upload and save settings data to Revolt's sync storage | | **Get users dm** `revolt_get_users_dm` | Open a DM with another user | | **Pin message** `revolt_pin_message` | Pin a message in a channel by its ID | | **Send channels messages** `revolt_send_channels_messages` | Send a message to a Revolt channel | | **Update channels messages** `revolt_update_channels_messages` | Edit a message that you've previously sent in a channel | | **Update user** `revolt_update_user` | Update user information | | **Remove message reaction** `revolt_remove_message_reaction` | Remove a reaction from a message | | **Unblock user** `revolt_unblock_user` | Unblock another user by their ID | | **Unpin message** `revolt_unpin_message` | Unpin a message in a channel | ## Example prompts **Fetch Owned Bots** > Pull the relevant data from Revolt, summarize it in plain English, and point out anything that needs attention. **Fetch Sync Settings** > Pull the relevant data from Revolt, summarize it in plain English, and point out anything that needs attention. **Fetch User** > Pull the relevant data from Revolt, summarize it in plain English, and point out anything that needs attention. **Fetch User Flags** > Pull the relevant data from Revolt, summarize it in plain English, and point out anything that needs attention. ## 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 Revolt working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Revolt API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Revolt 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 Revolt. | 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 Revolt actions to the runtime in a format your agent can reliably use. | 26 tools for Revolt are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Revolt 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 Revolt in the browser, and the 26 tools above work from chat. There is no SDK and no config file, and the Revolt 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. ### OpenClaw installed the Revolt skill but can't call the tools The ClawHub skill teaches OpenClaw about Revolt, but the calls run through the ClawLink plugin and your connected account. Make sure Revolt 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 Revolt 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 Revolt tools Revolt 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 Revolt 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. ### Revolt 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 Revolt has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Revolt integration? Yes. ClawLink is the fastest way to connect OpenClaw to Revolt: link your Revolt account once in the browser and OpenClaw can call the Revolt API through 26 ready-made tools — no custom code or token handling. ### How do I add Revolt to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Revolt skill from ClawHub, then you click Connect in the dashboard to authorize Revolt. OpenClaw calls the tools from the next message — no config files, and the Revolt key you paste is stored server-side instead of in your environment. ### How long does it take to connect Revolt to OpenClaw? About two minutes. Sign in, click Connect next to Revolt in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Revolt 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 Revolt working from chat. ### OpenClaw installed the Revolt skill but can't call the tools The ClawHub skill teaches OpenClaw about Revolt, but the calls run through the ClawLink plugin and your connected account. Make sure Revolt 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. ## Related - [OpenClaw SendGrid integration](https://claw-link.dev/openclaw/sendgrid) — Deliver transactional and marketing emails - [Dialpad tools](https://claw-link.dev/openclaw/dialpad) — Business phone, messaging, and video conferencing - [OpenClaw Discord Bot integration](https://claw-link.dev/openclaw/discord-bot) — Automate Discord server actions with bot-specific permissions