Discord MCP
Related Servers
Alternatives to Discord MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read, search, and manage Discord servers and channels using a bot token, including messaging, moderation, server administration, and connection diagnostics.MIT
- AlicenseAqualityFmaintenanceEnables LLMs to read and send Discord messages, list servers and channels, and monitor unread messages via a selfbot that uses a user token (violates Discord ToS).811 npm1MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to interact with the Discord REST API through tools for messages, reactions, threads, channels, webhooks, guilds, members, roles, moderation, events, invites, and file transfer. It supports guild allowlists, read-only mode, toolset selection, and approval before destructive actions.401,101 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with the Discord platform through a bot token, covering server and member inspection, channel and category management, message reading/searching/editing, reactions, forum posts and tags, role assignment, and webhooks. It supports both stdio and streamable HTTP transports for local or self-hosted use.842 npmMIT
- AlicenseNot gradedqualityBmaintenanceGrants read-only access to your own Discord DMs, group chats, and server channels, letting a model search messages, pull recent or full conversation history, and view attachments like images and PDFs. Messages are kept in a local SQLite cache with full-text search, with older history fetched from Discord only on demand.1MIT
- AlicenseNot gradedqualityDmaintenanceProvides full Discord REST API access through a bot token, enabling server management including channels, messages, members, roles, and more.228 npm1MIT
TDQS
Scored across 32 tools
Most tools map cleanly to distinct Discord resources (messages, channels, roles, members, guilds). The main ambiguity is discord_request, which overlaps with nearly every other tool by design, but its generic nature is clearly described as a catch-all REST endpoint accessor.
The vast majority of tools follow a consistent verb_noun pattern: read_messages, delete_message, list_roles, create_channel, get_guild, add_member_role. Minor deviations exist, such as discord_request as a standalone generic tool and get_current_user not matching the list/get style perfectly, but the overall pattern is predictable.
32 tools is on the heavier side but justified for a Discord server integration covering messages, channels, members, roles, threads, invites, and reactions. The generic discord_request tool helps keep the count from being even larger, and every tool addresses a concrete Discord operation.
The surface covers core interaction and moderation workflows well: message lifecycle, channel lifecycle, role assignment, member updates, invites, threads, pins, reactions, and DMs. Notable gaps include no dedicated webhook/emoji/event tools, though discord_request explicitly covers those REST operations, so agents can work around the gap.