Discord Bot Ideas: 12 Projects Worth Building in 2026

Most lists of bot ideas stop at a name and a sentence. That skips the part that decides whether your project survives: what Discord lets a bot read, when it has to answer, and what happens once it grows. Every limit below was read in Discord's developer docs and help center in November 2026. One of them changed this year, so older tutorials may be wrong about it.

The Discord rules that shape every idea

• Privileged intents. Guild Presences, Guild Members and Message Content sit behind extra checks. Since June 10, 2026 the trigger is 10,000 unique users who can see your app, not 100 servers. Under that you toggle them in the Developer Portal; past it you have 90 days to apply, then reapply every year.
• Message access. Without Message Content, the text fields of messages come back empty, except messages your app sent, DMs to it, messages that mention it and some replies to it.
• The 3-second rule. An interaction needs an initial response within 3 seconds or its token dies. Once you respond, the token lasts 15 minutes for follow-ups.
• Verification. An app has to be verified to scale past 100 servers, which includes the team owner verifying their identity through Stripe.
• Rate limits. A bot gets 50 requests per second globally, plus limits per route. An IP that makes 10,000 invalid requests in 10 minutes is temporarily blocked.
• Command caps. 100 global slash commands, 15 global user commands and 15 global message commands per app.

One more worth knowing before you write a line. Interactions can reach you over a Gateway connection or as HTTP requests to an endpoint that validates Discord's signatures, and you pick one or the other. HTTP is enough for anything built from commands, buttons and modals. Server events, such as a member joining, arrive over a persistent WebSocket, so those features need a process that stays up.

All 12 Discord bot ideas at a glance

The ideas, with what to build first

1. Release and alert notifier

Post deploys, failed builds and error alerts into the channel your team already reads. Strictly speaking, this doesn't need a bot: an incoming webhook takes a POST and shows the message, no persistent connection required. Build one source first, say your CI pipeline. You'll store the webhook URL per project and event IDs so a retry doesn't post twice. Treat that URL like a password, because whoever holds it can post to the channel.

2. Trivia game

A /trivia command, four buttons, a scoreboard. That's the whole first version. Store questions, plus scores keyed by server and user ID. Keep it member-triggered: Discord's Developer Policy bans automating messages just to keep a server looking active, so a scheduled question posted to fill a quiet channel is the wrong design. If trivia is too small, our list of vibe-coded weekend games has bigger game projects.

3. Role picker

Admins post one panel; members click to get the roles they want. Build the select menu first and store a mapping of option to role ID per server. You don't need the Guild Members intent, because each interaction already includes the member's roles. A greeting on join does need it. The classic bug is role order: a bot can only grant roles below its own highest role, so your setup command should check that and say so.

4. Save-for-later app

Apps can be installed to a user, not just a server, and that opens up personal tools. Add a message command called "Save", reply privately, and list saved items with /saved. Store the user ID, message link and an optional note. Keep it that small. Discord's policy limits API data to what your stated features need, so a link beats a growing copy of other people's messages.

5. Event RSVP bot

Start with /event create, which makes a native scheduled event and posts RSVP buttons. A server can have 100 events scheduled or active at once. Store event IDs, UTC start times and member time zones, because time zones are where these bots embarrass themselves. Discord's native polls (up to 10 answers, open up to 32 days) handle "which night works?" without extra code. Send reminders in a channel: its policy bars contacting users without explicit permission, so DMs must be opt-in.

6. Async standup bot

/standup opens a modal with three questions, then the answers roll into one digest in the team channel. You need the roster, answers and each person's time zone. There's no reason to read chat here, so Message Content never enters the picture. Add a summary from an AI model later if people actually read the digest. Don't measure anyone with it: the policy also bars using API data to profile users.

7. Feedback-to-backlog bot

A user posts a bug report in chat. A moderator right-clicks it, picks "Send to backlog", and a GitHub issue appears. Message context menu commands hand your bot the full message, with no privileged intent, so this is one of the cleanest designs on the list. Store the message link, author, issue URL and status, then post back when the issue closes. Keep your GitHub token on the server and show moderators what will be sent before it goes.

8. Support ticket bot

A button panel opens a modal; submitting it creates a private thread for the requester and your support staff. Private threads can only be created in regular text channels, so check that during setup. Store ticket ID, thread ID, assignee and status. Here's the catch most builders hit late: saving a transcript means reading what people typed in the thread, and that needs Message Content. Ship without transcripts first, using only modal text and status.

9. Game stats and linked roles

Build /link and /stats first. Discord's own user-install tutorial uses a similar game integration with /link, /profile and /leaderboard. The next step is linked roles, where admins require a rank your app reports through role connection metadata; that needs an OAuth2 flow with the role_connections.write scope. Store the Discord ID, game account ID, tokens and cached stats. Never ask for a password (Discord bans it), and read the game publisher's API terms before you start.

