A Model Context Protocol (MCP) server for the Discord API, this project enables AI assistants to seamlessly interact with Discord servers. It targets developers and power users seeking to automate Discord tasks, manage channels, send messages, and retrieve server information programmatically. The core benefit is bridging AI capabilities directly into Discord environments for enhanced automation and control.

How It Works

This project implements an MCP server that translates requests from AI clients into Discord API actions using the Java Discord API (JDA). It exposes Discord functionalities through an HTTP endpoint (http://localhost:8085/mcp) or via standard input/output (stdio) for legacy integrations. The recommended deployment method is Docker, which sets up a persistent, shared server instance, simplifying management and access for multiple AI clients.

Quick Start & Requirements

• Primary Install/Run: Docker installation is recommended.
  1. Create a local .env file with SPRING_PROFILES_ACTIVE=http, DISCORD_TOKEN=<YOUR_DISCORD_BOT_TOKEN>, and optionally DISCORD_GUILD_ID.
  2. Execute docker compose up -d --build to start the server.
• Manual Installation: Requires Git and Maven. Clone the repository, run mvn clean package, then execute the generated JAR file with the necessary environment variables.
• Prerequisites: Docker (recommended), Maven (for manual build), a Discord Bot Token.
• Links: Docker installation (docker.com), Maven installation (baeldung.com), Cursor MCP docs (docs.cursor.com/context/model-context-protocol).

Highlighted Details

• Provides an extensive toolkit for Discord operations, including Server Information, User Management (kick, ban, timeout, nickname), Message Management (send, edit, delete, react), Channel Management (create, edit, delete), Role Management, Moderation, Scheduled Events, and Emoji Management.
• Offers out-of-the-box integration support for various MCP clients such as Claude, Codex, OpenClaw, Cursor, and Claude Desktop, utilizing both HTTP and legacy stdio transports.
• The optional DISCORD_GUILD_ID environment variable streamlines client configuration by establishing a default server context.

Maintenance & Community

No specific details regarding maintainers, community channels (e.g., Discord/Slack), or project roadmap are provided within the README.

Licensing & Compatibility

The README does not specify a software license. This omission may present compatibility challenges for commercial use or integration into closed-source projects.

Limitations & Caveats

The preferred Docker installation method requires Docker to be pre-installed on the host system. Manual installation necessitates a working Maven environment. A significant adoption blocker is the absence of a declared software license in the project's documentation.