discord-server-mcp
Related Servers
Alternatives to discord-server-mcp
- AlicenseAqualityFmaintenanceA Model Context Protocol server that enables LLMs to send, edit, and delete Discord messages using webhooks. It supports text content, rich embeds, and thread interactions with strict Zod-based parameter validation.312 npm1MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Claude, Cursor, or Codex to build and manage Discord servers end to end — creating channels, roles, permission overwrites, threads, webhooks, events, and messages, plus whole-server blueprints applied idempotently. Includes guard rails like read-only and safe modes, per-server allowlists, and permission explanations.163 npmMIT
- AlicenseAqualityBmaintenanceEnables natural-language administration of a whole Discord server from any MCP-compatible client: messages, channels, roles, permissions, moderation, AutoMod, emoji and stickers, server settings, and Unicode name styling. Includes a resumable server architect that turns a described structure into an ordered, idempotent plan, with preview-before-apply gating, permission preflight, and an audit trail for safety.177MIT
- AlicenseAqualityBmaintenanceEnables MCP clients such as Claude to read and manage a Discord server through a bot — channels, members, roles, messages, threads, moderation and events. Tools are organized into optional packs with dry-run defaults and a read-only mode for safer destructive actions.201,195 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to manage Discord servers, channels, roles, permissions, messages, threads, webhooks, moderation, and declarative server blueprints through MCP tools over local stdio.8 npmMIT
- FlicenseNot gradedqualityDmaintenanceComprehensive Discord server management through MCP, enabling channel, role, permission, message, moderation, and automation tasks via natural language.4-
- AlicenseAqualityDmaintenanceAn MCP server that lets AI assistants provision Discord servers (guilds, categories, channels, roles, permissions) from declarative blueprints via the Discord REST API, with idempotent diff-based planning and no deletions.15MIT
TDQS
Scored across 48 tools
Most tools target a distinct resource+action (create_channel, edit_role, ban_member), and the blueprint family (import_discord_template, preview_blueprint, export_server_structure, apply_blueprint) is clearly delineated. The main friction is two tools both billed as entry points (get_server and setup_check say "Start here"), plus partial overlap between enable_tools, use_tool and configure, which an agent could hesitate between.
Everything is snake_case and the dominant pattern is verb_noun (create_channel, edit_role, delete_messages, set_permissions, search_messages). A handful break the verb-first pattern with noun phrases (setup_check, job_status, bot_invite_link, preview_blueprint) and even invert it (setup_check vs check_permissions), but the vocabulary remains readable and predictable.
48 exposed tools far exceeds the range where an agent can reliably pick without misfires, and several are meta-tools (enable_tools, use_tool, configure) that exist purely to navigate the surface. The gated pack system shows awareness of the problem, but the initial flat list is still very heavy for what is largely Discord CRUD.
Coverage is exceptional: full CRUD for channels, categories, threads, roles, messages, invites, permissions, member moderation, plus search, permission introspection and a complete blueprint import/export/preview/apply lifecycle. Remaining operations (AutoMod, webhooks, DMs, bans list, leaving servers) are deliberately reachable through enable_tools packs, so the domain has no dead ends.