Danushkumar V MCP Discord

What Danushkumar-V-mcp-discord MCP server does

Danushkumar-V-mcp-discord MCP server gives an MCP-compatible AI client access to selected Discord operations through a bot account. It can retrieve server details, read messages, send messages to a channel by ID or name, and remove individual messages. It also covers channel administration, forum workflows, reactions, and webhook management.

The available operations include creating and deleting text channels, listing forum channels, creating and retrieving forum posts, replying to posts, and deleting posts. Message tools can add one or several reactions, or remove a reaction. Webhook tools can create, send through, edit, and delete a webhook associated with a Discord channel.

How it works

The server authenticates to Discord with a bot token and exposes the Discord operations as MCP tools. A client invokes the relevant tool when an assistant needs to inspect or change Discord data. Messages can target a channel using either its numeric identifier or its name.

Two MCP transports are available. Stdio is the default and is suited to local client configurations. Streamable HTTP provides a configurable port and stateless operation for deployments that prefer an HTTP endpoint. The documented command-line options select the transport, port, and token configuration.

Discord access is limited to servers where the bot has explicitly been installed. The bot must also have the Discord intents and permissions needed for the requested operation.

Setup and configuration

Danushkumar-V-mcp-discord requires Node.js 16 or newer, npm 7 or newer, and a Discord bot. Enable Message Content, Server Members, and Presence intents in the Discord developer configuration, then add the bot to the target server.

The token can be supplied through the DISCORD_TOKEN environment variable or with the server's --config argument. The project can be run with npx mcp-discord, installed from source with npm and a TypeScript build, or run from the published Docker image. For HTTP mode, provide --transport http and a port such as 3000.

Required Discord permissions vary by operation. The documented set includes viewing channels, sending messages, managing messages, managing channels and threads, creating public threads, sending in threads, managing webhooks, and adding reactions. Administrator access is described as the simplest setup, but narrower permissions can be selected.

Tools and capabilities

• Send and read channel messages.
• Retrieve server information.
• Create and delete text channels.
• List forum channels and manage forum posts.
• Add single or multiple reactions and remove reactions.
• Delete messages from channels.
• Create, send through, edit, and delete webhooks.

Limitations and notes

The bot cannot access a Discord server until it has been invited there. Operations may fail when the bot lacks the corresponding Discord permission or intent. The provided setup examples document Claude and Cursor configurations, along with local stdio and streamable HTTP modes. The repository material identifies the project license as MIT.