discord-mcp
Related Servers
Alternatives to discord-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with Discord by managing servers, channels, forum posts, messages, reactions, webhooks, roles, and members through the Model Context Protocol.1,578 npmMIT
- FlicenseAqualityDmaintenanceEnables direct interaction with Discord servers to send messages, read channel history, and post rich embeds through natural conversation. It provides tools for listing channels and managing communication within Discord guilds using the Model Context Protocol.4-
- AlicenseNot gradedqualityBmaintenanceEnables interaction with Discord through the Model Context Protocol, providing access to all Discord features like channels, messages, threads, reactions, and roles. Supports secure Discord bot operations with rate limiting, caching, and comprehensive API coverage for OpenAI, LangChain, and other MCP clients.MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to interact with Discord through the REST API, supporting message reading and sending, channel and guild management, threads, pins, and reactions.17MIT
- FlicenseNot gradedqualityDmaintenanceEnables LLMs to read messages, discover channels, send messages, and monitor Discord communities using the Discord HTTP API.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Discord through the REST API and real-time events, supporting message management, user info, channel operations, and more with security controls.23 npm1MIT
TDQS
Scored across 222 tools
Descriptions do heavy lifting with explicit "When NOT to use → use X" cross-references, which rescues most boundary cases. But with 222 tools several clusters genuinely blur: messages_send vs messages_compose vs messages_publish vs components_v2_send vs webhooks_execute, messages_edit vs messages_update, members_modify vs members_add_role/remove_role, and three separate guild widget getters all require reading prose to pick correctly. An agent scanning names alone would misselect in these groups.
Overwhelmingly consistent snake_case with a resource-prefix grouping scheme (messages_*, channels_*, roles_*, members_*, webhooks_*, guild_*, automod_*, interactions_*). Minor deviations exist where extra qualifiers are inserted inconsistently (channels_create_guild_channel vs channels_create, stickers_get_guild_sticker, commands_create_global) and a few oddball entries (mcp_pipeline, workflow_start, intelligence_summarize_channel), but the pattern is predictable enough to guess names.
222 tools is far past the point where an agent can hold the surface in context, even though it mirrors the full Discord REST API. Entire families (webhooks_*_with_token, commands_*_global vs _guild, entitlements/skus/subscriptions, components_v2_build_*) could be collapsed or grouped behind fewer dispatchers. Discovery cost and misselection risk are high.
Coverage is remarkably thorough — messages, channels, threads, roles, members, bans, invites, webhooks, AutoMod, events, stage, soundboard, polls, voice, onboarding, entitlements — plus higher-level blueprint/workflow tools. Two concrete gaps remain: standalone (un-anchored) thread creation is explicitly deferred ("use a non-message thread tool once available"), and invites_list_channel points at a `guild_list_invites` tool that does not exist in this set, creating a dead-end reference.