How rate limiting has been going: how many times Discord asked this server to slow down (the request layer waits automatically), and the invalid-request counter that matters because Discord temporarily bans an IP after 10,000 invalid responses in ten minutes. Useful when calls feel slow.

Identity and status of a connected Discord bot: bot user, application, guild count, enabled gateway intents, and the server version. With more than one bot configured, pass bot to pick which (list_servers shows the configured bots). Use run_setup_check for a full health check with fix instructions.

End-to-end health check of the discord-mcp setup: token presence and validity, privileged gateway intent toggles, Discord's growth thresholds (App Verification by servers, intent review by users), default guild membership, whether this install runs from npm's temporary npx cache, how destructive actions get confirmed in this app, and leftovers from before the 2.0 rename. Every failed check comes with instructions for fixing it. With more than one bot configured, pass bot to check a specific one. Run this first when anything misbehaves.

Structured snapshot of a server: identity, member counts, boost status, channel outline grouped by category, and role count. The natural first call when starting work on a server. The outline holds only channels the bot can see; hidden_from_bot says how many others exist when any do. A running pause on invites or DMs is reported too.

The channels in a server the bot can see, grouped by category, with type and topic. Filter by type: text, voice, forum, stage, announcement, category. Channels the bot lacks View Channel on are left out by Discord; hidden_from_bot says how many when any are.

All roles in a server, highest first, with how many members hold each, color (and gradient), icon, position, and a plain-language digest of their key permissions.

Recent messages from a channel as a digest: author, time, content, attachments, reactions, and resolved reply references. Returns oldest first. Use next_before to page further back. To look at a message's pictures, use get_message with include_images.

Search the server's message history through Discord's native search index. Covers every channel the bot can read, or one channel if you name it, and looks inside embeds and polls, not just plain text. Matching is whole-word full text, not substring, so search for words rather than fragments. Filter by author, by what a message carries (image, link, file, and so on), or by pinned state, and order by newest first or by relevance.

Find specific members by a name fragment, or list those holding a given role. For the whole roster use list_members; for one member's full profile use get_member; to turn a fuzzy name into an id use find. Name search uses Discord's member search; role filtering walks the member list and reports if it hit the paging cap.

One member in detail: identity, nickname, roles by name, join date, and timeout state. Accepts a user ID or a name.

Universal name resolver. Give it a name fragment and get ranked candidates across channels, roles, and members with their IDs. Use this when unsure what an entity is called or to grab an ID once and reuse it.

Send a message to a channel, optionally as a reply, with embeds, or as a Components V2 layout of text, sections, image galleries, separators and link buttons inside colored containers, and with up to 10 files fetched from public URLs. Components replace content and embeds rather than joining them, and the choice is permanent for that message; in a layout, a file shows only where a gallery or thumbnail points at it as attachment://. For a private message to one person use send_dm; to post under a custom name and avatar use send_webhook_message; to send later use schedule_message. Mentions are suppressed by default; raise the mentions mode only deliberately. Supports dry_run.

Forward a message from one channel into another, the way the Discord client's forward does: the original travels along as a quoted snapshot. Works across channels in the server. An optional note is posted as its own message just before the forward, since Discord does not allow text on the forward itself.

Create a text, voice, forum, stage, announcement, or category channel, optionally inside a category, and optionally private or read-only from the start. private_to, read_only and posting_roles compile to permission overwrites and are applied in the same call, so a private channel is one request rather than a create followed by set_channel_permissions. Use set_channel_permissions for anything finer. Voice and forum settings (bitrate, user limit, region, default reaction, sort, layout, required tags) can be set at creation too. Supports dry_run.

Create a role from a vetted preset (none, member, moderator, admin) and/or an explicit list of permission names. Administrator is never granted by a preset; it must be spelled out explicitly. Can start with a gradient or holographic color and an icon where the server has those features. Supports dry_run.

