How to Add a TTS Bot to a Discord Server: Step-by-Step Setup

Adding a TTS bot to a Discord server takes about five minutes and happens on a web page, not inside the Discord app. Open the bot’s invite link, approve Discord’s official authorization screen (pick your server, review the permission list, click Authorize), then connect the bot to a voice channel and restrict who can trigger it. This guide walks through each step with Interaction Bot, a text-to-speech and translation bot that reports 56,065 Discord servers from the counters on its homepage (retrieved September 11, 2026), as the working example. The same flow applies to any TTS bot with a public invite link.

Before you start: two things your account needs

Discord permits a bot to be added only by someone who can manage the target server. Your account needs both of these:

• Membership in the server you want the bot to join.
• Manage Server (Discord also labels it Manage Guild) or Administrator on that server. Discord’s developer documentation explains that when you open a bot’s authorization page, “they’ll be prompted to add the bot to a guild in which they have proper permissions.” Without one of these roles, the server is greyed out in the “Add to server” dropdown and the invite silently fails.

One more thing to know before you start: a bot is never added through a normal server invite. Discord’s OAuth2 flow is the only install path, and it lives at discord.com/oauth2/authorize. Every bot’s “Add to Discord” button is a link to that page with the bot’s own settings already filled in.

Step 1: open the bot’s invite link

On the bot’s official website or its Discord App Directory listing, find the invte button, usually labeled Add to Discord, Add to Server, or Invite. For Interaction Bot it sits on the homepage and points at invite.interaction-bot.com, which forwards to Discord’s authorization page:

discord.com/oauth2/authorize?client_id=893494390142697493&permissions=1072235544144&scope=bot%20applications.commands

Two parts of that address do the real work:

• permissions=1072235544144. Against the values in Discord’s official permission reference, this number decodes to 24 individual permissions, from View Channels and Send Messages up to the voice permissions (Connect, Speak, Use Voice Activity) that let a bot read messages aloud.
• scope=bot applications.commands. Per Discord’s OAuth2 documentation, the bot scope “puts the bot in the user’s selected guild by default”, and applications.commands allows the app to add slash commands to that guild, which is how the bot’s commands such as /tts and /help appear on your server.

If you would rather watch somebody click through the whole install before you touch anything, Tech Academy’s walkthrough, “How To Add a TTS (Text-To-Speech) Bot To Your Discord Server (Easy)”, shows the invite and setup flow for a Discord TTS bot:

Step 2: approve Discord’s authorization screen (the OAuth step)

This screen is where the bot actually gets added. It loads under the bot’s name and shows three things: the Discord account acting at the top, an “Add to server” dropdown, and the list of permissions the bot is requesting, already ticked.

1. Check the account at the top. The page acts on whichever account is signed into that browser. If it is different from the account that holds Manage Server on your server, sign out and back in.
2. Pick your server from the dropdown. A server that is missing or greyed out is one where your account lacks Manage Server or Administrator.
3. Leave the permission defaults alone. For voice TTS these are the ones that matter:

4. Click Authorize. Discord may ask you to confirm a second time. The bot appears in your member list within a few seconds.

Two cautions. First, the most common cause of “the bot joined but never speaks” is an unticked permission during this step, often Connect, Speak, or Use Slash Commands; if members untick things to “be safe”, playback just fails silently. When in doubt, re-invite and leave the defaults. Second, do not grant Administrator. Interaction Bot’s invite does not ask for it, and no TTS bot needs it to read messages aloud.

Doing this from a phone works the same way, but the authorization screen may open in your browser, in Discord’s in-app browser, or in a separate tab, and it acts on whichever account that browser is signed into. Our mobile guide to adding a bot on Android and iPhone covers the small-screen differences.

Step 3: restrict who can trigger TTS

Once the bot is in, you control who gets to make it talk. A TTS bot that answers any member in any channel is spam waiting to happen, so give it a home:

• Create a dedicated text channel, for example #tts-text, and, if you like, pair it with the voice channel where speech will play.
• On that channel, set Discord’s permissions so only the roles you trust can send messages and use the bot’s commands. A small test server can keep the defaults; a busy server should start closed.

For a fuller picture of the difference between a voice-channel TTS bot and Discord’s built-in /tts, our guide to Discord text-to-speech bots compares both side by side.

Step 4: connect the bot to a voice channel

TTS bots play audio in a server voice channel, so the bot has to be in one. Join the voice channel where you want speech to be heard, then tell the bot to follow you. Interaction Bot’s command for this is /connect. Once it is in the channel, the bot’s text-to-speech feature can read a typed message to everyone listening, which is what its homepage advertises.

While you are at it, check the bot’s settings for guardrails before opening it to the whole server: maximum message length, volume, a default voice, and any cooldown or blocked-words options it offers. Interaction Bot’s dashboard is at the bot’s website. Log in with Discord, pick your server, and the configuration pages (including voice and translation defaults) are in the left-hand menu.

Step 5: test by sending a message

Now prove it works before announcing anything. In the text channel the bot watches, type the bot’s TTS command followed by a short sentence. On Interaction Bot that is /tts, one of the commands its docs list for reading a message aloud in a voice channel. You should hear the sentence in the voice channel moments later.

Two things to expect on a fresh install. Slash commands do not appear instantly: they are registered through Discord’s interactions system, and a brand-new command can show up a little later than the authorization. And if you type / and see no bot commands at all, the invite was likely made through an old link that omitted the applications.commands scope; re-run the bot’s current invite link, which fixes it.

Where people get stuck: the four classic failures

If something breaks, it is almost always one of these:

The site’s troubleshooting guide for Discord bots that go quiet works through the permission and channel fixes in full, including how to tell a settings problem from an outage by checking the bot’s status page.

Bottom line

Adding a TTS bot to a Discord server is a web-page job, not an app-menu job: open the bot’s invite link, choose your server and review the 24 requested permissions on Discord’s official authorization screen, then click Authorize. After that, three settings decide whether it is useful or chaotic: which text channel feeds it, which voice channel it is connected to, and which roles are allowed to trigger it. Set those, test with one short sentence, and open it up.