discord-mcp

The prompts are examples: say it your way and the assistant picks the tools. The tools listed under each prompt come from their descriptions, not from a recorded session. Most clients ask before each write unless you allow it; check how yours is set.

Catch up on a channel and post a recap

You were away. You want to know what happened in a busy channel, then share a short recap with the team.

  1. What happened in #support since yesterday morning? Group it by topic.

    Finds the channel by name, then reads its messages from that point on. Each call returns up to 100 messages, so the assistant pages forward on a busy channel.

    Tools: discord_find_channel_by_name (read-only)discord_read_messages (read-only)

  2. Which of these questions got no answer?

    Works from the messages it already read. If a thread holds the answer, it lists the channel's threads and reads them too.

    Tools: discord_list_channel_threads (read-only)

  3. Post the recap in #team as an embed, then pin it.

    Sends one embed with a title and a field per topic, then pins the new message.

    Tools: discord_send_embed (write)discord_pin_message (write)

Toolsets to load

Environment
DISCORD_MCP_TOOLSETS=discovery,messages

25 tools, about 10.4k tokens of context. Discovery comes along for the server and channel IDs.

Safety

  • With read-only mode on, steps 1 and 2 still run; the others need write tools.
  • Message bodies come back empty when Message Content is off in the Developer Portal. See Troubleshooting.

Stop a raid without guessing

New accounts flood #general with the same link. You want the spam gone and the accounts out, and you want to see each mass action before it runs.

  1. Read the last 50 messages in #general. Which authors posted the same link?

    Reads the channel. Every message carries its author_id, so the assistant can group the spam by account without a member search.

    Tools: discord_find_channel_by_name (read-only)discord_read_messages (read-only)

  2. Time out those accounts for one hour while we look.

    Times out each member. A timeout is undone with a duration of 0, so this step is easy to take back.

    Tools: discord_timeout_member (write)

  3. Delete the last 30 messages in #general. Show me the preview first.

    Runs a dry run that reports how many messages it would delete, then waits. It deletes only when called again with dry_run: false. It removes the most recent messages from every author, not only the spam.

    Tools: discord_bulk_delete_messages (destructive)

  4. Ban the accounts that only posted spam. List them before you ban anyone.

    The dry run returns the user IDs it would send to Discord. After your go, the real call returns which bans succeeded and which failed.

    Tools: discord_bulk_ban (destructive)

  5. Show me the audit log for the last hour.

    Reads who did what: your bans and timeouts, and anything another moderator did meanwhile.

    Tools: discord_get_audit_log (read-only)

Toolsets to load

Environment
DISCORD_MCP_TOOLSETS=discovery,messages,members,moderation

37 tools, about 14.4k tokens of context. Discovery comes along for the server and channel IDs.

Safety

  • discord_bulk_delete_messages (destructive) and discord_bulk_ban (destructive) run as a dry run by default: they report what would happen and change nothing until called again with dry_run: false.
  • With read-only mode on, steps 1 and 5 still run; the others need write tools.
  • The bot can only time out, kick or ban members whose highest role sits below its own. Discord refuses to time out the server owner or a member with Administrator.
  • Bulk delete skips messages older than 14 days: Discord does not allow it.

Run a community event

You host a monthly community call. You want the event created, announced with a link, and a headcount on the day.

  1. Create an event called Community call next Friday at 8 PM in the Town hall voice channel.

    Finds the voice channel, then creates the event. A voice or stage event needs its channel; an external event needs a location and an end time instead.

    Tools: discord_find_channel_by_name (read-only)discord_create_scheduled_event (write)

  2. Make an invite to the event and announce it in #announcements.

    Creates an invite that opens the event, then posts the announcement with the link.

    Tools: discord_create_event_invite (write)discord_send_embed (write)

  3. Publish the announcement to the servers that follow #announcements.

    Crossposts the message. This works only in an announcement channel, once per message.

    Tools: discord_crosspost_message (write)

  4. How many people are interested? Move the start to 8:30 PM.

    Lists the interested users, then changes only the start time of the event.

    Tools: discord_get_event_subscribers (read-only)discord_edit_scheduled_event (write)

Toolsets to load

Environment
DISCORD_MCP_TOOLSETS=discovery,messages,scheduled_events

32 tools, about 13.4k tokens of context. Discovery comes along for the server and channel IDs.

Safety

  • Every step writes, so it needs read-only mode off.
  • Creating an event needs the Create Events permission. Manage Events alone no longer suffices.

Restructure channels and roles in one pass

