Omnicord

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

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.

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

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

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.

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

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.

Snapshot this server's structure as a Discord template others can create servers from. One template per 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.

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.

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.

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

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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

End the live stage on a stage channel.

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.

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.

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.

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.

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

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.

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.

One saved blueprint in full, by name or ID.

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.

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

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

One scheduled event in detail.

Members who marked themselves interested in an event.

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

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

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

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

The new-member onboarding flow, when configured.

Current tallies for a poll message.

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.

Who reacted to a message with a given emoji.

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

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.

The members who currently hold a given role.

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.

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.

One thread's settings, state, and counts.

The Community welcome screen, when the server has one.

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.

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.

Server-side automatic moderation rules and what they do.

Current bans with reasons, paged.

Saved blueprints in the local store.

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

Custom emojis in the server, with usage syntax.

Active event subscriptions and their buffer sizes.

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.

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

Installed integrations: bots, Twitch and YouTube links.

Active invites for the server or one channel.

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

Pinned messages in a channel, newest pin first.

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.

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

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

Discord templates created from this server.

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.

Custom soundboard sounds in the server.

Stage channels that currently have a live stage running.

Custom stickers in the server.

Who is in a thread.

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

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.

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

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.

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

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.

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.

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.

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.

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

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

Remove a member from a thread. Needs Manage Threads.

Lift an active timeout from a member early.

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.

Add a reply inside a forum post.

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

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.

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.

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.

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.

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.

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.

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

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

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.

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.

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.

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

Description is built at runtime.

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

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 a ban so the user can rejoin with an invite.

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

Unpin a message. The message itself is untouched.

Stop recording and discard a subscription's buffer.

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.

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

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.

Rename a custom emoji.

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

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

Rename a forum tag or change its moderated flag.

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.

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.

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.

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

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

Rename a soundboard sound or change its volume.

Change the topic of a live stage.

Rename a sticker or change its description and tags.

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

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

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