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.
- discord_login connects the configured bot, and discord_get_server_info reads a guild's channels and member count
- Messages handled directly — discord_send posts to a text channel, discord_read_messages pulls recent messages up to a limit, and discord_delete_message removes one
- Channels and categories built and torn down: discord_create_text_channel with an optional topic, discord_delete_channel with a reason, and discord_create_category, discord_edit_category (name and position) and discord_delete_category
- Forums as a first-class surface — discord_get_forum_channels lists them, discord_create_forum_post creates a post with optional tags, discord_get_forum_post reads it with its messages, discord_reply_to_forum adds a reply, and discord_delete_forum_post removes a thread
- Reactions one at a time or in bulk: discord_add_reaction, discord_add_multiple_reactions and discord_remove_reaction
- Webhooks managed end to end — discord_create_webhook, discord_send_webhook_message, discord_edit_webhook and discord_delete_webhook — so a channel can receive posts without the bot itself sending them
A Discord bot token, held in DISCORD_TOKEN or passed with --config. Node, run over stdio as npx mcp-discord --config <token>; 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