Discord Management MCP
Provides tools for inspecting, backing up, and managing Discord guilds, including guild and member inventory, moderation and AutoMod, roles, channels, server configuration, backups, and restore planning with confirmation and backup safeguards.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Discord Management MCP Back up my Discord server and report the backup ID and coverage."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Discord Management MCP
Safe-by-default Discord management from any MCP client

Discord Management MCP is a local Model Context Protocol (MCP) server for inspecting, backing up, and managing Discord guilds. It runs over stdio, keeps the bot token and backup files on the operator's machine, and places confirmation, backup, and restore guards in front of every mutation. The server exposes 54 tools across guild inventory, moderation, roles, channels, server settings, backups, and restore planning.
It works with any MCP client that supports local stdio servers, including Claude Desktop, Claude Code, Cursor, VS Code, Codex, Windsurf, and Cline. This independently developed project is not affiliated with, endorsed by, sponsored by, or approved by Discord Inc.
New to Discord bots? The setup and first use guide walks through creating the application, inviting the bot with the right permissions, copying the server ID, registering the client, verifying the connection, and running the first safe backup and restore.
Install
The published package runs with one command:
npx --yes discord-management-mcpThe package is published on npm as discord-management-mcp and declares MCP registry metadata for io.github.TheStreamCode/discord-management-mcp through package.json and server.json.
Register with your client
Every client needs the same command, arguments, and DISCORD_TOKEN environment variable. Paste the equivalent of this entry into the client's MCP configuration:
{
"mcpServers": {
"discord-management": {
"command": "npx",
"args": ["--yes", "discord-management-mcp"],
"env": {
"DISCORD_TOKEN": "your_bot_token"
}
}
}
}Client | Registration |
Claude Desktop | Add the entry above to the MCP servers configuration. |
Claude Code | Add a local stdio server with the same command and arguments. |
Cursor | Add the entry above to the MCP configuration. |
VS Code | Add the same command and arguments in the client's MCP configuration. |
Codex | Add a stdio server entry with the same command and arguments. |
Windsurf | Add the entry above to the MCP configuration. |
Cline | Add the server in the MCP settings panel. |
Claude Desktop, Cursor, Windsurf, and Cline accept the mcpServers JSON shape shown above. Clients that use a different configuration schema accept the same command, args, and env values. See each client's own documentation for the exact file or command.
Related MCP server: TheeDiscordMCP
Quick start
The short version, with the full walkthrough in setup and first use:
Create the bot. Developer Portal > New Application > Bot > Reset Token. That token is the only credential the server needs. Do not use the Application ID, Public Key, or OAuth2 client secret.
Invite it. OAuth2 > URL Generator > scope
botplus the permissions you need. Start with View Channels, Manage Channels, Manage Roles, Manage Server, View Audit Log, and the moderation permissions you plan to use. Then drag the bot role above the roles it must edit.Copy the server ID. Enable Developer Mode, right-click the server icon, Copy Server ID. This number is the
guildIdargument, not the bot's application ID.Register the client. Use the configuration in Register with your client with
DISCORD_TOKENinenv, or put the token in.env.localin the working directory.Verify and back up. Ask the client to run
discord_list_guilds, thendiscord_backup_createfor your server, and readcoverage.channels.complete.
Example first request:
Use discord_list_guilds, then discord_backup_create for the server I name, and report the backup ID and coverage.Then change things only through the guarded path: create a backup, review the target objects, apply one small change, and confirm the result. Every mutation needs an audit reason:
{
"guildId": "123456789012345678",
"confirm": true,
"reason": "Create the approved community announcements channel"
}High-impact operations also require a guild-matched backupId unless the operator explicitly accepts allowWithoutBackup: true. The tool catalog lists the exact policy for every mutating tool.
Features
Many Discord MCP servers stop at read-only inspection or previewing a change, and some route the bot token through a hosted service. Discord Management MCP executes changes locally, but only through a guard and recovery path:
Capability | Typical preview-only server | Discord Management MCP |
Read-only inspection | Yes | Yes, 23 read-only tools |
Execute changes | No | Yes, 31 mutating and moderation tools |
Local backup before risky changes | Rarely | JSON schema v2 snapshots with channel coverage |
Restore | No | Plan with plan hash, apply with pre-restore backup |
Rollback guarantee | Not offered | Best effort, reported honestly with |
Data path | Often hosted | Local stdio only |
What that means in practice:
Local by design. The bot token, snapshots, restore plans, and stdio transport stay on the operator's machine. There is no hosted relay and no public HTTP listener.
Preview, then apply. Backups can be diffed and turned into a restore plan before anything changes, and plans carry a hash that apply can verify.
Backup to restore promise. A risky change can point at a same-guild snapshot; restore apply writes a fresh pre-restore backup before its first Discord mutation.
An explicit safety matrix. Every Discord mutation needs
confirm: trueand a reason. The listed high-impact tools need a same-guild backup. Emergency incident actions stay available without one.Truthful recovery. Restore reports skipped, lossy, applied, and failed operations instead of promising an impossible full rollback.
Backup to restore
The recovery path has three steps:
discord_backup_createwrites a JSON snapshot toBACKUP_DIRatomically, strips invite codes, webhook tokens, and other secrets, and records channel coverage incoverage.channels.discord_backup_diffanddiscord_backup_restore_planshow what would change. A plan includes aplanHashandNOT_RESTOREDwarnings for captured sections that Discord cannot recreate.discord_backup_restore_applycan verify anexpectedPlanHash, creates a pre-restore backup, then applies supported role and channel fields conservatively. Deletes remain opt-in.
Discord cannot restore original IDs after delete and recreate, message or audit-log history, exact invite codes, webhook tokens, or every community and discovery setting. The server reports those limits instead of hiding them. See safety and backups for the full model.
Tool coverage
The server registers 54 tools. See the tool catalog for every name and the guard matrix for the backup policy.
Domain | Tools |
Guild, member, and audit inventory | 17 |
Backups and restore | 6 |
Channels | 6 |
Roles | 7 |
Moderation and AutoMod | 13 |
Server configuration | 5 |
Total | 54 |
Read-only tools are annotated as read-only and never require confirmation. Mutating Discord tools require confirm: true plus a non-empty audit reason, and mutations run through a shared queue so they cannot interleave. discord_backup_create only writes a local snapshot and does not require confirmation.
Requirements
Node.js 24 or newer.
A Discord application with a bot token.
The bot invited to the target guild with only the permissions required for the intended tools.
ENABLE_MESSAGE_CONTENT and ENABLE_GUILD_MEMBERS are opt-in and require the matching privileged intents in the Discord Developer Portal. Since 2026-06-10, Discord reviews privileged intent usage at 10,000 users rather than 100 servers, and approved apps must reapply annually. See configuration for details.
Configuration
Configuration is read from the process environment first, then from .env.local in the working directory. Boolean values accept true/false, yes/no, on/off, or 1/0.
Variable | Purpose | Default |
| Discord bot token from Developer Portal > Bot > Token | Required |
| Relative directory for local JSON backups; it must stay inside the project directory |
|
| Stderr log level: |
|
| Enables message-content tools and requires the Discord Message Content intent |
|
| Enables the Guild Members gateway intent for workflows that require it |
|
See the configuration reference for token rules, logging behavior, and privileged-intent setup.
Privacy and security
Everything runs locally over stdio: the bot token, backup files, restore plans, and the server process itself never leave the operator's machine. Mutations are guarded by explicit confirmation and by backups that are validated for size, depth, structure, symlinks, and guild identity before planning or restore. A restore creates a pre-restore backup before its first Discord mutation and stops truthfully on operation failure. See design and trust boundaries and safety and backups for the full model, and SECURITY.md for private vulnerability reporting.
Safety model
Every Discord mutation requires
confirm: trueand a non-emptyreason; the reason is passed to Discord where audit-log reasons are supported.High-impact tools require a backup from the same guild, or an explicit
allowWithoutBackup: trueacknowledgement.discord_set_incident_actionsis intentionally exempt: it is used during raids, and its changes are reversible.Restore apply creates its own pre-restore backup and retains its ID on every error path.
Backup writes are atomic, and backup paths are confined to the project directory with symlink and junction rejection.
Read-only tools are implemented and annotated as read-only.
See safety and backups for the guard matrix, channel coverage, and restore behavior, and design and trust boundaries for the runtime model. Report vulnerabilities privately through SECURITY.md.
Troubleshooting
The server exits because DISCORD_TOKEN is missing or invalid
Set the Bot Token in the process environment or in .env.local in the working directory. A value that looks like a Discord Application Public Key is rejected with an explicit message: use the Bot Token, not the Application ID, Public Key, or OAuth2 client secret.
Message content comes back empty
Message-content tools need both ENABLE_MESSAGE_CONTENT=true and the Message Content Intent enabled in the Discord Developer Portal. Without both, Discord can return empty content, embeds, and attachments fields. Restart the server after changing either side. If the app is approaching the review threshold, remember that privileged intent access is reviewed at 10,000 users and must be renewed annually.
A mutation is rejected before it reaches Discord
Mutating tools require confirm: true and a non-empty reason. High-impact tools additionally require a backupId from the same guild, or an explicit allowWithoutBackup: true acknowledgement. discord_set_incident_actions is the exception for emergency use. Check the guard matrix before retrying.
Channels are missing from a backup or channel list
The bot can only back up channels it can view. Starting 2026-11-16, Discord omits channels the bot cannot view from GET /guilds/{id}/channels, and gateway payloads can carry obfuscated channel objects. Backups record this in coverage.channels and warn when coverage is incomplete. Grant VIEW_CHANNEL where the channels matter, and treat complete: false as a partial rollback point. See channel coverage and obfuscation.
Restore reports skipped or lossy operations
Discord cannot recreate original IDs, message or audit-log history, exact invite codes, webhook tokens, managed integration objects, or every community and discovery setting. Check the plan's planHash and its NOT_RESTORED warnings, then review the reported operations before retrying.
Logs are too quiet or too noisy
Set LOG_LEVEL to error, warn, info, or debug. Logs are JSON lines on stderr, so stdout stays reserved for MCP protocol traffic. Use debug while diagnosing a tool call and error for quiet hosts.
Development
Requirements: Node.js 24 or newer and npm from the lockfile.
git clone https://github.com/TheStreamCode/discord-management-mcp.git
cd discord-management-mcp
npm ci
npm run lint
npm run typecheck
npm test
npm run build
npm run verify:mcp
npm run preflight
npm run pack:check
npm audit --omit=dev --audit-level=highnpm run verify:mcp starts the built server over stdio with a placeholder token and checks the advertised MCP surface: 54 tools, deterministic tool listing, titles, descriptions, input and output schemas, and annotation hints. It never calls the Discord API.
Tests use mocks and must not contact Discord. Live mutations are never part of routine verification. The repository keeps its engineering guidance in AGENTS.md; it is not shipped in the npm package. See CONTRIBUTING.md for contribution rules.
Support
See SUPPORT.md. Use GitHub Issues for reproducible bugs and feature proposals, and report vulnerabilities privately through GitHub Security Advisories.
Contributing
See CONTRIBUTING.md. Pull requests must pass npm run preflight, npm run verify:mcp, and the required CI checks.
License
MIT, see LICENSE. Copyright (c) 2026 Michael Gasperini (Mikesoft).
This independently developed project is not affiliated with, endorsed by, sponsored by, or approved by Discord Inc. Discord is a trademark of Discord Inc. See NOTICE for the applicable Discord terms and policies.
Maintained by Michael Gasperini (Mikesoft). If this project is useful to you, consider sponsoring its maintenance.
Available Tools
54 toolsdiscord_assign_roleAssign Discord roleC
Assign a role to a guild member.
Inputs: roleId (required), userId (required), guildId (required), reason, +1 more. Returns: ok, name, error, action, +5 more
discord_backup_createCreate Discord BackupA
Capture the current Discord guild configuration as a JSON backup snapshot.
Inputs: guildId (required). Returns: ok, error, counts, guildId, +4 more
discord_backup_diffDiff Discord BackupsARead-onlyIdempotent
Compare roles and channels between two stored backup snapshots.
Inputs: afterBackupId (required), beforeBackupId (required). Returns: ok, error, summary, operations, +2 more
discord_backup_listList Discord BackupsARead-onlyIdempotent
List stored Discord backup snapshot IDs, newest first.
Inputs: no named parameters. Returns: ok, note, count, error, +2 more
discord_backup_readRead Discord BackupARead-onlyIdempotent
Validate a stored Discord backup and return sanitized metadata without exposing its payload.
Inputs: backupId (required). Returns: ok, note, error, counts, +7 more
discord_backup_restore_applyApply Discord Backup RestoreADestructive
Conservatively apply role/channel create/update operations from a backup. Creates a pre-restore backup first, rejects an expectedPlanHash mismatch before mutating, and deletes require includeDeletes: true.
Inputs: backupId (required), targetGuildId (required), reason, confirm, +3 more. Returns: ok, error, failed, applied, +7 more
discord_backup_restore_planPlan Discord Backup RestoreARead-onlyIdempotent
Create a non-mutating restore plan that compares the live guild to a stored backup and includes a stable planHash.
Inputs: backupId (required), targetGuildId (required). Returns: ok, plan, error, summary, +3 more
discord_ban_memberBan Discord memberBDestructive
Ban a guild member. Requires confirmation and either a backupId or allowWithoutBackup.
Inputs: userId (required), guildId (required), reason, confirm, +3 more. Returns: ok, error
discord_bulk_ban_membersBulk ban Discord membersADestructive
Ban up to 200 users in one Discord request. Requires confirmation and either a backupId or allowWithoutBackup.
Inputs: guildId (required), userIds (required), reason, confirm, +3 more. Returns: ok, error
discord_bulk_delete_messagesBulk delete Discord messagesADestructive
Bulk delete messages by count or explicit message IDs. Requires confirmation and backup acknowledgement.
Inputs: channelId (required), limit, reason, confirm, +3 more. Returns: ok, error
discord_create_automod_ruleCreate Discord AutoMod ruleC
Create a Discord AutoMod rule with JSON trigger metadata and actions.
Inputs: name (required), actions (required), guildId (required), eventType (required), +7 more. Returns: ok, error
discord_create_channelCreate Discord channelC
Create a text, voice, category, forum, or stage channel.
Inputs: name (required), type (required), guildId (required), nsfw, +8 more. Returns: ok, name, note, type, +10 more
discord_create_inviteCreate Discord inviteC
Create an invite for a channel without returning its secret code or URL.
Inputs: channelId (required), maxAge, reason, unique, +3 more. Returns: ok, error
discord_create_roleCreate Discord roleC
Create a Discord role, optionally with primary/secondary/tertiary gradient colors.
Inputs: name (required), guildId (required), color, hoist, +5 more. Returns: ok, name, error, action, +5 more
discord_create_scheduled_eventCreate Discord scheduled eventB
Create a Discord scheduled event. Use channelId for voice/stage events or location for external events.
Inputs: name (required), guildId (required), entityType (required), scheduledStartTime (required), +9 more. Returns: ok, error
discord_create_webhookCreate Discord webhookC
Create a webhook in a text-capable guild channel.
Inputs: name (required), channelId (required), avatar, reason, +1 more. Returns: ok, error
discord_delete_automod_ruleDelete Discord AutoMod ruleCDestructive
Delete a Discord AutoMod rule.
Inputs: ruleId (required), guildId (required), reason, confirm, +2 more. Returns: ok, error
discord_delete_channelDelete Discord channelBDestructive
Delete a Discord guild channel after confirmation and backup acknowledgement.
Inputs: channelId (required), reason, confirm, backupId, +1 more. Returns: ok, name, note, type, +10 more
discord_delete_roleDelete Discord roleADestructive
Delete a Discord role after confirmation and backup acknowledgement.
Inputs: roleId (required), guildId (required), reason, confirm, +2 more. Returns: ok, name, error, action, +5 more
discord_delete_scheduled_eventDelete Discord scheduled eventCDestructive
Delete a Discord scheduled event.
Inputs: eventId (required), guildId (required), reason, confirm, +2 more. Returns: ok, error
discord_delete_webhookDelete Discord webhookADestructive
Delete a webhook by ID. Requires confirmation and either a backupId or allowWithoutBackup.
Inputs: webhookId (required), reason, confirm, backupId, +1 more. Returns: ok, error
discord_get_channelGet Discord channelCRead-onlyIdempotent
Get Discord channel metadata.
Inputs: guildId (required), channelId (required). Returns: ok, error
discord_get_guildGet Discord guildCRead-onlyIdempotent
Get Discord guild metadata.
Inputs: guildId (required). Returns: ok, error
discord_get_roleGet Discord roleCRead-onlyIdempotent
Get Discord role metadata.
Inputs: roleId (required), guildId (required). Returns: ok, error
discord_kick_memberKick Discord memberADestructive
Kick a guild member. Requires confirmation and either a backupId or allowWithoutBackup.
Inputs: userId (required), guildId (required), reason, confirm, +2 more. Returns: ok, error
discord_list_application_commandsList Discord application commandsCRead-onlyIdempotent
List guild application commands.
Inputs: guildId (required). Returns: ok, error
discord_list_audit_logList Discord audit log entriesBRead-onlyIdempotent
Read recent Discord audit log entries. Requires the View Audit Log permission for the bot.
Inputs: guildId (required), after, limit, before, +2 more. Returns: ok, error
discord_list_automod_rulesList Discord AutoMod rulesBRead-onlyIdempotent
List AutoMod rules in a Discord guild.
Inputs: guildId (required). Returns: ok, error
discord_list_bansList Discord bansBRead-onlyIdempotent
List guild bans with pagination. Requires the Ban Members permission.
Inputs: guildId (required), after, limit, before. Returns: ok, error
discord_list_channel_messagesList Discord channel messagesBRead-onlyIdempotent
List recent messages from a text-based channel. Requires ENABLE_MESSAGE_CONTENT=true and the Discord Message Content privileged intent.
Inputs: guildId (required), channelId (required), after, limit, +2 more. Returns: ok, error
discord_list_channelsList Discord channelsBRead-onlyIdempotent
List channels in a Discord guild.
Inputs: guildId (required). Returns: ok, error
discord_list_emojisList Discord emojisCRead-onlyIdempotent
List emojis in a Discord guild.
Inputs: guildId (required). Returns: ok, error
discord_list_guildsList Discord guildsARead-onlyIdempotent
List Discord guilds visible to the configured bot.
Inputs: no named parameters. Returns: ok, error
discord_list_invitesList Discord invitesARead-onlyIdempotent
List non-secret invite metadata in a Discord guild; invite codes and URLs are omitted.
Inputs: guildId (required). Returns: ok, error
discord_list_membersList Discord membersCRead-onlyIdempotent
List guild members, capped at 1000.
Inputs: guildId (required), after, limit. Returns: ok, error
discord_list_role_member_countsList Discord role member countsBRead-onlyIdempotent
List how many guild members currently hold each role.
Inputs: guildId (required). Returns: ok, error
discord_list_rolesList Discord rolesCRead-onlyIdempotent
List roles in a Discord guild.
Inputs: guildId (required). Returns: ok, error
discord_list_scheduled_eventsList Discord scheduled eventsCRead-onlyIdempotent
List scheduled events in a Discord guild.
Inputs: guildId (required). Returns: ok, error
discord_list_stickersList Discord stickersCRead-onlyIdempotent
List stickers in a Discord guild.
Inputs: guildId (required). Returns: ok, error
discord_list_webhooksList Discord webhooksARead-onlyIdempotent
List webhooks in a Discord guild without exposing tokens.
Inputs: guildId (required). Returns: ok, error
discord_remove_roleRemove Discord roleCDestructiveIdempotent
Remove a role from a guild member.
Inputs: roleId (required), userId (required), guildId (required), reason, +1 more. Returns: ok, name, error, action, +5 more
discord_reorder_channelsReorder Discord channelsCDestructiveIdempotent
Set channel positions within a guild.
Inputs: guildId (required), positions (required), reason, confirm. Returns: ok, name, note, type, +10 more
discord_reorder_rolesReorder Discord rolesCDestructiveIdempotent
Set role positions within a guild.
Inputs: guildId (required), positions (required), reason, confirm. Returns: ok, name, error, action, +5 more
discord_search_membersSearch Discord membersARead-onlyIdempotent
Search guild members by username or nickname. Requires ENABLE_GUILD_MEMBERS=true and the Guild Members privileged intent.
Inputs: query (required), guildId (required), limit. Returns: ok, error
discord_set_channel_permissionsSet Discord channel permissionsCDestructiveIdempotent
Set explicit channel permission overwrites for a role or member.
Inputs: deny (required), allow (required), targetId (required), channelId (required), +5 more. Returns: ok, name, note, type, +10 more
discord_set_incident_actionsSet Discord incident actionsADestructive
Temporarily disable guild invites and/or DMs during a raid or incident. Emergency action: no backup is required, each window is capped at 24 hours, and null re-enables immediately.
Inputs: guildId (required), reason, confirm, dmsDisabledUntil, +1 more. Returns: ok, error
discord_set_voice_channel_statusSet Discord voice channel statusB
Set or clear the status text shown on a voice channel. Uses the Discord REST voice-status endpoint and requires the bot to be allowed to manage the channel.
Inputs: status (required), channelId (required), reason, confirm. Returns: ok, name, note, type, +10 more
discord_timeout_memberTimeout Discord memberCDestructiveIdempotent
Timeout a guild member for the requested duration in seconds.
Inputs: userId (required), guildId (required), durationSeconds (required), reason, +1 more. Returns: ok, error
discord_unban_memberUnban Discord memberCDestructiveIdempotent
Remove a guild ban for a user.
Inputs: userId (required), guildId (required), reason, confirm. Returns: ok, error
discord_update_automod_ruleUpdate Discord AutoMod ruleCDestructiveIdempotent
Update a Discord AutoMod rule with JSON trigger metadata and actions.
Inputs: ruleId (required), guildId (required), name, reason, +7 more. Returns: ok, error
discord_update_channelUpdate Discord channelCDestructiveIdempotent
Update editable properties on a Discord guild channel, including voice bitrate, user limit, and RTC region.
Inputs: channelId (required), name, nsfw, topic, +7 more. Returns: ok, name, note, type, +10 more
discord_update_guild_settingsUpdate Discord guild settingsADestructiveIdempotent
Update basic guild settings such as name, description, moderation levels, locale, and AFK timeout. Requires a backupId or allowWithoutBackup.
Inputs: guildId (required), name, reason, confirm, +8 more. Returns: ok, error
discord_update_roleUpdate Discord roleCDestructiveIdempotent
Update editable Discord role fields, including gradient colors.
Inputs: roleId (required), guildId (required), name, color, +6 more. Returns: ok, name, error, action, +5 more
discord_update_scheduled_eventUpdate Discord scheduled eventDDestructiveIdempotent
Update a Discord scheduled event.
Inputs: eventId (required), guildId (required), name, image, +11 more. Returns: ok, error
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 54 tools
Most tools target clearly distinct resources and actions, especially the CRUD families for channels, roles, events, webhooks, and AutoMod. A few boundaries are less crisp, such as backup/restore-plan/apply versus general guild settings mutation, but descriptions generally guide selection correctly.
Tool names consistently use the discord_ prefix followed by a snake_case verb_noun pattern. Variants like bulk_delete, backup_restore_plan, and set_voice_channel_status remain predictable and readable within the same convention.
With 54 tools, the surface is very large for a single MCP server and exceeds the range where an agent can comfortably scan and select tools. Many administrative operations could likely be grouped into fewer parameterized tools.
The server covers a broad Discord admin surface: guilds, channels, roles, members, moderation, AutoMod, scheduled events, webhooks, invites, audit logs, and backups. Notable gaps remain around message sending/editing, webhook updates, invite deletion, and application command management.
Maintenance
Related MCP Connectors
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
- Discortics - Discord BotDeprecatedcom.discortics
Set up and manage your Discord server from MCP: channels, roles, verification, tickets and security.
Manage VaultCord-protected Discord servers: members, verification, backups and security.
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables Discord server inspection, structural editing, blueprint-based setup and audit, with read/write tools and dry-run safety.MIT
- AlicenseBqualityDmaintenanceLocal 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
- FlicenseNot gradedqualityCmaintenanceEnables MCP clients to read, post to, and moderate a Discord server through the Discord REST API, with opt-in guardrails and dry-run safeguards.-
- 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.141 npmMIT