discord_add_multiple_reactions
Adds multiple emoji reactions to a Discord message at once
Run a Discord bot from an assistant — post and read messages, manage channels and categories, run forum posts, react, and drive webhooks.
LABSCO SUMMARY
The webhook tools are the piece worth noting: alongside sending as the bot, the server can create and drive channel webhooks, so an assistant can wire up a posting endpoint and use it in the same session. Forum handling is unusually complete here — creating posts with tags, reading their messages, and replying — rather than treating a forum as just another text channel.
A Discord bot server exposing 22 tools across messaging, channel and category management, forum posts, reactions and webhooks, driven by your own bot token.
A Discord bot token, held in DISCORD_TOKEN or passed with --config. Node, run over stdio with npx; a streamable HTTP transport is available via --transport http --port, which is what the Docker image runs by default.
One command plus a key — npx mcp-discord --config ${DISCORD_TOKEN}, then supply credentials
USE CASES
Log the bot in, send a message to a text channel, and read back the recent conversation to see what came before or after.
Create a category, add text channels under it with topics, and reposition or remove pieces as the layout changes.
Find the forum channels, open a tagged post, read its messages, and reply to keep the discussion going.
Create a webhook on a channel, send a message through it, and edit or remove it later — so posts can arrive without the bot being the sender.
Add one emoji or several at once to a message, and pull a reaction back off when it no longer applies.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
discord_add_multiple_reactionsAdds multiple emoji reactions to a Discord message at once
discord_add_reactionAdds an emoji reaction to a specific Discord message
discord_create_categoryCreates a new category in a Discord server.
discord_create_forum_postCreates a new post in a Discord forum channel with optional tags
discord_create_text_channelCreates a new text channel in a Discord server with an optional topic
discord_create_webhookCreates a new webhook for a Discord channel
discord_delete_categoryDeletes a Discord category by ID.
discord_delete_channelDeletes a Discord channel with an optional reason
discord_delete_forum_postDeletes a forum post or thread with an optional reason
discord_delete_messageDeletes a specific message from a Discord text channel
discord_delete_webhookDeletes an existing webhook for a Discord channel
discord_edit_categoryEdits an existing Discord category (name and position).
discord_edit_webhookEdits an existing webhook for a Discord channel
discord_get_forum_channelsLists all forum channels in a specified Discord server (guild)
discord_get_forum_postRetrieves details about a forum post including its messages
discord_get_server_infoRetrieves detailed information about a Discord server including channels and member count
discord_loginLogs in to Discord using the configured token
discord_read_messagesRetrieves messages from a Discord text channel with a configurable limit
discord_remove_reactionRemoves a specific emoji reaction from a Discord message
discord_reply_to_forumAdds a reply to an existing forum post or thread
discord_sendSends a message to a specified Discord text channel
discord_send_webhook_messageSends a message to a Discord channel using a webhook
BEFORE YOU INSTALL
22 tools when we connected; the project documents 42. The missing ones include role, member and channel-permission management, forum and voice channel creation, and message search and editing.
All 4 documented clients run the server on your machine.
INSTALLATION
git clone https://github.com/barryyip0625/mcp-discord.git
cd mcp-discord
npm install
npm run buildnpx mcp-discord --config ${DISCORD_TOKEN}{
"mcpServers": {
"discord": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_DISCORD>/build/index.js"
],
"env": {
"DISCORD_TOKEN": "<YOUR_DISCORD_TOKEN>"
}
}
}
}<YOUR_PATH_TO_MCP_DISCORD> is the full path of your clone (npm run build in the steps above creates build/index.js there), and <YOUR_DISCORD_TOKEN> is your bot's token from the Discord Developer Portal.
{
"mcpServers": {
"discord": {
"command": "npx",
"args": [
"-y",
"mcp-discord"
],
"env": {
"DISCORD_TOKEN": "<YOUR_DISCORD_TOKEN>"
}
}
}
}This runs the published mcp-discord package, so it needs no clone or build. <YOUR_DISCORD_TOKEN> is your bot's token from the Discord Developer Portal.