discord-admin-mcp
Related Servers
Alternatives to discord-admin-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceA local MCP server that lets AI clients control a Discord bot via Discord's REST API, offering messaging, administration, and moderation tools. Includes safety features such as guild scoping, allowlists, and opt-in write permissions.20MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that exposes Discord API as tools, enabling users to manage servers, channels, messages, and roles through natural language.-
- AlicenseAqualityDmaintenanceMCP server over the real Discord REST API: 5 read-only tools plus 7 write tools gated off by default behind DISCORD_MCP_ENABLE_WRITE.121MIT
- AlicenseBqualityCmaintenanceLocal MCP server for inspecting and managing an allowlisted Discord server via Discord's REST API, with safety modes, idempotent JSON blueprints, and destructive-operation safeguards.271MIT
- FlicenseCqualityDmaintenanceAn MCP server that exposes Discord bot actions as tools for LLM clients.291-
- AlicenseAqualityDmaintenanceAn MCP server that enables LLMs to control Discord servers via a bot token, providing comprehensive management tools for messages, members, roles, channels, permissions, and more.6781 npmMIT
TDQS
Scored across 28 tools
Each tool targets a distinct resource+action pair: channel CRUD, role CRUD, role assignment (add_role/remove_role), member moderation (kick/ban/unban/timeout), and message operations are all clearly separated. Minor overlap exists between list_members/search_members and between set_channel_permission and the role tools, but the descriptions make the boundaries clear enough to choose correctly.
The dominant pattern is a consistent verb_noun snake_case convention (delete_channel, kick_member, create_role, delete_invite, send_message). Two outliers — 'whoami' and 'audit_log' — break the pattern, but everything else is predictable.
28 tools is slightly above the comfortable range, and the surface covers many sub-domains (members, channels, roles, messages, invites, moderation). Nearly every tool does correspond to a real, distinct Discord operation, so it is heavy but not padded.
Core lifecycles are covered: channel create/edit/delete/list, role create/edit/delete plus assign/remove, member kick/ban/unban/timeout/nickname, message read/send/delete, and invite create/list/delete, plus audit log and permission overrides. Gaps include message edit/pin, single-member fetch (get_member), and guild-level settings, which agents would have to work around.