Skip to main content
This page is the short version. Each step links to the page that explains it properly — skip ahead whenever you want more detail.

Invite the bot

Use the invite link and pick your server.Keep Administrator ticked unless you have a specific reason not to. Most of the bot works without it, but the parts that don’t — antinuke reverting a role deletion, VoiceMaster creating channels, ticket categories — fail in ways that are annoying to debug. You can always trim permissions later.
After inviting, drag mira’s role near the top of your role list. Discord will not let any bot manage a role that sits above its own, so a low-positioned bot silently fails at half the things you ask of it. This is the single most common setup problem.

Set a prefix

The default is !. If another bot already uses it, change it:
You can also run !prefix add to keep more than one, or set a personal prefix that works in every server you’re in.

Turn on antinuke

Do this before anything else. Antinuke watches for destructive admin actions and punishes whoever performs too many of them too quickly.
Then whitelist the people who are supposed to do bulk work:
Full walkthrough → Antinuke

Set up moderation roles

mute and jail need roles and channel overwrites to exist. One command explains and creates what’s missing:
Then, so that punishments escalate on their own:
More → Punishments and Warnings

Point logging at a channel

Events are grouped into categories, so you can enable a whole category at once or pick individual events. Splitting them across multiple channels works too.More → Logging

Greet new members

That’s the plain version. The {...} syntax is the scripting language — it’s how you build embeds, buttons and containers for every customisable message in the bot.More → System messages

Add the fun bits

Whatever your server actually needs:

Levels

!level toggle on

Starboard

!starboard add #starboard ⭐

VoiceMaster

!voicemaster setup

Tickets

!tickets setup

Social feeds

!tiktok add #feed username

Reposter

!reposter status on

​
Checking your work

Two commands give you a full picture of what’s currently configured:
!configuration (alias !config) is the overview — it walks every module and shows what’s on, what’s off, and which channels things are pointed at. It’s the fastest way to spot something you forgot.
Once you’re happy with the setup, run !backup to snapshot it. If someone wrecks the server later, restoring from a backup is a lot faster than doing all of this again.