Run
Custom bot identity
Your own name and avatar on the bot.
By default the server is served by the JP Metamods application: its name and avatar. With this option it is served by an application of your own instead, with the same features and settings; only the identity members see changes.
Create an application in the Discord developer portal, switch on the two privileged intents (server members, message content), paste the application id and the bot token in the dashboard. The token is checked with Discord before it is stored, stored encrypted, and never shown again.
Plan: Business · Add-on on Free and Pro
Your brand, not ours
Members see your bot’s name and avatar on every message, panel and log line.
Nothing to host
One process serves every server; your bot is a second Discord connection in it, running the same code.
Safe to try
A token that fails to log in shows as an error and the server stays with the JP Metamods bot. Disable keeps the token and hands the server back; Remove forgets it.
How it works
The dashboard’s tour walks you through these same steps on the page itself, one setting at a time.
- 1
Create the application
In Discord’s developer portal, with the two privileged intents on.
- 2
Paste id and token
Checked with Discord, stored encrypted.
- 3
Invite yours, remove ours
The status card says the next step, so members see one bot.
What you control
- Application id and token
- Verified before storing; never shown again.
- Disable / Remove
- Hand the server back, keep or forget the token.
Questions people ask
Do I need to host anything?
No. The bot runs on our infrastructure under your application.
Can I switch back?
Any time: Disable hands the server back to the JP Metamods bot immediately.
Add the bot, run the tour, invite your members
It takes one afternoon. The captcha, the roles and the welcome are waiting for them.