Discord MCP Server
Discord interactions and channel management for your local AI assistant workflows.
Data last scanned today · Reviewed today
Overview
The Discord MCP Server provides an interface between the Model Context Protocol and the Discord API using the JDA framework. It enables AI models to perform tasks such as retrieving server data, managing channels, and sending messages directly from within MCP-compatible host applications. Deployment is handled via Docker, requiring a Discord bot token and optional guild ID configuration. The server is designed for users looking to build automated bots or incorporate Discord community data into their local AI workflows.
Our verdict
With a security score of 39/100, this tool is categorized as high risk. The score reflects that the server is community-maintained and has not undergone an editorial review, nor has its authentication or OAuth implementation been verified. Because it requires a Discord bot token and allows interaction with your servers, it should be used only in trusted local environments by users comfortable managing their own security configurations.
- Uses zero direct dependencies to reduce supply chain exposure
- Provides documented setup instructions via Docker and Docker Compose
- Released under the permissive MIT license
- Not maintained by the official Discord organization
- Lacks external security or editorial verification of its codebase
- Authentication methods have not been independently audited
Tools
| Tool | Description | Risk |
|---|---|---|
| get_server_info | Get detailed discord server information | low |
| get_user_id_by_name | Get a Discord user's ID by username in a guild for ping usage <@id> | low |
| send_private_message | Send a private message to a specific user | medium |
| edit_private_message | Edit a private message from a specific user | medium |
| delete_private_message | Delete a private message from a specific user | high |
| read_private_messages | Read private message history from a specific user (includes attachment metadata, supports count 1-100 and optional cursor: before or after or around) | low |
| send_message | Send a message to a specific channel | medium |
| edit_message | Edit a message from a specific channel | medium |
| delete_message | Delete a message from a specific channel | high |
| read_messages | Read message history from a specific channel (includes attachment metadata, supports count 1-100 and optional cursor: before or after or around) | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What prerequisites are required to run this MCP server?
You must have Docker installed to run the recommended containerized version. If you choose to build the project manually, you must have Maven installed.
›Is the DISCORD_GUILD_ID environment variable mandatory?
No, it is optional. Providing it sets a default Discord server ID so that any tool accepting a guildId parameter can omit it.
›How can I verify if the server is running correctly?
If running via Docker, you can check the status using 'curl -fsS http://localhost:8085/actuator/health' to verify the health endpoint.
›What is the difference between HTTP and legacy stdio connection modes?
HTTP mode is recommended as a singleton for persistent connections. Legacy stdio mode starts a new process or container per client session.
Badge
Maintain this server? Add the live badge to your README.