LEVEL 2Discord
Connect Minecraft to Discord
Bridge chat and alerts without leaking a bot token.
◷ About 18 min◇ CarefulReviewed Aug 18, 2026
On this page
What it can doSafe setup outlineProtect the bot tokenDecide what belongs in DiscordTest after setupWhat it can do#
A bridge such as DiscordSRV can copy selected Minecraft chat to Discord, send Discord messages into Minecraft and report join, leave or server events. It can be useful for a community; a small private server may not need it.
Safe setup outline#
- 1Create or choose a Discord server you control.
- 2Create dedicated channels for game chat and optional staff alerts.
- 3Create a Discord application and bot in the official Developer Portal.
- 4Invite it with the narrow permissions documented by the bridge project.
- 5Download DiscordSRV from its official project page ↗ or choose another maintained bridge that supports your exact platform.
- 6Stop Minecraft, put the jar in
plugins, then restart. - 7Put the bot token only in the private server configuration field/file.
- 8Map channel IDs and test one direction at a time.
- 9Confirm ordinary Discord users cannot run console/admin actions.
Protect the bot token#
A bot token is a password. Anyone who has it may be able to act as the bot.
- Never paste it into public chat, screenshots, logs, support posts or a public repository.
- Keep the plugin configuration out of shared starter zips and public backups.
- Do not send the token through Minecraft chat.
- If it leaks, reset it immediately in Discord’s developer controls, update the private config and restart the bridge.
Decide what belongs in Discord#
Useful events include server online/offline, join/leave, player count and selected staff alerts. Mirroring every console line creates noise and may leak IP addresses, paths, plugin data or secrets.
Write down which direction each channel flows:
| Channel | Minecraft → Discord | Discord → Minecraft | Staff only? |
|---|---|---|---|
| game-chat | Yes | Yes | No |
| server-status | Yes | No | No |
| staff-alerts | Selected events | No | Yes |
| admin-console | Avoid | Avoid | Yes |
Test after setup#
- 1Send a normal message from Minecraft.
- 2Send a normal message from Discord.
- 3Test join/leave and server restart notices.
- 4Test with a normal Discord role, not only the owner.
- 5Inspect logs for permission or rate-limit warnings.
- 6Back up the configuration without exposing it publicly.
Was this page helpful?