How to Bridge Server Chat to Discord (DiscordSRV Setup)
DiscordSRV setup for a Minecraft chat bridge: create the bot, copy channel IDs into config.yml, run /discordsrv reload, and turn on the console relay.
DiscordSRV bridges your Minecraft chat to a Discord channel in both directions, and it comes down to four things in order: create a bot and copy its token, invite that bot and copy your channel IDs, drop the jar in plugins and paste those values into config.yml, then run /discordsrv reload. The piece most owners leave switched off is the console-relay channel, which streams your live server log into a private Discord channel and lets you run commands from your phone - so you can read a crash without ever opening an SSH session to the box.
One thing to settle before you start: DiscordSRV is a Bukkit plugin. It runs on Paper, Spigot, or Purpur, and the target for a plugin server right now is 26.1 stable. It needs Java 21 or newer. It does not run on vanilla, and it does not run on Fabric or Forge, because neither of those exposes the Bukkit API the plugin hooks into. If you're on the wrong software, no amount of config editing will make it load.
Create the Discord bot and copy its token
Head to discord.com/developers/applications, click New Application, give it a name, then open the Bot tab on the left. Hit Reset Token, then Copy. Treat that string like a password - it's the only credential the plugin uses to log in as the bot, and if it ever leaks into a screenshot or a pasted log, reset it and use the new one. Don't try to reuse a leaked token by "being careful"; Discord will happily let anyone with it control your bot.
The step almost everyone skips is right below, under Privileged Gateway Intents. Toggle on Message Content Intent. Without it, Discord can tell your bot that a message happened but won't include the text, so Discord-to-game chat comes through completely silent. While you're there, toggle on Server Members Intent too - you'll need it later for role syncing. Save.
If you paste a bad token, the symptom is loud. On startup you'll see Failed to authenticate to the Discord API in the console, which nearly always means a wrong token or stray quotes wrapped around it in the config. Copy it clean, no extra characters.
Invite the bot and grab your channel IDs
The bot exists now, but it isn't in your server yet. Go to OAuth2 > URL Generator. Under scopes, tick bot. A permissions box appears below - tick View Channels, Send Messages, Read Message History, and Manage Roles (that last one is for the account-link role syncing later). Copy the generated URL at the bottom, open it in a new tab, pick your Discord server from the dropdown, and click Authorize. The bot should now show up in your member list, offline for the moment.
Next you need the numeric IDs for your channels. In Discord, open User Settings > Advanced > Developer Mode and switch it on. Now right-click your public chat channel and choose Copy Channel ID - that long number is what the config wants, not the channel name. While you're here, create a second channel that only admins can see - call it something like #server-console - and copy its ID as well. You'll wire that one up two sections down, and it's worth setting up now so you're not hunting for it later.
Install DiscordSRV and wire up config.yml
Download the DiscordSRV jar and drop it into your server's plugins/ folder, then restart once so it generates plugins/DiscordSRV/config.yml. If the jar-drop and plugins-folder mechanics are new to you, how to add plugins to a Paper server walks through the whole loop of downloading, placing, and restarting.
Open that generated config.yml and you only need to touch three things to get chat flowing. Set BotToken: to the token you copied. Find the Channels: map and set global: "your-chat-channel-id" using the public channel ID from the last section - keep the quotes. Leave everything else at its default for now; the defaults are sane and you can refine later.
You don't need a full restart to apply this. Type /discordsrv reload in the server console or in-game and the plugin re-reads its config. Within a second or two the bot should flip to online in your member list.
If you want to change how messages look, two keys control the formatting. DiscordChatChannelMinecraftToDiscordFormat controls what shows up on the Discord side when someone types in game, and DiscordChatChannelDiscordToMinecraftFormat controls the [Discord] Name: message line that appears in Minecraft. Skip these until the basics work - format tweaks are easy to fiddle with for an hour and forget you were testing whether it works at all.
Turn on the console-relay channel (the underrated payoff)
This is the part that changes how you run the server. Open config.yml again, find DiscordConsoleChannelId:, and set it to the private admin channel ID you copied earlier. Reload with /discordsrv reload.
Two things start happening immediately. Your console output streams into that Discord channel in near real time, and anything you type in the channel runs as a console command. That means when a player pings you at midnight saying the server froze, you open Discord on your phone, scroll the log, and read the stack trace right there - the same trace you'd otherwise SSH in to find. Pair that with why your Minecraft server keeps crashing and you can usually spot the offending plugin or the out-of-memory line before you're even at a keyboard.
Now the blunt security warning: anyone who can see that channel effectively has console and op access to your server. They can type op theirname or stop and it just runs. So keep it a private, admin-only channel, lock the view permission down, and never, ever point DiscordConsoleChannelId at your global chat channel. That mistake hands the keys to everyone in your Discord.
Two keys make it safer. DiscordConsoleChannelBlacklistedCommands lets you list commands the relay refuses to run - put stop, op, and whitelist on it so a compromised admin account can't nuke the box. DiscordConsoleChannelLevels filters which log levels get relayed, so you can drop INFO spam and only see WARN and ERROR if the channel gets noisy.
Link player accounts and sync roles
Account linking ties a player's Minecraft identity to their Discord identity. A player runs /discord link in game, gets a 4-digit code back, then DMs that code to your bot. The bot binds their Minecraft UUID to their Discord account. That's the whole flow from the player's side.
Once a player is linked, DiscordSRV can two-way sync a Discord role to an in-game permission group. This works cleanly through LuckPerms - set up your groups first with permission ranks in LuckPerms, then map them. The relevant config key is SynchronizedRoles, where you pair a Discord role name with a LuckPerms group. There's also MinecraftDiscordAccountLinkedRoleNameToAddUserTo, which auto-grants a "Linked" role to anyone who completes the link - handy for showing at a glance who's connected. If you want to require it, the Require linked account to play option gates joins so only linked accounts can connect, which some private communities use as a soft membership check.
Test both directions and fix the usual misses
Type a message in game and watch your Discord channel - it should show up there. Then type a message in that Discord channel and watch the server - it should appear in game with the [Discord] prefix. If both work, you're done.
When one direction is dead, the cause is almost always one of three things. Bot shows offline in the member list means a wrong token or the bot was never actually invited - recheck the OAuth2 URL step. Game-to-Discord works but Discord-to-game is silent means Message Content Intent is still switched off in the developer portal; flip it on and /discordsrv reload. Nothing shows in either direction usually means a wrong channel ID, or the bot lacks Send Messages or View Channels permission in that specific channel - check the channel's permission overrides, not just the server-wide role.
With that working, DiscordSRV earns its spot in a healthy ops stack. It sits nicely alongside the other must-have Paper plugins for a new server, and it pairs especially well with scheduled automatic restarts - you'll see the restart announce and land in your console channel, which is a quiet confirmation the cron fired. A live bridge also keeps a community talking when the server's empty, which does more for getting and keeping players on a new server than most owners expect.
FAQ
Does DiscordSRV work on Fabric or Forge?
No. It's built on the Bukkit API, so you need Paper, Spigot, or Purpur. If you're running a Velocity or BungeeCord network, install DiscordSRV on each backend Bukkit server rather than on the proxy - the proxy itself has no Bukkit API for the plugin to hook into, so it can't load there.
Can I bridge more than one channel?
Yes. Add extra entries under the Channels: map, each pairing an in-game chat-channel name with a Discord channel ID. The catch is that the default config only ships global, so before you can route a second channel you need an in-game chat-channels plugin to actually define those named channels - DiscordSRV maps to names your chat plugin creates, it doesn't invent them.
Why does game-to-Discord work but Discord messages never reach the game?
The Message Content Intent is still disabled in the developer portal. DiscordSRV actually prints a startup warning about the missing message content intent, so check your log if you're unsure - it'll say so plainly. Re-enable the intent, run /discordsrv reload, and it takes effect right away with no full restart needed.
How do I cut off a compromised admin from the console channel fast?
Pull their view permission on that channel - strip the role that grants it, or add a per-user deny override - and they lose relay access the instant Discord applies the change, no /discordsrv reload or restart required. If what leaked is the bot token itself rather than a person's account, the channel locks won't help at all: reset the token in the developer portal and update BotToken, because anyone holding the old one can drive the bot directly. Cleaning up afterward is easier than you'd think, since the relay tags each command it runs with the Discord user who sent it, so the log shows exactly what that account executed before you locked it out.


