Refer the common guide for configuring mautrix bridges: Setting up a Generic Mautrix Bridge
Note: bridging to Discord can also happen via the mx-puppet-discord and matrix-appservice-discord bridges supported by the playbook.
mautrix-discord bridge (the one being discussed here), because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook.The playbook can install and configure mautrix-discord for you.
See the project’s documentation to learn what it does and why it might be useful to you.
There are 2 ways to login to discord using this bridge, either by scanning a QR code using the Discord mobile app or by using a Discord token.
If this is a dealbreaker for you, consider using one of the other Discord bridges supported by the playbook: mx-puppet-discord or matrix-appservice-discord. These come with their own complexity and limitations, however, so we recommend that you proceed with this one if possible.
If you want to set up Double Puppeting (hint: you most likely do) for this bridge automatically, you need to have enabled Appservice Double Puppet or Shared Secret Auth service for this playbook.
See this section on the common guide for configuring mautrix bridges for details about setting up Double Puppeting.
Note: double puppeting with the Shared Secret Auth works at the time of writing, but is deprecated and will stop working in the future.
To enable the bridge, add the following configuration to your inventory/host_vars/matrix.example.com/vars.yml file:
matrix_mautrix_discord_enabled: true
There are some additional things you may wish to configure about the bridge.
See this section on the common guide for configuring mautrix bridges for details about variables that you can customize and the bridge’s default configuration, including bridge permissions, encryption support, bot’s username, etc.
After configuring the playbook, run it with playbook tags as below:
ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-users-created,start
Notes:
The ensure-matrix-users-created playbook tag makes the playbook automatically create the bot’s user account.
The shortcut commands with the just program are also available: just install-all or just setup-all
just install-all is useful for maintaining your setup quickly (2x-5x faster than just setup-all) when its components remain unchanged. If you adjust your vars.yml to remove other components, you’d need to run just setup-all, or these components will still remain installed.
You can learn more here about authentication from the bridge’s official documentation on Authentication.
For using this bridge, you would need to authenticate by scanning a QR code with the Discord app on your phone.
You can delete the Discord app after the authentication process.
To acquire the token, open Discord in a private browser window. Then open the developer settings (keyboard shortcut might be “ctrl+shift+i” or by pressing “F12”). Navigate to the “Network” tab then reload the page. In the URL filter or search bar type “/api” and find the response with the file name of “library”. Under the request headers you should find a variable called “Authorization”, this is the token to your Discord account. After copying the token, you can close the browser window.
@discordbot:example.com (where example.com is your base domain, not the matrix. domain).login-token command, otherwise, send login-qr command.help to the bot to see the available commands.guilds status to see the list of guildsguilds bridge GUILD_ID --entireThe bridge supports using Discord’s webhook feature to relay messages from Matrix users who haven’t logged into the bridge. See the official documentation for setting up webhook relaying.