Give a member a role. Preflights the bot's role hierarchy so the failure mode is an explanation, not a 403. Supports dry_run. A role that would give the member moderator or admin powers (such as banning, kicking, or timing out members, deleting other people's messages, or managing the server, roles, or channels), or let them see channels hidden from them now, needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change. Other roles are given at once.

Delete one message. Safe to call directly: the first call deletes nothing and returns a preview plus a confirm_token, and the deletion only happens when the call is repeated with that token. Use this two-step flow to let the user approve through the conversation rather than telling them to delete things by hand in Discord. Supports dry_run.

Curated server blueprints to start from: vetted structures for common server kinds. Fetch one with get_reference_layout, adapt names and channels to the user's theme, then stage it with plan_server_build.

One reference layout in full: the blueprint plus the reasoning behind its structure. Adapt it rather than applying it verbatim; the user's theme and wording should win.

Validate a blueprint against the live server and stage an ordered build plan. Checks Discord limits, name collisions, role references, feature requirements, and the bot's permissions, and reports every problem at once. Changes nothing on Discord. Use it for any multi-step structure, even a small one: the plan shows the user every step before anything happens. By default existing channels and roles with matching names are reused as they are. With update_existing, existing items are changed to match the blueprint too: renames (items carrying an id from export_server_blueprint), permissions, colors, topics, slowmode, category moves, and who can see or post. An item changes only the settings it lists; list one empty to clear it. To delete roles, categories, or channels, list them in remove; leaving something out of a blueprint never deletes it. Each change shows before and after, each deletion what it loses, with risks flagged. A plan that changes or deletes runs only by its plan_id, exactly as shown, or not at all.

Execute a staged plan by plan_id, or pass a blueprint directly to build it additively. A plan that changes existing items runs exactly as staged or not at all: it is checked against the server again and refused if anything it would touch has changed since. Building goes in dependency order: roles, then categories, then channels, creating before changing. If a step fails, the run stops and the report says exactly what was created, changed, failed, and never attempted; plan again to finish. Afterwards the server is compared with the blueprint and anything that did not take effect is reported. A build that changes anything returns a change_id that undo_change reverses.

Edit a channel's name, topic, slowmode, NSFW flag, or category, a voice channel's bitrate, user limit, region, and video quality, how long its threads stay open, and a forum's default reaction, sort, layout, post slowmode, and whether posts need a tag. Only passed fields change. Pass category "none" to move a channel out of its category. Supports dry_run.

Delete a channel or category. Safe to call directly: the first call deletes nothing and returns a preview plus a confirm_token, and the deletion only happens when the call is repeated with that token. When the user asks to delete something, call this and relay the preview for their go-ahead instead of sending them to do it manually in Discord; the gate exists exactly so deletion can be approved through the conversation. Deleting a category leaves its channels in place, uncategorized.

