Discord has become a serious workspace tool for technical teams and communities. If your team runs on Discord rather than Slack, connecting OpenClaw gives you the same AI assistant capability inside your server. The setup is similar in spirit to the Slack integration but different in the details.
How OpenClaw Integrations Work
OpenClaw is a self-hosted AI assistant that runs on your own server — typically an EC2 instance — and connects to Slack. It uses Claude under the hood to process requests. Out of the box, OpenClaw doesn't ship with pre-built connections to third-party tools. Instead, integrations are built using the skills system: markdown files in ~/.openclaw/skills/ that give Claude instructions for a particular domain, combined with HTTP tool calls to any API you expose to it.
In practice, adding a real integration means: getting API credentials from the third-party service, building or configuring a small proxy/endpoint that OpenClaw can call, and writing a skill file that tells Claude how to use it. For some tools this is an afternoon of work. For others — like Discord — it's considerably more involved.
Connecting OpenClaw with Discord: Step by Step
Step 1: Create a Discord Application and Bot
Go to the Discord Developer Portal, create a new application, and add a Bot user. Under the Bot settings, copy the Bot Token. You'll also need to enable the Message Content Intent — this privileged intent is required for OpenClaw to read message text. Without it, the bot can only see mentions and slash command payloads.
Step 2: Set the Required Permissions and Invite the Bot
In the OAuth2 URL Generator, select the bot scope and the permissions your bot needs: Read Messages/View Channels, Send Messages, Read Message History. Generate the invite URL and use it to add the bot to your server. Once it's in, configure your OpenClaw instance with the bot token and the Guild (server) ID it should respond in.
Step 3: Configure Gateway Intents and Test
Discord's Gateway API uses Intents to control which events your bot receives. OpenClaw needs at minimum GUILD_MESSAGES and MESSAGE_CONTENT (privileged). Set these in your application's bot settings and in your OpenClaw configuration. Test by mentioning the bot in a channel — it should respond via Claude within a few seconds.
Challenges and Caveats
Message Content Intent Is Now Privileged
As of 2022, Discord requires explicit approval for bots that read message content in servers with over 100 members. For small teams this is approved automatically, but for larger communities or public bots, you need to apply for verification and the privileged intent. This can take time and isn't guaranteed for bots with broad access.
Discord Rate Limits Are Per-Route
Discord's API applies rate limits per route (endpoint + HTTP method). Sending many messages in quick succession will hit the POST /channels/{id}/messages rate limit. For bots responding to high message volume, OpenClaw needs rate limit aware queuing.
Skip All of This — Use Cody Instead
Cody supports Discord as a first-class interface alongside Slack and Telegram. Connect your Discord server and get AI-powered answers without any bot setup or intent configuration.
Related Guides
- Connecting OpenClaw with Slack: A Practical Guide
- Connecting OpenClaw with Telegram: A Practical Guide
- Connecting OpenClaw with Notion: A Practical Guide
Need the model-flexible version? See: How to Connect Discord to OpenClaw: Setup, Models, and Workflow Guide.