MCP Discord Bot Server
Related Servers
Alternatives to MCP Discord Bot Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables Claude or any MCP client to operate a Discord bot through 35 tools, covering reading channels, searching history, posting and replying, managing channels, threads and roles, moderating members, and reading the audit log. It runs locally as a stateless subprocess, making plain HTTPS calls to Discord's REST API with no gateway connection.35MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to send and read messages in Discord channels, manage servers, channels, and roles via Discord's API.12 npm2MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to send and read messages in Discord channels through the Discord API, with server and channel discovery.12 npmMIT
- AlicenseNot gradedqualityFmaintenanceMCP server that gives AI agents first-class access to Discord, enabling discovery, messaging, channel management, moderation, and arbitrary REST calls through typed, consent-aware tools.6 npm3MIT
- FlicenseNot gradedqualityDmaintenanceEnables LLMs to read messages, discover channels, send messages, and monitor Discord communities using the Discord HTTP API.-
- AlicenseNot gradedqualityAmaintenanceExposes the full Discord API to LLM agents so they can send and manage rich messages, channels, threads, members, roles, moderation, AutoMod, webhooks, and interactive components. Acts as a drop-in replacement for the legacy Java/Spring implementation, keeping all 75 original tools while adding embeds, polls, files, server configuration, and restart-safe role menus.32 npmMIT
TDQS
Scored across 15 tools
Each tool targets a distinct resource and action, so selection is generally unambiguous. There is minor overlap between discord_create_dm (opens a DM channel) and discord_send_dm (which implicitly does the same plus sends), and send_message vs send_dm could be confused, but descriptions clarify the boundaries.
Every tool follows a strict discord_verb_noun snake_case pattern (discord_send_message, discord_list_channels, discord_create_dm, etc.). The convention is uniform across all 15 tools with no deviations.
At 15 tools the surface sits at the top of the well-scoped range and each tool maps to a concrete Discord operation. Nothing feels redundant enough to remove, and no important area is padded with trivial variants.
Core messaging lifecycle (send/read/edit/delete/search), channels, guilds, members, reactions, pins, and DMs are well covered. Minor gaps exist: no channel delete/rename, no unpin, and no reaction removal, but agents can work around most of these.