10. Docs answer bot

/ask searches your documentation and replies with an answer plus source links. Store document chunks, embeddings and a log of unanswered questions, which can become your docs backlog. Model calls can outlast the 3-second limit, so defer first and send the answer as a follow-up. Answer from your docs, not chat history: Discord bans training AI models on message content without express permission. Our guide to using AI in coding covers the review habits you'll want while building it.

11. Moderation queue

Start with a "Report" message command that drops the message into a private queue with action buttons, then log each decision. That covers a lot of value with no privileged intent. Discord's AutoMod can block messages before they're sent, and your bot can manage its rules with the Manage Server permission, but each server gets only 6 keyword rules and 1 each for spam, preset wordlists, mention spam and member profiles. Scanning every message yourself means Message Content and, past 10,000 users, a review. A bot also can't kick or ban anyone whose highest role is equal to or above its own.

12. Premium server add-on

This one sits on top of a bot people already use. Create one guild subscription, which entitles a whole server, and gate one feature behind it. Store SKU and entitlement data. The paperwork is the hard part: a verified app owned by a team, a team owner aged 18 or over, 2FA, a terms of service and privacy policy, and either slash commands or approved Message Content access. Premium Apps is available to developers based in the US, EU and UK, and an app becomes eligible for payouts after its first $100. Where it's supported, the policy says paid features covered by Premium Apps must also be offered through it, at prices no higher than elsewhere. Our list of vibe coding projects that make money covers other ways to charge.

First prompts to try

Give any of these to your AI coding tool. Discord's community resources page lists discord.js and discord.py among its libraries, and its first-bot tutorial is in JavaScript. Our Cursor prompts post has more patterns if you work in that editor.

Support ticket bot: "Build a Discord bot in [language] with one admin command, /ticket-panel, that posts a button. The button opens a modal asking for a subject and description. On submit, create a private thread in that channel, add the requester and the user IDs in [staff list], and save ticket ID, thread ID, status and assignee in [database]. Don't request any privileged intents. Keep the token in an environment variable."

Feedback-to-backlog bot: "Create a Discord app that receives interactions over HTTP and validates request signatures. Register a message context menu command called Send to backlog, usable only by members with [permission]. It shows a modal with the message text prefilled and an editable title, then creates a GitHub issue in [repo] containing the message link. Reply privately with the issue URL. Handle duplicate submissions."

Docs answer bot: "Build /ask for Discord. Defer the interaction immediately, search the document chunks in [vector store] for the question, and send a follow-up that answers only from those chunks, with up to three source links. If nothing matches, say so and log the question. Don't read channel messages, and don't store anything except the question text and result status."

How to choose

Join the servers you'd build for and watch what someone does by hand twice a week. That's your idea. Then run it through three questions. Can it work from commands, buttons and modals? If so, you skip privileged intents and can host it on HTTP. Does it need to read chat? Try a message command first, since a person choosing a message is often enough. And what happens at 100 servers and 10,000 users? If the answer is "apply for Message Content", write down your use case now, because Discord asks for it in specifics.

Not sold on Discord as the place to build? Our list of web app ideas covers projects that live outside it.

Frequently Asked Questions

What is a good first Discord bot project?
An alert notifier or a trivia game. The notifier only needs an incoming webhook, with no bot user or persistent connection. Trivia teaches slash commands and buttons, which are the two pieces most other ideas on this list reuse.

Does my Discord bot need the Message Content intent?
Usually not. Discord says slash commands are the recommended replacement for text commands and need no privileged intent. Message context menu commands hand your bot the full message a user picked. A bot can also read messages it sends, DMs sent to it and messages that mention it without the intent.

How many servers can an unverified Discord bot join?
Discord's developer help center says verification is required for an app to scale past 100 servers. The team owner verifies their identity through Stripe and the app must meet the checklist in the App Verification tab of the Developer Portal.

Can a Discord bot make money?
It can sell subscriptions and one-time purchases through Discord's Premium Apps. The app must be verified and owned by a developer team, the team owner must be at least 18, and Discord says Premium Apps is available to developers based in the United States, European Union and United Kingdom. An app becomes eligible for payouts once it has made its first $100.

Do I need a server running all the time?
Not for slash commands, buttons and modals. Discord can send those interactions to an HTTPS endpoint, and its docs include a Cloudflare Workers tutorial. Events such as a member joining arrive over the Gateway, which is a persistent WebSocket connection, so those features need a process that stays up.

Can I train an AI model on my server's messages?
Not without Discord's express permission. Its Developer Policy bans using message content obtained through the APIs to train machine learning or AI models. Answering questions from your own documentation, with a model you call at request time, avoids that problem.