Edit a role's name, color (solid, gradient, or holographic), icon, hoist, mentionable flag, or permissions. Passing preset and/or permissions replaces the role's permission set with the named bundle plus listed names. Only passed fields change. Supports dry_run. A permission change that would give the role moderator or admin powers (such as banning, kicking, or timing out members, deleting other people's messages, or managing the server, roles, or channels), or let it see channels it cannot see now, needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change.

Delete a role. Members holding it simply lose it; nothing else changes. Safe to call directly: the first call deletes nothing and returns a preview plus a confirm_token, and the deletion only happens when the call is repeated with that token. Prefer this gated flow over telling the user to delete the role manually.

Edit a message the bot itself sent, or one posted through one of the server's webhooks (that needs Manage Webhooks). Discord does not allow editing anyone else's messages, no matter the permission level. A message sent as a Components V2 layout stays one: edit it with components, never with content or embeds.

Pin a message in a channel. Needs the Pin Messages permission (split from Manage Messages in 2026). Channels hold at most 50 pins.

Unpin a message. The message itself is untouched.

Pinned messages in a channel, newest pin first.

Set the short status line shown on a voice channel, a note about what is happening in it right now, up to 500 characters. Pass an empty status to clear it. This is the live status, not the topic. Needs Set Voice Channel Status, Manage Channels, and Connect in that channel.

Time a member out so they cannot talk, react, or join voice, for up to 28 days. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token applies the timeout. Relay the preview for the user's go-ahead. The reason lands in the audit log.

Lift an active timeout from a member early. It puts someone a moderator silenced back in the conversation, so it needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change. A member who is not timed out is left alone, with nothing to confirm.

Remove a member from the server. They can rejoin with a new invite. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token performs the kick. Relay the preview for the user's go-ahead instead of doing nothing.

Ban a user from the server, optionally deleting their recent messages. Works on users who already left (pass their user ID). Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token performs the ban. Relay the preview for the user's go-ahead.

Lift a ban so the user can rejoin with an invite. The first call changes nothing and returns a preview (who it is and why they were banned) and a confirm_token; repeating the call with the token lifts the ban.

Ban up to 200 users at once by ID, for raid cleanup. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token performs the bans. Reports which bans succeeded and which failed.

Current bans with reasons, paged.

Discord's historical record of administrative actions: who did what, to what, when, and why. Use this to investigate what already happened; for activity as it happens use subscribe_events. Filter by action name (like channel_create, member_ban_add, message_delete) or by the acting user. Discord merges some actions repeated in quick succession (message deletes, member moves and disconnects, channel and role reordering) into one entry that keeps only the first reason.

Discord's raid-defense security actions for the whole server. Pause new invites, and pause DMs between members who are not friends, each for up to 24 hours, to lock the server down during a raid. Give a number of hours to pause, 0 to lift a pause, or omit a field to leave it unchanged. Called with neither field, it reports the current state, including any raid or DM spam Discord detected on its own. Pausing, or pausing for longer, happens at once. Lifting a pause that is running, or ending it sooner, needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change.

Add one or more reactions to a message in a single call. Takes unicode emoji directly or custom emoji by name.

Remove a reaction: the bot's own by default, or another user's (which needs Manage Messages).

Clear all reactions from a message, or all of one emoji. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token executes. Relay the preview for the user's go-ahead.

Who reacted to a message with a given emoji.

Post a native Discord poll: a question, two to ten answers, and a duration of up to 32 days.

Current tallies for a poll message. With include_voters, also who voted for each answer.

Close one of the bot's own polls early and finalize the results. Voting stops for good, since a poll cannot be reopened. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token ends the poll. A poll that has already closed is left alone.

Create an invite link for a channel. Defaults are deliberate: expires in 24 hours, unlimited uses. A never-expiring invite must be asked for explicitly with max_age_seconds 0. roles gives roles to whoever joins with it, and for_users limits it to particular people. An invite whose roles would give moderator or admin powers (such as banning, kicking, or timing out members, deleting other people's messages, or managing the server, roles, or channels), or open channels, needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change.

Active invites for the server or one channel.

Inspect an invite code: where it leads, how used it is, the roles it gives, and whether it is limited to particular people.

Revoke an invite link. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token revokes it.

Webhooks in the server or one channel. Tokens are never included.

Create an incoming webhook on a channel. Webhooks post with any display name and avatar, which is how messages 'as someone' work legitimately.

Rename a webhook, change its avatar, or move it to another channel.

Delete a webhook. Anything still posting through it stops working. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token deletes it.

Post through a webhook with an optional display name and avatar override, and up to 10 files fetched from public URLs. Mentions are suppressed.

Custom emojis in the server, with usage syntax.

Upload a custom emoji from an image URL. Discord's limit for emoji files is 256 KB; png, jpeg, gif, and webp work.

Rename a custom emoji.

Delete a custom emoji. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token deletes it.

Scheduled community events (the kind members RSVP to), with type, time, status, and interest counts. For pending scheduled messages see list_scheduled_messages; for live event subscriptions see list_event_subscriptions.

One scheduled event in detail.

Create a Discord scheduled community event that members see on the events list and can mark interest in: a voice, stage, or external (in-person or off-platform) event. This is not for sending a message later (use schedule_message) or watching live activity (use subscribe_events). Voice and stage events need a channel; external events need a location and an end time.

Edit a scheduled event's details, or move it through its lifecycle: status start makes it live, status end completes it. An ended event cannot be started again, so ending one needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change. Everything else happens at once.

Cancel and remove a scheduled event. Interested members lose the listing. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token cancels it.

Members who marked themselves interested in an event.

Watch one server live: start recording real-time activity as it happens (messages, joins and leaves, reactions, channel and role changes, bans, voice movement) into a buffer you then read with get_recent_events. Only the named server's events are recorded (the default server when none is named). Use this to observe what is going on now. It is not for scheduled community events (create_event) or timed messages (schedule_message). Available types: message_created, message_deleted, member_joined, member_left, reaction_added, reaction_removed, channel_created, channel_deleted, role_created, role_updated, role_deleted, ban_added, ban_removed, voice_state_changed.

Read and clear buffered events from a subscription, oldest first.

Active event subscriptions and their buffer sizes.

Stop recording and discard a subscription's buffer.

Start a thread in a text or announcement channel: standalone, branched from a message when message_id is given, or private (invite-only) when asked. For a post in a forum channel, use create_forum_post instead.

Active threads across the server or one channel. Archived threads come from a specific channel with include_archived.

One thread's settings, state, and counts.

Rename a thread, archive or unarchive it, lock or unlock it, or change its slowmode and auto-archive window.

Delete a thread and its messages. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token deletes it. Archiving is the reversible alternative.

Who is in a thread.

Pull a member into a thread. Adding someone to a private thread they cannot see now lets them read all of it, earlier messages included, so that needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token adds them.

Remove a member from a thread. Needs Manage Threads.

Start a post in a forum channel: a title, the opening message, optional tags from the forum's tag list, and up to 10 files fetched from public URLs.

Posts in a forum, filterable by tag, optionally archived too.

Add a reply inside a forum post: text, embeds, or both.

Edit a post's title or tags, pin or unpin it within the forum, lock or unlock replies, or archive it.

Delete a forum post and every reply in it. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token deletes it.

Add a tag to a forum's tag list. Moderated tags can only be applied by people with Manage Threads.

Rename a forum tag or change its moderated flag.

Remove a tag from a forum; posts carrying it simply lose it. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token removes it.

Server-side automatic moderation rules and what they do.

Create a server-side moderation rule that runs on Discord's own infrastructure: Discord-maintained preset word lists (slurs, profanity, sexual content), custom keyword filters (with optional regex), spam detection, mention-flood limits, or member_profile checks on usernames, nicknames, and bios (Community servers only). For slur or hate-speech filtering prefer trigger keyword_preset with the slurs preset: Discord maintains the word list, so none needs to be written. Actions: block the message, alert a channel, and/or time the sender out (timeout is not available on spam, keyword_preset, or member_profile rules). On member_profile rules block quarantines the member until they fix their profile.

Rename a rule, enable or disable it, or replace its keyword list. Turning a rule off, or a new list that leaves out keywords the rule has now, stops it catching what it caught, so that needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change. Renaming, turning a rule on, and adding keywords happen at once.

Delete an AutoMod rule; its protection stops immediately. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token deletes it. Turning it off with update_automod_rule is the reversible alternative.

Edit server settings: name, description, icon, banner, invite background, AFK behavior, system and rules channels, verification level, explicit media filter, and default notifications. Images come from public URLs. Only passed fields change. Descriptions need a Community server; the banner and invite background need boosts. A lower verification level, a weaker media filter, or turning Community off lowers the server's protection, so that needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change. Raising them, and every other setting, happens at once.

A server's preview: name, description, and approximate member counts. Works for servers the bot is in; other servers need to be discoverable.

Widget settings: enabled state and invite channel.

Enable or disable the widget, or point its invite channel. An enabled widget shows the server's name, who is online, and its voice channels to anyone on the web, and with an invite channel it lets anyone join. So turning it on, or pointing it at an invite channel while it is on, needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change. Turning it off or clearing the channel happens at once.

The Community welcome screen, when the server has one.

Edit the Community welcome screen: the description and up to five channel cards.

The new-member onboarding flow, when configured.

Configure the new-member onboarding flow on a Community server: prompts with options that grant channels and roles, the default channels every member sees, and the enabled state. Discord's app asks for at least seven default channels when configuring this by hand; the API has been observed to accept fewer. Members pick these options themselves, so offering a role that gives moderator or admin powers, or opens channels hidden from everyone, needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token saves it.

Installed integrations: bots, Twitch and YouTube links.

Remove an integration from the server. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token removes it.

Discord templates created from this server.

Snapshot this server's structure as a Discord template others can create servers from. One template per server.

Update a template to match the server's current structure.

Delete a server template; its share link stops working. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token deletes it.

Remove members inactive for a number of days who hold no roles. Needs Kick Members and Manage Server, or Administrator where the owner has made pruning admin-only. Safe to call directly: the first call counts who would go using Discord's own preview and returns a confirm_token; repeating the call with the token prunes for real.

Change the bot's status dot and custom status text. Needs the gateway connection this server keeps by default.

Custom stickers in the server.

Upload a custom sticker from an image URL. Discord requires png, apng, or gif at 320x320 pixels and up to 512 KB. Servers start with five sticker slots; boosts add more.

Rename a sticker or change its description and tags.

Delete a custom sticker. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token deletes it.

Custom soundboard sounds in the server.

Upload a soundboard sound from an audio URL: mp3 or ogg, up to 512 KB and 5.2 seconds. Servers start with eight sound slots; boosts add more.

Rename a soundboard sound or change its volume.

Delete a soundboard sound. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token deletes it.

Save a blueprint to the local store for reuse: apply it to other servers with execute_build_plan or track drift with diff_blueprint. Names are unique.

Saved blueprints in the local store.

One saved blueprint in full, by name or ID.

Delete a saved blueprint from the local store. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token deletes it. Servers built from it are untouched.

Snapshot a live server's structure into a blueprint: roles, categories, channels, and their visibility, with permission overwrites decompiled back into private_to and read_only where they fit and warnings where they do not. Each item carries its id, so editing the export and planning it with update_existing renames and changes those exact items. Optionally save the result straight to the store with save_as.

Turn a Discord server template link (discord.new/CODE or discord.com/template/CODE) into a blueprint: its roles, categories, channels, and who can see and post where. Nothing is built; plan the result with plan_server_build to build it on a server, after editing it if wanted. Optionally save it with save_as. The template's server settings (verification level, media filter, notifications) are listed for update_server, since blueprints do not carry them.

Compare a blueprint against the live server: what the blueprint expects but the server lacks (missing), what exists but differs (changed, with the fields), and what the server has that the blueprint never mentioned (extra, informational). Reads the blueprint as the whole truth, so a setting it leaves out counts as its default. The drift detector for config-as-code workflows. To act on it, plan_server_build applies changes with update_existing and deletes extras listed in remove.

Recent changes made through discord-mcp on a server, newest first: builds, and single creates, edits, and deletes of channels and roles, permission edits, roles given or taken, server settings edits. Each says what it did and whether it has been undone. The change_id is what undo_change takes.

Undo changes made through discord-mcp, from their records: builds, and any single create, edit, or delete of a channel or role, permission edit, role given or taken, server settings edit. Use this rather than redoing things by hand: it has an exact copy of what was there. It deletes what a change created, puts back what it changed, and recreates what it deleted. A setting goes back only if it still holds the value the change set; anything changed since stays and is reported. Recreated items get new ids, and a deleted channel's messages cannot come back. Pass change_id for one change, since (a time) to undo every change made from then on, such as everything today, or change_ids for several; they are undone newest first. With none, the latest change not yet undone. The first call changes nothing and returns every step plus a confirm_token; repeat with the token to run it. If a step fails (a rate limit, say), calling it again finishes the rest.

Fetch one message in full: author, content, timestamps, attachments, embeds, reactions, and any reply reference. With include_images, also returns the message's pictures so you can look at them: attachments, embed images, layout media, and what a forwarded message carries.

Send a direct message from the bot to a member who shares a server with it. Fails gracefully when the recipient has DMs closed. The message comes from the bot, never from a user account.

Delete many recent messages at once (2 to 100), optionally filtered by author or text. Discord cannot bulk delete messages older than 14 days. Safe to call directly: the first call returns how many it would remove, with a sample of them, plus a confirm_token; repeating the call with the token deletes them.

Publish a message in an announcement channel out to every server that follows it.

Post a text message to a channel at a later time, once or on a daily or weekly repeat. This sends an ordinary message; for a community event members can RSVP to, use create_event. This server sends it when the time comes. One limit worth knowing: delivery needs this server to be running at that moment, so always-on scheduling wants the hosted or Docker deployment rather than a laptop that sleeps. A message that came due during downtime is sent at the next start.

Pending timed messages waiting to send, soonest first. These are messages queued with schedule_message, not Discord community events (list_events).

Cancel a pending scheduled message by its id. The queued text is gone for good, and a repeat stops, so the first call returns a preview and a confirm_token; repeating the call with the token cancels it.

Edit a member's nickname or voice state. Voice changes (server mute, server deafen, move to another voice channel) only apply while the member is connected to voice. Role changes go through assign_role and remove_role. Moving someone into a voice channel they cannot join themselves lets them hear it, and lifting a server mute or deafen undoes what a moderator did, so those need confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change. Everything else, muting and deafening included, happens at once.

Remove a member from whatever voice channel they are in. They stay in the server; only the voice connection ends.

Who is currently in a voice or stage channel, with their mute and deafen state. This reads the live voice presence the gateway tracks, so it reflects the time since this server connected.

Take a role away from a member. Preflights the bot's role hierarchy so a failure is an explanation, not a 403. Usually done at once. A role can also hold someone back (one that hides channels from whoever has it, such as a quarantine role); taking that away lets them in, so it needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change.

The effective permissions a member has, server-wide or in a specific channel once role and overwrite resolution is applied, in plain language. Uses Discord's own permission check when Discord gives one, which includes its implicit rules; source says which.

The permission overwrites on a channel, resolved into plain language per role and member.

Set a permission overwrite on a channel for one role or member: which permissions are explicitly allowed and which are denied. It replaces that role's or member's whole overwrite on the channel, so list every permission it should keep, not only the new one; get_channel_permissions shows the current one. Permission names like manage_messages or send_messages. On a category, Discord also makes the same change in every channel inside whose permissions match the category's exactly (synced), as the Discord app does; the result names them. To keep such a channel as it is, change that channel first, which stops it matching. get_channel_permissions says whether a channel is synced. A change that would let someone see a channel they cannot see now, or give them moderator or admin powers (such as banning, kicking, or timing out members, deleting other people's messages, or managing the server, roles, or channels) there, needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change.

Remove a role's or member's permission overwrite from a channel, so their permissions there come from their roles and the other overwrites. On a category, Discord also makes the same change in every channel inside whose permissions match the category's exactly (synced), as the Discord app does; the result names them. To keep such a channel as it is, change that channel first, which stops it matching. get_channel_permissions says whether a channel is synced. Removing one that keeps someone out (a private channel's denial for @everyone, say) needs confirming, as does one whose removal gives moderator or admin powers (such as banning, kicking, or timing out members, deleting other people's messages, or managing the server, roles, or channels): the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change.

Lock a channel by denying everyone the ability to send messages and start threads. Roles and members with their own permission to post on the channel keep it, so moderators set up that way keep access; the result names them. Reverse with unlock_channel, which puts back exactly what the lock changed.

Reverse lock_channel: lift the denials the lock added and put back what it took off, leaving alone anything that was denied before the lock. A channel that was read-only before it was locked stays read-only. On a channel no lock is on record for, it would remove everyone's denial on sending, which may be there on purpose, so that needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change.

Answer whether an actor (the bot, or a member) has a given permission, server-wide or in a channel, and explain the result through the role and overwrite chain. The answer is Discord's own permission check when Discord gives one, so it includes the implicit rules (a missing View Channel cancels what depends on it).

Full detail for one channel: type, topic, category, slowmode, NSFW flag, and a count of its permission overwrites.

Copy a channel's settings and permission overwrites into a new channel in the same category.

Copy a role's permissions, color, and settings into a new role.

Move channels to new positions, and optionally into a different category, in one call.

Move roles to new hierarchy positions in one call. Higher positions sit higher in the list and outrank lower ones. Moving a role that can ban, kick, time out, rename, or change roles above a role it was below lets its holders do that to the people with the other role, so that needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change.

Subscribe a channel to an announcement channel, so crossposted messages from the source appear in the target.

Add or remove a role across every member matching a filter. Safe to call directly: the first call returns the affected count and a confirm_token; repeating the call with the token applies the change. Walks up to 3000 members and reports if it hits the cap.

Stage channels that currently have a live stage running.

Open a live stage on a stage channel with a topic. Members can then be invited to speak.

Change the topic of a live stage.

End the live stage on a stage channel. It ends for everyone listening, so the first call returns a preview and a confirm_token; repeating the call with the token ends it.

Every server your bots are in, each labeled with which bot reaches it, with approximate member counts. A server more than one of your bots is in appears once per bot, with handles_server marking the one that tools run as there. Use get_server_overview for one server's full detail.

A paged roster of server members. Pass after with the last id to continue. For finding specific people, search_members is better.

The members who currently hold a given role.

The slash commands this bot's application has registered. Omit guild for the global set, or pass a guild for that server's set. Guild commands and global commands are separate lists; a name can exist in both.

Register a slash command, or update it in place if the name is already taken. Pass a guild while iterating: guild commands appear immediately, while global commands can take up to an hour to show up everywhere and are rate limited per day. Subcommands and subcommand groups are not supported here.

Change a registered command's description or options. Anything not passed is left as it is. Replacing options replaces the whole list, so send every option you want to keep.

Unregister a slash command so it no longer appears for users. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token removes it.

Change how the bot looks. In one server (the default): its nickname, avatar, banner, and bio there, shown only in that server, so one bot can look different in each community. Everywhere (scope everywhere): its username, avatar, and banner, for every server it is in. Images come from public URLs; none removes a server-only one, so the global one shows again. A replaced avatar or banner is saved to the data folder first, since Discord does not keep it. Discord limits username changes to about two an hour.

Make the bot leave a server. It can only come back through a new invite from someone with Manage Server, and its own role there is deleted. Always previews first and asks for confirmation. The server must be named: this never falls back to the default one. When two of your bots are in the server, bot says which one leaves.

Review a server's security the way an attacker would look at it, and list findings from high to low with a fix for each: powers held by everyone or by everyday roles, roles that can raise their own power through Manage Roles, bots with Administrator, powerful roles offered in onboarding or handed out by invites, 2FA for moderators, verification, the media filter, AutoMod, webhooks, and permanent invites. Read only; it changes nothing.

Who can see and use a channel: @everyone, each role that can see it (with how many members hold it, whether they can post or join, and any powers there), members with their own overwrite, and the owner. With include_members, also checks every member one by one, which is exact where roles combine. Read only.

What one member can reach across the server: their server-wide powers, every channel they can see (and whether they can post or join there), channels where they hold extra powers, and how many channels are closed to them. Read only. For why one permission is or is not there, use explain_permissions.

What happened in a server recently, in one call: every channel and thread with new messages since a time (default the last 24 hours), busiest first, with who talked, the messages themselves (trimmed), @everyone pings, and, with mentions_of, the messages that mention a member. Quiet channels are skipped without being read. Read only. For one channel's full history use read_messages.