How to Add Bots to a Discord Server: Step-by-Step Guide

Discord apps—often still called bots—can add moderation, automation, games, utilities, or support tools. Installing one means choosing a trusted app, authorizing it for the correct server, reviewing its access, and testing it. If you lack the required server permission, ask an authorized manager to install it.

Quick Setup Overview

1. Choose a trusted Discord app or bot.
2. Open its official invite or installation page.
3. Sign in to Discord if its own authorization page asks you to.
4. Select the correct server installation.
5. Review every requested permission.
6. Authorize the app.
7. Complete any verification requested by Discord.
8. Confirm that the app appears in the server.
9. Test a command from its official documentation.
10. Adjust its role and channel access if necessary.

1. Make Sure You Have Permission to Add Apps

You must be the server owner or have Manage Server to add and manage server apps. Ordinary members may use installed apps but cannot install them for the server.

Account installation is different: it makes the app available to your account in supported spaces. For this task, choose server installation when Discord offers both.

Do not transfer ownership or claim permissions you were not given. Ask the owner if the server does not appear.

2. Choose a Trusted Bot or Discord App

Discord’s App Directory is a useful starting point on desktop or web. You can also use a developer’s verified official site. Check the exact app, developer, support and privacy details, and whether its access fits its purpose.

The Directory is not a guarantee that an app suits your server. Avoid random invites, copied sites, unexpected messages, and apps promising free Nitro or urgent “verification.” Discord’s guide to discovering and adding apps explains the installation contexts.

3. Open the Bot’s Official Invite or Install Page

From the App Directory, install from the app’s profile. On a developer site, verify the domain first. The link should lead to Discord’s authorization flow, which identifies the app and requested access.

Stop if a page asks you to paste code, run an unknown program, or provide an account token. Normal public-app installation needs none of these.

4. Select the Correct Discord Server

Confirm the signed-in account, then choose the intended server carefully from those available.

If it is missing, check the account and Manage Server access. The app may also restrict installation contexts. Do not request Administrator merely to make a server appear.

5. Review the Bot’s Permissions Before Authorizing

Requested permissions should match what the app actually does. Common examples include:

• View Channels: see permitted channels and their content.
• Send Messages: post in allowed text channels.
• Manage Messages: delete messages sent by other members.
• Manage Roles: create or manage roles below the app’s role, within the permissions it holds.
• Moderate Members or Timeout Members: place members in timeout.
• Administrator: receive all permissions and bypass channel permission restrictions.

A moderation app may need more access than a poll app. Approve only what supports the features you will use. Administrator is too broad to grant merely for setup convenience.

Read the developer’s explanation for any powerful permission. Broad access is not proof of malicious intent, but an unexplained mismatch warrants investigation. Discord’s Roles and Permissions guide documents Administrator and role hierarchy.

6. Authorize the App

Recheck the app, server, and permissions, then approve through Discord’s authorization screen. Discord may request sign-in, normal multi-factor authentication, a CAPTCHA, or confirmation.

Enter credentials only into a verified Discord-controlled login. A developer should never ask for your Discord password, account token, bot token, backup codes, 2FA code, or 2FA secret. Never disable security checks or send those details to “support.”

7. Check That the Bot Joined the Server

For a server installation, find the app in the member list and Server Settings > Integrations > Bots and Apps. Confirm its identity and any created role. The Server Integrations page also records useful installation details.

An account-installed app appears under User Settings > Authorized Apps and may not join as a member. Presence alone is not a complete health test, so try a documented command.

8. Test the Bot’s Commands

Many apps use slash commands: type / and select one from Discord’s picker. Others use the app launcher or Apps menu on a message or member. Follow the current documentation.

Start with a harmless help or status command. Do not guess an old prefix unless documented. Confirm the response and test the intended member access.

9. Adjust the Bot’s Role and Permissions

A bot commonly receives a role. If it has Manage Roles, it can affect roles below its highest role, so place it above only what it must manage.

Review server-wide permissions and channel overrides. Too little can break a feature; too much increases risk. Change one permission at a time and retest instead of granting Administrator.

10. Limit the Bot to Specific Channels

Depending on the app and server, you may have three separate controls:

• channel overrides that limit what the bot role can see or do;
• Discord command permissions that limit who can use commands and where; and
• the app’s own configuration for allowed channels or features.

