Set up the Discord plugin for Claude Code

This guide sets up the Discord plugin from Anthropic's official plugin repository for Claude Code through the documented marketplace route. Before relying on it in production, review the full [README](https://github.com/anthropics/claude-plugins-official/tree/main/external_plugins/discord) and the [access control documentation](https://github.com/anthropics/claude-plugins-official/blob/main/external_plugins/discord/ACCESS.md) in the repository.

Check the prerequisites

The plugin requires a current version of Claude Code (check with claude --version) and the Bun JavaScript runtime. If Bun is missing, install it with curl -fsSL https://bun.sh/install | bash.

Create a Discord bot

In the [Discord Developer Portal](https://discord.com/developers/applications), create a new application with a bot. In the Bot section, under "Privileged Gateway Intents", enable "Message Content Intent" — without it, incoming messages arrive with empty content. Generate a bot token via "Reset Token" and save it, since it's only shown once. Invite the bot to a server of your own through the OAuth2 URL generator (scope "bot", permissions to read and send messages plus reactions), since Discord only allows direct messages between users who share a server.

Install and configure the plugin

In Claude Code, run these commands in order:

/plugin install discord@claude-plugins-official
/discord:configure [TOKEN]
claude --channels plugin:discord@claude-plugins-official

Replace [TOKEN] with the bot token from the Developer Portal. The third command starts Claude Code with the Discord channel active.

Grant access

Send the bot a direct message; it replies with a six-digit pairing code. Enter it in Claude Code with /discord:access pair [CODE] to pair yourself. For team setups, use a maintained allowlist instead via /discord:access allow <ID>; guild channels stay disabled by default and can be enabled individually with /discord:access group add <ID>.

Keep security in mind

Choose the access policy deliberately to match your use case: pairing for personal use, a maintained allowlist for multiple participants, or /discord:access policy disabled to lock the channel entirely for a while. Also check the "Public Bot" toggle in the Discord Developer Portal so not just anyone can add the bot to another server. Because a connected bot can potentially trigger far-reaching actions in the running Claude Code session, the access.json configuration under ~/.claude/channels/discord/ deserves a periodic review, especially before enabling new guild channels.