> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mira.lgbt/llms.txt
> Use this file to discover all available pages before exploring further.

# Quick Start

> Add mira and get it set up in a few minutes.

This page walks you through it from an empty server to a working bot. It takes a few minutes, and each step builds on the one before it, so go in order.

<Steps>
  <Step title="Authorize mira" icon="user-plus">
    Open the link below and pick your server from the dropdown. You need the **Manage Server** permission in that server to add a bot at all, so if your server isn't listed, that's usually why.

    Leave the requested permissions checked. Administrator is the simplest option and saves you from chasing down a missing permission later.

    <Card title="Authorize mira" icon="plus" href="https://discord.com/oauth2/authorize?client_id=1459655092889452545&permissions=8&scope=bot+applications.commands">
      mira#6767
    </Card>

    <Warning>
      This is the **real mira**. Its ID is `1459655092889452545`, and that's the only thing worth
      checking, since anyone can copy a name and an avatar but nobody can copy an ID. If a bot
      calling itself mira isn't listed in these docs, it isn't ours.
    </Warning>
  </Step>

  <Step title="Move the role to the top" icon="arrow-up">
    mira is in the server now, but it landed at the bottom of your role list, which means it can't touch anything above it. Discord only lets a bot act on roles and members ranked below its own role.

    Go to **Server Settings > Roles** and drag mira's role above every role you want it to manage. If you plan on it managing your staff, that means above your staff roles too.

    <Tip>
      The top of the list is the safest place for it. Anything you leave above mira is a gap you'll run into eventually.
    </Tip>
  </Step>

  <Step title="Check that it responds" icon="message-circle">
    With the role sorted out, make sure mira is actually listening. Send `!help` in any channel it can read and you should get a response.

    The default prefix is `!`. Mentioning mira works as a prefix too, in every server, so `@mira help` gets you a response even if the prefix has been changed and you don't know what it is.

    Nothing back at all? Check that mira can see the channel and has permission to send messages in it.
  </Step>

  <Step title="Set your prefix" icon="terminal">
    Now that mira is responding, you can pick what it responds to. This step is optional, and `!` is fine if it isn't already taken by another bot in your server.

    Use `prefix set` to replace the default with your own, or `prefix add` if you'd rather run more than one at a time. `prefix reset` puts everything back to `!`.

    <Note>
      Removing your last prefix restores the default instead of leaving you with none, so you can't lock yourself out.
    </Note>
  </Step>
</Steps>

## You're set up

mira is in the server, ranked high enough to do its job, and answering to a prefix you chose. That's the whole setup. Everything from here is optional and can be done whenever you want.