How to Add a Bot to Your Discord Server (2026)
To add a bot to your Discord server, click the bot's "Add to Server" or "Invite" link, sign into Discord, pick the server from the dropdown, review the permissions checklist, complete the captcha, and authorize. The bot appears in your member list within seconds. You need the Manage Server permission on the target guild for the OAuth flow to succeed.
Key Takeaways
- You need the Manage Server permission on the target Discord server to authorize any bot
- Most bots are added through Discord's OAuth2 invite flow, not file uploads or downloads
- Default invite links request permissions the bot needs — uncheck what you don't want before authorizing
- Bots typically join within 5 seconds; a missing bot usually means the captcha was abandoned
- PeakBot uses one-click invite at peakbot.pro and replaces the MEE6/Carl-bot/Dyno workflow with AI
Step 1: Find a Trustworthy Bot Source
Before you click any "Add to Server" button, confirm where the link came from. Bots can request dangerous permissions like Administrator, Manage Webhooks, and Manage Roles — all of which can be abused if the bot is malicious.
The three reliable places to find legit bots in 2026:
- The bot's official website (e.g., peakbot.pro)
- The bot's verified Discord support server
- top.gg or discords.com (third-party directories with moderation)
I learned this the hard way three years ago when a "free Nitro generator" bot deleted half my channels in under a minute. Stick to verified sources. If a bot has a blue checkmark inside Discord's invite screen, it's been verified by Discord and has passed identity review — that's the strongest signal you can get.
What "verified" actually means
Discord verifies bots that hit 75+ servers and pass an identity check from the developer. Verified bots get a small badge in the user profile and can request additional intent scopes. PeakBot is verified, which is why the OAuth screen shows the checkmark next to the bot avatar.
Step 2: Click the Invite Link
Every bot has a unique OAuth2 URL that looks like this:
https://discord.com/oauth2/authorize?client_id=XXXX&permissions=YYYY&scope=bot%20applications.commands
You don't build this URL yourself. You click it. For PeakBot, the link is at peakbot.pro → Add to Discord in the top-right of the homepage.
When you click an invite, Discord opens the Authorize screen in your browser (or in the desktop app if you have it set as your default handler). If you're not signed in, it'll ask you to log in first. Use the email and password tied to the account that owns or moderates the target server.
What if the link is expired?
Bot invite links don't expire on their own — but if the developer regenerates the bot's OAuth secret, every old invite link breaks instantly. If you see "This application is unavailable", grab a fresh link from the bot's website. Don't accept a "fixed" link from a random DM.
Step 3: Pick the Right Server
The Authorize screen shows a dropdown labeled Add to Server. Click it and you'll see every server where you have Manage Server permission. If your target server isn't listed, you don't have permission to invite bots there — ask an admin instead.
| Permission you have | Can invite bots? |
|---|---|
| Server Owner | Yes (always) |
| Administrator | Yes |
| Manage Server | Yes |
| Manage Channels only | No |
| Moderator role without Manage Server | No |
| Default member | No |
Once you select the server, the bot is locked to that guild for this OAuth session. You can't change it without going back.
Step 4: Review and Adjust Permissions
This is the step most users skip — and it's the most important one. Discord shows you every permission the bot wants, with a checkbox next to each one. Uncheck anything that feels wrong.
Common permissions and what they actually do:
| Permission | What it lets the bot do | Risk if abused |
|---|---|---|
| Administrator | Everything, bypasses all role checks | Catastrophic — full server control |
| Manage Roles | Create, delete, assign roles below its highest role | High — can lock out members |
| Manage Channels | Create, delete, modify channels | High — can wipe channel structure |
| Kick Members | Remove members (rejoinable) | Medium |
| Ban Members | Permanently ban members | High |
| Manage Messages | Delete any message, pin, unpin | Medium |
| Read Message History | See past messages | Low (but privacy-relevant) |
| Send Messages | Post in channels | Low |
| Embed Links | Send rich embeds | Low |
Rule of thumb: if a bot demands Administrator and it's not a verified utility bot, walk away. PeakBot, for example, requests Manage Roles, Manage Channels, Send Messages, and Embed Links — never blanket Administrator. You can read the full permission breakdown in the PeakBot docs.
Trimming permissions you don't need
If a bot you trust asks for Manage Webhooks but you only want it for moderation, you can uncheck Webhooks before clicking Authorize. The bot will still join — it just won't be able to use that capability. You can re-enable it later from Server Settings → Integrations → [Bot Name].
Step 5: Complete the Captcha and Authorize
Discord drops an hCaptcha (sometimes Cloudflare Turnstile in 2026) right before the bot joins. This is to stop automated bot-flooding. Click the checkbox, complete the image puzzle if it appears, and hit Authorize.
If the captcha says "try again later" three times in a row, your IP is rate-limited. Wait 15 minutes, switch networks, or use the desktop app instead of the browser. This happens often on shared Wi-Fi like university or office networks.
Step 6: Verify the Bot Joined
Switch back to your Discord server. The bot appears in the member sidebar on the right within ~5 seconds. You'll also see a system join message in your default channel that says "[BotName] just joined the server".
If you don't see the bot:
- Refresh Discord (Ctrl+R on desktop, swipe down on mobile)
- Check Server Settings → Members and search the bot name
- Check Server Settings → Integrations — if the bot is there but not in members, it joined but is offline
PeakBot will also DM you a welcome message with the next-step quickstart link, which I find genuinely useful — it points straight at the AI Server Builder onboarding flow.
Do I need a bot to run a healthy Discord server?
Technically no. Discord ships with native moderation tools (AutoMod, Timeout, Verification Levels) that cover the basics. But for anything beyond the basics — tickets, leveling, reaction roles, scheduled announcements, music, full-server templating — you need a bot. The native tools don't cover it.
The four bots most people consider in 2026:
| Bot | Strengths | Weaknesses | Free tier |
|---|---|---|---|
| MEE6 | Brand recognition, leveling | Aggressive paywall, dated UX | Limited |
| Carl-bot | Reaction roles, automod | No AI features, complex setup | Generous |
| Dyno | Modular, customizable | Outdated dashboard | Generous |
| PeakBot | AI Server Builder, 30+ features free | Newer brand | 30+ features free |
If you want a deeper comparison, the PeakBot vs MEE6 breakdown goes feature-by-feature.
Step 7: Run the First-Time Setup
A freshly added bot does nothing until you configure it. Most bots either:
- DM you a setup link, or
- Respond to a slash command like
/setupor/dashboard
PeakBot uses both. Type /dashboard in any channel where the bot can read messages and you'll get a clickable button that opens peakbot.pro with your server pre-selected. From there, the AI Server Builder takes over: type "gaming clan with comp scrims, vods, and casual chat" and PeakBot generates the full channel/role/permission structure in under 60 seconds. Pro at $8.50/mo unlocks the AI Server Builder; the rest is free.
Setting role hierarchy correctly
After the bot joins, drag its role above the roles it needs to manage in Server Settings → Roles. Discord's role hierarchy is strict: a bot can only manage roles below its own highest role. If you skip this, every assign role command will fail silently.
Troubleshooting Common Bot Invite Failures
"This application is unavailable"
The bot's OAuth secret was rotated, or the bot was deleted by Discord Trust & Safety. Get a fresh link from the bot's website.
"You are missing permissions"
You don't have Manage Server on the target guild. Ask the owner or an admin.
Bot joins but is offline
The bot's host (the server actually running the code) is down. This is on the developer, not you. Check the bot's status page — PeakBot publishes uptime at peakbot.pro/status.
Bot is online but slash commands don't appear
Discord caches application commands for up to 1 hour on first install. Restart your Discord client and wait. If they still don't appear, the bot wasn't given the applications.commands scope — re-invite with a fresh link.
For deeper protocol-level reading, Discord's official OAuth2 documentation covers every edge case.
Frequently Asked Questions
How do I add a bot to a Discord server on mobile?
Open the bot's invite link in your phone's browser. iOS and Android both prompt to open in the Discord app — accept that. The Authorize flow on mobile is identical to desktop: pick the server from the dropdown, review permissions, solve the captcha, authorize. Total time: under 30 seconds. The bot appears in your member list immediately.
Why does the bot need Administrator permission?
It usually doesn't. Bots that demand Administrator are either lazy (the developer didn't scope permissions properly) or shady. Verified utility bots like PeakBot scope to exact permissions: Manage Roles, Manage Channels, Send Messages, Embed Links. If a bot insists on Administrator, audit it carefully or pick an alternative.
Can I add the same bot to multiple servers?
Yes — bots scale across thousands of servers. Re-run the OAuth invite flow for each server. Each install is independent: configuration on Server A doesn't carry to Server B. Some bots (PeakBot included) let you copy a configuration from one server to another via the dashboard.
How do I remove a bot I added by mistake?
Go to Server Settings → Integrations → [Bot Name] → Remove. The bot leaves instantly and all its data tied to your server is wiped within 30 days per Discord's privacy rules. You can also right-click the bot in the member list and select Kick, but Integrations is cleaner because it revokes the OAuth grant fully.
Is it safe to give bots Manage Roles?
For verified bots from trusted sources, yes — Manage Roles is required for any bot that does reaction roles, leveling rewards, or auto-roles on join. The safety control is role hierarchy: a bot can only manage roles ranked below its own. Keep your admin and moderator roles above the bot's role, and Manage Roles becomes safe by design.
What's the difference between bot and applications.commands scope?
The bot scope lets the application join your server as a member. The applications.commands scope lets it register slash commands. Modern bots need both. If you only grant bot, the bot joins but / commands won't show up. If you only grant applications.commands, slash commands work but the bot can't see messages or do background work.
Conclusion
Adding a bot to your Discord server is a five-minute job once you know the OAuth flow: find a trustworthy source, click invite, pick the server, trim permissions, solve the captcha, authorize. The hard part isn't the install — it's picking a bot that doesn't paywall the basics or demand Administrator permissions you can't audit.
PeakBot keeps 30+ features free forever and gates only the AI Server Builder behind $8.50/mo Pro. If you want to spin up a fully built server from a single sentence — channels, roles, permissions, automod rules, all of it — start at peakbot.pro, check the pricing, or read the feature list. The FAQ covers everything else, and the blog has more guides like this one.
