Discord Bot Maker
Make a Discord bot with a few readable Python functions. Discord Bot Maker handles command registration, typed slash options, responses, buttons, permissions, cooldowns, saved data and background tasks.
from discord_bot_maker import Bot, CommandContext, Embed
bot = Bot.from_env()
bot.reply("hello", Embed("Hello, {{user.display_name}}!", "Welcome to {{server.name}}."))
@bot.command(description="Give yourself a point")
def point(ctx: CommandContext):
return f"You have {ctx.user_store.increment('points')} points."
bot.run(sync=True)
No subclass, command tree, interaction response plumbing, or database setup is needed for this example. Sponge demonstrates the package as a real bot, including a pet duck, saved snack counts, server settings, polls and restart-safe reminders. Sponge's personality lives in its script; the library is reusable for any bot.
The prepared stable release is 2.0.0. The project uses Python 3.15.0; the package declares Python 3.10+. Sponge has connected and synchronized its expanded command set live; automated tests cover the authoring features offline. More live feature testing is welcome.
Create your Discord bot
- Open the Discord Developer Portal, choose New Application, and give your bot a name.
- Open Bot. Add a bot user if prompted, then choose Reset Token and copy the bot token. This is different from the application ID, public key, and OAuth client secret. Keep it private; reset it if it is exposed.
- Open Installation, enable Guild Install, and select the
botandapplications.commandsscopes under Default Install Settings. - Give it View Channels, Send Messages, and Embed Links, then save. Open the Discord Provided Link, select Add to Server, and authorize it in a server you can manage. Administrator permission is unnecessary.
- For faster testing, enable User Settings → Advanced → Developer Mode in Discord, then right-click your server and choose Copy Server ID.
Slash commands do not need privileged intents. Enable Message Content Intent
on the Bot page only if you use prefix commands. Enable Server Members Intent
if you use bot.welcome(). These bots connect through the Gateway; leave
Interactions Endpoint URL empty. No public key or OAuth client secret is
needed to run the Python bot.
Keep the token in a local .env file next to your script and add .env to
.gitignore. Bot.from_env() reads it automatically. The runnable examples below
show the variable names. For installation details, see
Discord's installation guide
and our first-bot guide.
Run Sponge
The current checkout already has a virtual environment. Put these in .env:
DISCORD_BOT_TOKEN=your_bot_token
DISCORD_GUILD_ID=your_server_id
DISCORD_CHANNEL_ID=
The channel is optional. .env is ignored by Git and loaded automatically.
Stop any previous instance, then run:
.venv/bin/python examples/sponge.py --sync
Try /hello, /wisdom, /duck, /feed, /motto, /duck_motto, /poll,
/remind, /reminders, or /cancel_reminder. motto requires Manage Server.
Use --sync after changing command definitions; omit it for ordinary restarts.
The original minimal example remains available:
.venv/bin/python examples/bot.py --sync
.venv/bin/python examples/bot.py --preview hello
First-time Discord setup explains the bot token, installation,
permissions, server and channel IDs. Neither example requires an interactions URL.
Slash commands need no privileged intents. Calling bot.welcome() opts into
Server Members Intent, which must also be enabled in Discord's Developer Portal.
Install from a fresh checkout
uv venv --python 3.15 .venv
uv pip install -e .
For contributors running all backend tests, install the locked dependencies too:
uv pip install -r requirements.lock
uv pip install --no-deps -e .
.venv/bin/python -m pytest -q
The core library does not require FastAPI, PostgreSQL or the web frontend. Those
are separate optional dependencies. requirements.lock pins the tested full
contributor/backend environment; the published package uses compatible ranges.
Coding agents
AGENTS.md and CLAUDE.md ship inside the Python package with public API patterns,
examples, setup, and offline testing guidance. Agents do not automatically read
instructions from installed dependencies. Point your agent at the installed guide:
python -c "from importlib.resources import files; print(files('discord_bot_maker').joinpath('AGENTS.md').read_text())"
In this repository, the root AGENTS.md and CLAUDE.md point to the same guide.
Learn the API
- Authoring guide: command functions, response types, permissions, storage, polls, reminders and schedules.
- Sponge's source: a complete consumer of the public package API.
- AI coding reference: canonical patterns, API links and boundaries.
- v2 implementation plan and implementation status: the visual editor is in active development; hosted deployment checks remain.
Portable definitions
Static text/Embed replies can be exported with bot.to_definition() for the shared
preview/Discord engine. Python callbacks and interactive/background features stay
in Python source; export rejects these instead of silently discarding them.
.venv/bin/discord-bot-maker template greeting > bot.json
.venv/bin/discord-bot-maker validate bot.json
.venv/bin/discord-bot-maker preview bot.json --command hello
.venv/bin/discord-bot-maker run bot.json --sync --guild-id YOUR_SERVER_ID
Existing users
The distribution is discord-bot-maker; Python imports stay discord_bot_maker.
DBot, createCommand(), bRun(), and the original prefix API remain available.
For new bots use Bot.from_env(), reply() and @bot.command().
The unfinished v1 Command builder is now an immutable command definition.
User-facing replies have no forced attribution or author mentions.
MIT licensed. Created by Aaryan Dehade.
PyPI release
After publishing 2.0.0, install the stable release on PyPI with:
python -m pip install --upgrade 'discord-bot-maker==2.0.0'
See the release guide, changelog, and v1 migration guide. Only the Python package is being prepared for PyPI; the web app is a separate work in progress.
Metadata
Release files for discord-bot-maker 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| discord_bot_maker-2.0.0.tar.gz | 82.4 kB | Without provenance | Details for discord_bot_maker-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| discord_bot_maker-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for discord_bot_maker-2.0.0-py3-none-any.whl |
Total release size: 123.9 kB
Release files / discord_bot_maker-2.0.0.tar.gz
| Download URL | discord_bot_maker-2.0.0.tar.gz |
|---|---|
| Size | 82.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b2154c91ff163920db60c2ab76a67a72994fb9627555b9a54fd79eff68e4875e
|
|
BLAKE2b-256 checksum How to use checksums |
c717add6299cea2106362aa71458bcaea10f2d2f62dc9cf0b9f8f4f4d401993b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.15.0
|
Release files / discord_bot_maker-2.0.0-py3-none-any.whl
| Download URL | discord_bot_maker-2.0.0-py3-none-any.whl |
|---|---|
| Size | 41.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ae186e9ff92d52abd9c90d5e9b716a3cfd8d6537853d0bd885acc2123898f8d6
|
|
BLAKE2b-256 checksum How to use checksums |
6d811eb2a0202fbe659e6bf22290bc0d2a359f9b01e53671456f2c443afa4b8f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.15.0
|
Security for discord-bot-maker 2.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.