Add your server

Two steps, both done from Discord. Nothing to install on your end.

1. Invite the bot

The bot only needs View Channels and Read Message History to show your channels and messages here. If you also want website visitors to be able to reply (/settings posting true, see below), it additionally needs Manage Webhooks — used only to create one relay webhook per channel that opts in. Replies are posted through that webhook using the visitor's own live Discord username and avatar, it never posts as your bot's own identity and never uses a visitor's real account.

2. Configure your server

Once the bot's in, anyone with the Manage Server permission can run these:

/settings published true

Puts the server in the directory on the homepage. Run it again with false whenever you want it gone.

/settings description

Opens a form to set the short description that shows under your server's name.

/settings tags

Opens a form for freeform tags, one per line, like "gaming" or "chill". No fixed list, write whatever fits.

/settings posting true

Lets website visitors who log in with their own Discord account reply on this server's topics. Off by default, and needs the bot to have Manage Webhooks.

/settings show

Replies privately with your current published state, description, tags, and posting setting, so you can check what's actually live.

What shows up

Every text channel becomes a topic. Every forum channel becomes its own little forum, with its threads as topics inside it. It's all pulled live from Discord on every page load, nothing gets cached or duplicated beyond your published state, description and tags.

Heads up: there's no access control layered on top of this. Whatever the bot can read in your server, anyone visiting this site can read too once you publish it. Only add the bot to channels you're okay with being public.

Logging in with Discord

Visitors can optionally log in with their own Discord account (top right of any page). Logging in never grants anyone access to more than they already have in Discord — it can only narrow what a specific person sees, never widen it beyond the published, anonymous view described above.

If the logged-in visitor is a member of your server, their view of it is filtered to match their actual Discord permissions there: a channel they can't see in Discord (private, role-restricted, whatever the reason), they won't see here either, even though it's part of a published server. This is computed live from their real roles every time, not a one-time snapshot.

If the logged-in visitor is not a member of your server at all, logging in doesn't change anything for them here: they see the exact same public, unfiltered view as an anonymous visitor (everything the bot can read in a published server, same as always). Being logged in only unlocks the member-only filtering above once someone actually is a member.

If you've also enabled /settings posting true, a logged-in member can reply on any topic they have Discord permission to post in. Their reply is relayed into the real channel through a bot-managed webhook, shown under their live Discord username and avatar — it's a relay, not a message sent from their real Discord account, and it's Discord's own permission check (not this site's) that decides whether they're allowed to post there at all.