Based on mautrix-discord. Bridges Discord servers (a.k.a. "guilds") as Matrix spaces, channels as rooms, with full puppeting so messages you send from Matrix appear natively in Discord.
⚠️ Heads up. Using a personal Discord token is against the Discord ToS. Discord has never enforced this against Matrix bridges, but the risk is yours to accept. For production use on corporate Discord servers, use the bot-token path instead.
@discordbot:<your-name>.meldry.com.https://discord.com/api/....Authorization: header value (no prefix — just the token).@discordbot:<your-name>.meldry.com:
login-token user <your-token>
Logged in as YourDiscordHandle#1234. Your servers start bridging.login-token bot <your-bot-token>Bot mode is safer (Discord ToS compliant) but loses per-user puppeting — all Matrix users appear as the bot on the Discord side.
| Command | What it does |
|---|---|
login-token user <token> | Log in with a personal Discord token |
login-token bot <token> | Log in with a bot token |
logout | Unlink |
guilds | List joined servers |
bridge <guild-id> | Manually bridge one server |
unbridge <guild-id> | Stop bridging one server |
help | Full command list |
"Token invalid" — Discord tokens expire when you log out of the browser, and when you change your password. Grab a new one.
Bot user can't see channels — In Discord, make sure the bot role has View Channel permission on each channel you want bridged.
Emoji and stickers not showing — Custom emoji require the bridge to have upload permission on your homeserver. This is enabled by default on Meldry; no action needed.
"Account flagged" — Discord sometimes flags accounts that log in from unusual IPs. If this happens, verify via the Discord email they send you. The bridge does not bypass verification.