# saseq/discord-mcp [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/SaseQ/discord-mcp  
**GitHub Stars:** 584  
**Views:** 4  
**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://discord-mcp:8085/mcp"
  }
}
```

## Documentation

## What saseq/discord-mcp MCP server does

saseq/discord-mcp exposes selected Discord API operations through the Model Context Protocol. It uses JDA, the Java Discord API library, to connect an MCP client to a Discord bot and its guild data. The documented capabilities cover server information and user or member lookup, including retrieving a Discord user ID for mention formatting.

The project is intended for MCP-compatible applications and automation workflows that need to query Discord from an AI-assisted interface. A Discord bot token is required, and the bot must be configured for the Discord environment it will access.

## How it works

The recommended deployment runs as a Docker container with the HTTP profile enabled. MCP clients connect to `http://localhost:8085/mcp`, while the application also exposes an Actuator health endpoint at `http://localhost:8085/actuator/health`.

A legacy stdio mode is available through a Docker process started by the client. In that arrangement, each client session starts the configured container command. The HTTP setup instead runs one long-lived server that multiple clients or workflows can reach through its MCP endpoint.

The server can also be built with Maven and launched from the resulting JAR. Claude Code, Codex CLI, Cursor, Claude Desktop, and n8n connection examples are included, along with configuration guidance for streamable HTTP clients such as OpenClaw.

## Setup and configuration

Docker is the recommended installation method. Set `DISCORD_TOKEN` to the bot token before starting the container. Set `SPRING_PROFILES_ACTIVE=http` to run the HTTP transport. `DISCORD_GUILD_ID` is optional; when set, it supplies a default guild ID for tools that accept a `guildId` parameter.

A typical container publishes port 8085 and passes the environment variables into the image:

```bash
export DISCORD_TOKEN="YOUR_DISCORD_BOT_TOKEN"
export DISCORD_GUILD_ID="OPTIONAL_DEFAULT_SERVER_ID"
export SPRING_PROFILES_ACTIVE=http

docker run -d -i \
  --name discord-mcp \
  -p 8085:8085 \
  -e SPRING_PROFILES_ACTIVE \
  -e DISCORD_TOKEN \
  -e DISCORD_GUILD_ID \
  saseq/discord-mcp:latest
```

Docker Compose can build and start the service from a cloned repository. Manual installation requires Maven, followed by starting the packaged JAR with the Discord token and HTTP profile environment variables.

## Tools and capabilities

- `get_server_info` retrieves detailed information about a Discord server.
- `get_user_id_by_name` looks up a Discord user's ID by username within a guild, supporting mention syntax such as `<@id>`.
- `get_member_by_id` retrieves a Discord guild member using an ID.

The optional default guild ID can reduce the need to pass `guildId` separately when a tool supports that parameter.

## Limitations and notes

The HTTP endpoint at `localhost` is reachable only from the local machine. Remote clients, including Claude Desktop remote connectors, need a publicly reachable HTTPS endpoint through a tunnel or reverse proxy. If n8n runs inside Docker, its `localhost` refers to the n8n container rather than the host; use a reachable Docker service name or host address instead.

Keep the Discord bot token in the runtime environment and pass it to the container or Java process. The stdio configuration starts a separate process or container per client session, while HTTP mode uses a shared long-running server.

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