# saseq/discord-mcp [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/SaseQ/discord-mcp  
**GitHub Stars:** 482  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/saseq-discord-mcp

## Description
A MCP server for the Discord integration. Enable your AI assistants to seamlessly interact with Discord. Enhance your Discord experience with powerful automation capabilities.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "discord-mcp": {
    "url": "http://localhost:8085/mcp"
  }
}
```

## Documentation

## What the saseq/discord-mcp MCP server does

The saseq/discord-mcp MCP server connects MCP-compatible applications to the Discord API through a Discord bot. It is intended for agent workflows that need to read server information or perform Discord actions without implementing Discord API calls in the client.

The documented functionality includes retrieving detailed information about a Discord server, managing channels, sending messages, looking up a user's Discord ID by username within a guild, and sending private messages to a specific user. The available operations depend on the permissions granted to the configured bot and the Discord environment where it is installed.

## How it works

The application is implemented with JDA, the Java Discord API library. The recommended deployment runs one Docker container in HTTP mode. That container exposes the MCP endpoint at `http://localhost:8085/mcp`, which MCP clients can use as a shared connection.

A legacy stdio mode is also documented. In that setup, a client starts the Docker image as a process and communicates through standard input and output. HTTP mode is described as the preferred singleton arrangement because multiple clients can connect to the same running service.

The Discord bot authenticates with `DISCORD_TOKEN`. `DISCORD_GUILD_ID` is optional and supplies a default server ID, allowing tools that accept a `guildId` parameter to omit it.

## Setup and configuration

Docker is the recommended installation path. Set the bot token and activate the HTTP Spring profile before starting the container:

```bash
export DISCORD_TOKEN="your-bot-token"
export SPRING_PROFILES_ACTIVE=http
docker run -d -i --name discord-mcp --restart unless-stopped -p 8085:8085 -e SPRING_PROFILES_ACTIVE -e DISCORD_TOKEN -e DISCORD_GUILD_ID saseq/discord-mcp:latest
```

The image uses port 8085 for the MCP endpoint. The service also exposes an Actuator health URL at `http://localhost:8085/actuator/health`.

For a source-based installation, clone the repository, run `mvn clean package`, and launch the resulting JAR with the Discord token and HTTP profile configured. Docker Compose is another documented option and builds the project from the cloned repository.

Clients can connect using the HTTP URL. Cursor and Claude Desktop are documented integrations; Claude Desktop can also launch the image in legacy stdio mode. Remote Claude Desktop connectors require a publicly reachable HTTPS endpoint rather than a localhost URL.

## Tools and capabilities

The saseq/discord-mcp MCP server documents these tool groups and operations:

- Server information: retrieve detailed Discord server information with `get_server_info`.
- User management: resolve a username to a guild user ID with `get_user_id_by_name`.
- Private messaging: send a direct message with `send_private_message`.
- Discord administration and communication: manage channels and send messages, as described in the project documentation.

The `DISCORD_GUILD_ID` default can reduce repeated guild ID arguments, but it is not required when a tool receives the guild ID directly.

## Limitations and notes

The server requires a Discord bot token and appropriate Discord permissions. The material does not specify the full permission matrix, supported channel operations, or the complete tool list, so those details should be confirmed against the repository before production use.

A localhost endpoint is available only to clients that can reach the host running the container. For remote clients, the endpoint must be exposed through an appropriate public HTTPS setup. Claude Desktop's remote connector configuration is managed in its Connectors interface rather than its local configuration file.

_Full upstream README: https://allmcps.com/mcp/saseq-discord-mcp/readme_