Your server grew without a plan. You want new categories, a staff area, a Helper role and the right permissions, reviewed once and then applied together.

  1. Look at my channels, roles and permissions. Propose a layout with an Events category, a private Staff category and a Helper role. Do not change anything yet.

    Reads the current structure and replies with a plan: what it would create, move and allow, in order. Nothing changes on Discord in this step.

    Tools: discord_list_channels (read-only)discord_list_roles (read-only)discord_audit_permissions (read-only)

  2. Apply the plan.

    Creates the role and the categories, moves the channels, and puts the role where the plan says. For the private category it grants the bot View Channel before it denies @everyone, then syncs the channels inside with their category.

    Tools: discord_create_role (write)discord_create_channel (write)discord_move_channel (write)discord_set_member_permission (write)discord_set_role_permission (write)discord_lock_channel_permissions (write)discord_set_role_position (write)

  3. Check that Helpers can see #help but not the Staff category.

    Reads the overwrites on the channels it changed and compares them with the plan.

    Tools: discord_get_channel_permissions (read-only)

  4. Delete the old #events-old channel.

    Runs a dry run first and names the channel it would delete. It deletes only when called again with dry_run: false.

    Tools: discord_delete_channel (destructive)

Toolsets to load

Environment
DISCORD_MCP_TOOLSETS=discovery,channels,permissions,roles

27 tools, about 7.4k tokens of context. Discovery comes along for the server and channel IDs.

Safety

  • discord_delete_channel (destructive) runs as a dry run by default: it reports what would happen and changes nothing until called again with dry_run: false.
  • With read-only mode on, steps 1 and 3 still run; the others need write tools.
  • For the steps with no dry run, the preview is the plan in the first step, and your client's prompt before each write, if it asks.
  • Deny @everyone View Channel only after the bot has its own allow: otherwise the bot loses sight of the channel. Only Administrator ignores channel overwrites.
  • The bot can only edit, assign or move roles below its own highest role. New roles are placed below it.

Set up a support forum with tags

Questions get lost in a chat channel. You want a forum where each question is a post, tagged by type, and closed when solved.

  1. Create a forum called help in the Support category.

    Finds the category, then creates the forum channel in it.

    Tools: discord_find_channel_by_name (read-only)discord_create_forum_channel (write)

  2. Give it the tags Bug, Question, Feature request and Solved. Only moderators can apply Solved.

    Sets the forum's tags. A moderated tag can only be applied by members with Manage Threads.

    Tools: discord_set_forum_tags (destructive)

  3. Open a first post that explains how to ask a good question.

    Creates the post with its title and starter message.

    Tools: discord_create_forum_post (write)

  4. List the posts tagged Bug. Mark the fixed ones Solved and archive them.

    Lists the forum's posts, reads the ones in question, then updates their tags and archives them. Archiving closes a post without deleting it.

    Tools: discord_get_forum_tags (read-only)discord_list_forum_threads (read-only)discord_get_forum_post (read-only)discord_update_forum_post (write)

Toolsets to load

Environment
DISCORD_MCP_TOOLSETS=discovery,forums

14 tools, about 4.4k tokens of context. Discovery comes along for the server and channel IDs.

Safety

Post notifications through a webhook

Release notes and alerts should arrive in #releases under their own name and avatar, as tidy embeds.

  1. Create a webhook named Release notes in #releases.

    Creates the webhook and returns its ID and token.

    Tools: discord_find_channel_by_name (read-only)discord_create_webhook (write)

  2. Post the notes for version 2.0 through it as an embed with a field per change.

    Sends the message through the webhook. The token authorizes the send, so the bot needs no permission in the channel for it.

    Tools: discord_send_webhook_message (write)

  3. Fix the typo in the second field of that message.

    Edits the message it sent, through the same webhook.

    Tools: discord_edit_webhook_message (write)

Toolsets to load

Environment
DISCORD_MCP_TOOLSETS=discovery,webhooks

12 tools, about 4.2k tokens of context. Discovery comes along for the server and channel IDs.

Safety

  • Every step writes, so it needs read-only mode off.
  • A webhook token lets anyone post through it, with or without this server. Keep it out of shared chats and repositories. Delete the webhook to revoke the token.
  • discord_list_webhooks (read-only) returns tokens, even in read-only mode. Leave the webhooks toolset out when you do not need it.

Audit who can do what

Before you open the server to more people, you want to know which channels are restricted, which roles hold strong permissions, and who changed them lately.

  1. Audit the permissions of my server. Which channels deny @everyone, and which roles have Administrator or Manage Server?

    Builds a report of every channel overwrite, with role and member names, and lists the roles with their permissions.

    Tools: discord_audit_permissions (read-only)discord_list_roles (read-only)

  2. Who holds the Moderator role? What can Alex do on the server?

    Lists the role's members, then one member's roles and server-wide permissions. Those come from roles only: channel overwrites are not applied.

    Tools: discord_get_role_members (read-only)discord_search_members (read-only)discord_get_member_info (read-only)

  3. Who changed roles or channels this week?

    Reads the audit log, filtered by action type when you ask for one.

    Tools: discord_get_audit_log (read-only)

Toolsets to load

Environment
DISCORD_MCP_TOOLSETS=discovery,permissions,members,roles,moderation

31 tools, about 9.6k tokens of context. Discovery comes along for the server and channel IDs.

Safety

  • Every step only reads, so the recipe works with read-only mode on.
  • Channels the bot cannot view are left out of the audit and counted in hiddenChannels. Grant the bot View Channel on them to include them.