Skip to main content
Glama
OrygnsCode

Omnicord - Discord server management MCP for AI agents

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DISCORD_TOKENNoThe bot token. Required for anything real; the server boots without it and the diagnostics explain what to fix.
OMNICORD_PORTNoHTTP port, default 3414.3414
OMNICORD_GUILDNoOptional default server ID so tools can omit the guild parameter.
OMNICORD_GATEWAYNoDefault on when a token is set: the bot shows as online and real time event subscriptions work. Set to off for REST only operation.on
OMNICORD_DATA_DIRNoWhere saved blueprints and scheduled messages live. Default: .omnicord next to package.json for a source checkout, .omnicord in your user folder for an installed copy..omnicord
OMNICORD_HTTP_HOSTNoHTTP bind address, default 127.0.0.1.127.0.0.1
OMNICORD_SAFE_MODENoDefault on. Destructive tools preview first and require a confirm token; set to false only for trusted automation.true
OMNICORD_HTTP_TOKENNoBearer token for HTTP mode. Required to bind beyond localhost.
OMNICORD_HTTP_ORIGINSNoComma separated browser origins allowed to call the HTTP endpoint. Empty means none.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_rate_limit_statusA

How rate limiting has been going: how many times Discord asked Omnicord 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.

get_bot_infoA

Identity and status of a connected Discord bot: bot user, application, guild count, enabled gateway intents, and the Omnicord 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.

run_setup_checkA

End-to-end health check of the Omnicord setup: token presence and validity, privileged gateway intent toggles, guild count against Discord's verification thresholds, and default guild membership. 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.

get_server_overviewA

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.

list_channelsA

All channels in a server grouped by category, with type and topic. Filter by type: text, voice, forum, stage, announcement, category.

list_rolesA

All roles in a server, highest first, with color, position, and a plain-language digest of their key permissions.

read_messagesB

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.

search_messagesA

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.

search_membersA

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.

get_memberA

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

findA

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_messageA

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. Components replace content and embeds rather than joining them, and the choice is permanent for that message. 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_messageA

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_channelA

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. Supports dry_run.

create_roleA

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. Supports dry_run.

assign_roleA

Give a member a role. Preflights the bot's role hierarchy so the failure mode is an explanation, not a 403. Supports dry_run.

delete_messageA

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.

list_reference_layoutsA

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.

get_reference_layoutA

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.

plan_server_buildA

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. Compose the blueprint from the user's request, optionally starting from a reference layout. Existing channels and roles with matching names are reused, never duplicated.

execute_build_planA

Execute a staged plan by plan_id, or pass a blueprint directly. Either way the blueprint is re-validated against the live server at this moment, then built in dependency order: roles, then categories, then channels, with private_to and read_only compiled into permission overwrites at creation. Strictly additive: existing entities are reused, nothing is deleted or modified. If a step fails, the run stops and the report says exactly what was created, what failed, and what was never attempted. Re-running after a fix resumes naturally because finished work is reused.

update_channelA

Edit a channel's name, topic, slowmode, NSFW flag, or category. Only passed fields change. Pass category "none" to move a channel out of its category. Supports dry_run.

delete_channelA

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.

update_roleA

Edit a role's name, color, 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.

delete_roleA

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_messageA

Edit a message the bot itself sent. 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_messageA

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

unpin_messageA

Unpin a message. The message itself is untouched.

list_pinned_messagesA

Pinned messages in a channel, newest pin first.

set_voice_channel_statusA

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.

timeout_memberA

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.

remove_timeoutA

Lift an active timeout from a member early.

kick_memberA

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_memberA

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.

unban_memberA

Lift a ban so the user can rejoin with an invite.

bulk_banA

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.

list_bansA

Current bans with reasons, paged.

get_audit_logA

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.

set_incident_actionsA

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.

add_reactionsA

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

remove_reactionA

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

clear_reactionsA

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.

get_reactionsA

Who reacted to a message with a given emoji.

create_pollA

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

get_poll_resultsB

Current tallies for a poll message.

end_pollA

Close one of the bot's own polls early and finalize the results.

create_inviteA

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.

list_invitesA

Active invites for the server or one channel.

get_inviteA

Inspect an invite code: where it leads and how used it is.

delete_inviteA

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.

list_webhooksA

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

create_webhookA

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

update_webhookA

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

delete_webhookA

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.

send_webhook_messageA

Post through a webhook with an optional display name and avatar override. Mentions are suppressed.

list_emojisB

Custom emojis in the server, with usage syntax.

create_emojiA

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

update_emojiA

Rename a custom emoji.

delete_emojiA

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.

list_eventsA

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.

get_eventA

One scheduled event in detail.

create_eventA

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.

update_eventA

Edit a scheduled event's details, or move it through its lifecycle: status start makes it live, status end completes it.

cancel_eventA

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.

get_event_attendeesC

Members who marked themselves interested in an event.

subscribe_eventsA

Watch the 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. 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.

get_recent_eventsA

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

list_event_subscriptionsB

Active event subscriptions and their buffer sizes.

unsubscribe_eventsB

Stop recording and discard a subscription's buffer.

create_threadA

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.

list_threadsA

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

get_threadB

One thread's settings, state, and counts.

update_threadA

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

delete_threadA

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.

list_thread_membersC

Who is in a thread.

add_thread_memberB

Pull a member into a thread.

remove_thread_memberA

