LEVEL 2Discord

Connect Minecraft to Discord

Bridge chat and alerts without leaking a bot token.

◷ About 18 minCarefulReviewed Aug 18, 2026
On this pageWhat it can doSafe setup outlineProtect the bot tokenDecide what belongs in DiscordTest after setup

What 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#

  1. 1
    Create or choose a Discord server you control.
  2. 2
    Create dedicated channels for game chat and optional staff alerts.
  3. 3
    Create a Discord application and bot in the official Developer Portal.
  4. 4
    Invite it with the narrow permissions documented by the bridge project.
  5. 5
    Download DiscordSRV from its official project page or choose another maintained bridge that supports your exact platform.
  6. 6
    Stop Minecraft, put the jar in plugins, then restart.
  7. 7
    Put the bot token only in the private server configuration field/file.
  8. 8
    Map channel IDs and test one direction at a time.
  9. 9
    Confirm 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:

ChannelMinecraft → DiscordDiscord → MinecraftStaff only?
game-chatYesYesNo
server-statusYesNoNo
staff-alertsSelected eventsNoYes
admin-consoleAvoidAvoidYes

Test after setup#

  1. 1
    Send a normal message from Minecraft.
  2. 2
    Send a normal message from Discord.
  3. 3
    Test join/leave and server restart notices.
  4. 4
    Test with a normal Discord role, not only the owner.
  5. 5
    Inspect logs for permission or rate-limit warnings.
  6. 6
    Back up the configuration without exposing it publicly.
Was this page helpful?