Keep moderation output in a staff area or utility commands in a bot channel when useful. Discord’s app moderation guide documents current controls.

Not every app supports every control. Command restrictions do not remove role powers, and channel denies cannot confine an app with Administrator.

How to Add a Discord Bot on Mobile

On a phone, open a trusted install link or available app profile. Let Discord or the browser handle authorization, choose the server, and review access before approving.

The App Directory is documented for desktop and web. Mobile button placement and browser-to-app handoff vary by platform and version.

Why Can’t I Add a Bot to My Discord Server?

Common reasons include:

• you do not own the server or lack Manage Server;
• you are signed in to the wrong Discord account;
• you selected account installation instead of server installation;
• the app does not support that installation context;
• the authorization session or browser has become stale; or
• Discord or the app is experiencing a service incident.

Refresh the official flow and verify the account before changing permissions. Use official support for app-specific restrictions.

Bot Joined but Commands Don’t Work

Check whether the app can view the channel, send the required response, and access any role it must manage. Confirm that application commands are allowed for the member and channel, and that the documented command is enabled for this installation.

The app may still be registering commands, be offline, or have a service problem. Role hierarchy can block management actions. Check official docs and status; do not reset tokens, reinstall repeatedly, or grant Administrator without evidence.

Bot Is Offline

An offline bot often indicates a developer-side hosting or service problem. A server owner cannot repair the app’s backend.

Check official app support and Discord Status. If an incident exists, wait. Avoid repeated reinstalls when no server setting changed.

How to Remove a Bot from a Discord Server

If you own the server or have Manage Server, remove the app from Server Settings > Integrations or kick its bot member using the current server controls. Deleting only its role does not uninstall the app.

If the app is also on your account, remove it separately under User Settings > Authorized Apps > Deauthorize. Review app-created webhooks and leftover roles, deleting only confirmed unused items. Server removal may not erase developer-retained data; consult its privacy policy.

Should You Give a Discord Bot Administrator?

Usually, no. Administrator grants every permission and bypasses channel restrictions, so it removes much of your ability to contain the app.

Some management apps document a reason for it. Verify the developer, understand the feature, prefer granular access, and review the role after installation.

How Many Bots Should a Server Have?

There is no useful universal number. Add apps for defined needs; duplicate moderation, logging, or utility bots create confusion and more access to audit.

A smaller set is easier to configure, test, and remove. Audit it periodically.

Security Checklist Before Adding Any Discord Bot

• Start from the App Directory or the developer’s verified official source.
• Check the exact domain, app identity, developer, privacy information, and support link.
• Compare each requested permission with the app’s documented purpose.
• Never share an account token or bot token.
• Never hand a developer your password, 2FA code, secret, or backup codes.
• Never disable 2FA to complete an installation.
• Do not paste browser-console scripts or code supplied by a stranger.
• Do not run an unknown executable or scan an unsolicited login QR code.
• Review the app role and channel access immediately after installation.
• Remove apps you no longer use.

Discord’s scam protection guidance specifically warns against unknown downloads, pasted code, shared passwords or authorization tokens, and unverified QR codes.

What to Do After Adding the Bot

Enable only needed features, test with a normal member role where practical, and document powerful permissions. Check configuration and logs after real use.

Periodically remove unused integrations and reduce access that is no longer necessary.

Frequently Asked Questions

Can anyone add a bot to a Discord server?

No. Discord currently requires the server owner or a member with Manage Server to add and manage a server app. Other members may still be allowed to use installed apps.

Is it safe to add Discord bots?

It can be, when you verify the source and developer, review permissions and data access, and keep privileges limited. An App Directory listing does not replace your own review.

Why is my server not showing when I try to add a bot?

You may be using the wrong account, lack Manage Server, have selected an account-only installation, or be using an app that does not support that server context.

Can I add a Discord bot from my phone?

Yes, when the app provides a supported install link or profile flow. Use the Discord authorization screen, select the server, and review permissions; the exact browser-to-app flow varies by mobile platform.

Should a Discord bot have Administrator permission?

Usually not. Administrator grants all permissions and bypasses channel restrictions. Approve it only after verifying a trusted app's documented need and considering narrower permissions.

How do I remove a bot from my Discord server?

An authorized server manager can remove it from Integrations or kick its bot member. If it was also installed to your account, deauthorize that copy separately under Authorized Apps.