Remove a member from a thread. Needs Manage Threads.

create_forum_postA

Start a post in a forum channel: a title, the opening message, and optional tags from the forum's tag list.

list_forum_postsA

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

reply_to_forum_postB

Add a reply inside a forum post.

update_forum_postA

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

delete_forum_postA

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.

create_forum_tagA

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

update_forum_tagA

Rename a forum tag or change its moderated flag.

delete_forum_tagA

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.

list_automod_rulesC

Server-side automatic moderation rules and what they do.

create_automod_ruleA

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.

update_automod_ruleA

Rename a rule, enable or disable it, or replace its keyword list.

delete_automod_ruleA

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. Disabling is the reversible alternative.

update_serverA

Edit server settings: name, description, AFK behavior, system and rules channels, verification level. Only passed fields change. Descriptions need a Community server.

get_server_previewA

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

get_server_widgetA

Widget settings: enabled state and invite channel.

update_server_widgetA

Enable or disable the widget, or point its invite channel.

get_welcome_screenB

The Community welcome screen, when the server has one.

update_welcome_screenA

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

get_onboardingC

The new-member onboarding flow, when configured.

update_onboardingA

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.

list_integrationsA

Installed integrations: bots, Twitch and YouTube links.

delete_integrationA

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.

list_server_templatesB

Discord templates created from this server.

create_server_templateA

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

sync_server_templateA

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

delete_server_templateA

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.

prune_membersA

Remove members inactive for a number of days who hold no roles. 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.

set_bot_presenceA

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

list_stickersC

Custom stickers in the server.

create_stickerA

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.

update_stickerA

Rename a sticker or change its description and tags.

delete_stickerA

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.

list_soundboard_soundsC

Custom soundboard sounds in the server.

create_soundboard_soundA

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.

update_soundboard_soundA

Rename a soundboard sound or change its volume.

delete_soundboard_soundA

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_blueprintA

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.

list_blueprintsB

Saved blueprints in the local store.

get_blueprintA

One saved blueprint in full, by name or ID.

delete_blueprintA

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.

export_server_blueprintA

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. Optionally save the result straight to the store with save_as.

diff_blueprintA

Compare a saved 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). The drift detector for config-as-code workflows.

get_messageA

Fetch one message in full: author, content, timestamps, attachments, embeds, reactions, and any reply reference.

send_dmA

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.

bulk_delete_messagesA

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 the exact list it would remove plus a confirm_token; repeating the call with the token deletes them.

crosspost_messageA

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

schedule_messageA

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. Omnicord sends it when the time comes. One limit worth knowing: delivery needs the Omnicord process 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.

list_scheduled_messagesA

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

cancel_scheduled_messageA

Cancel a pending scheduled message by its id.

update_memberA

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.

disconnect_memberA

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

list_voice_membersA

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 Omnicord connected.

remove_roleA

Take a role away from a member. Preflights the bot's role hierarchy so a failure is an explanation, not a 403.

get_member_permissionsA

The effective permissions a member has, server-wide or in a specific channel once role and overwrite resolution is applied, in plain language.

get_channel_permissionsA

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

set_channel_permissionsA

Set a permission overwrite on a channel for one role or member: which permissions are explicitly allowed and which are denied. Permission names like manage_messages or send_messages.

clear_channel_permissionsA

Remove a role's or member's permission overwrite from a channel, restoring inheritance from the category and roles.

lock_channelA

Lock a channel by denying everyone the ability to send messages. Existing role overwrites that allow posting still apply, so moderators keep access. Reverse with unlock_channel.

unlock_channelA

Reverse lock_channel by removing the send-message denial from the everyone overwrite.

explain_permissionsA

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 preflight engine, made directly askable.

get_channelA

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

clone_channelA

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

clone_roleA

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

reorder_channelsA

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

reorder_rolesA

Move roles to new hierarchy positions in one call. Higher positions sit higher in the list and outrank lower ones.

follow_announcement_channelA

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

bulk_update_rolesA

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.

list_stagesB

Stage channels that currently have a live stage running.

start_stageA

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

update_stageA

Change the topic of a live stage.

end_stageB

End the live stage on a stage channel.

list_serversA

Every server your bots are in, each labeled with which bot reaches it, with approximate member counts. When more than one bot is configured this is the map for choosing which one acts. Use get_server_overview for one server's full detail.

list_membersA

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

get_role_membersC

The members who currently hold a given role.

list_app_commandsA

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_app_commandA

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.

update_app_commandA

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.

delete_app_commandA

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 155 tools

Disambiguation2/5

With 155 tools, many have overlapping purposes—e.g., clone_channel vs export_server_blueprint, create_event vs schedule_message vs subscribe_events, and multiple search/list functions. Descriptions clarify distinctions, but the sheer breadth makes misselection likely without careful reading.

Naming Consistency5/5

Consistent snake_case verb_noun pattern throughout (get_message, create_channel, delete_role, etc.). No deviations or mixed conventions.

Tool Count1/5

155 tools is far too many for a single MCP server, even one covering Discord's extensive API. This creates cognitive overload and violates the principle of well-scoped tool sets.

Completeness5/5

The tool surface is remarkably complete, covering nearly every Discord management operation: channels, roles, members, messages, events, automod, integrations, templates, stages, forums, and more. No obvious gaps.

Maintenance

ActivityMaintained
ResponsivenessNo issues