# Discord [Health: Active]

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

## Description
Discord for LLM agents: 168 tools for messages, moderation, channels, roles, threads and AutoMod.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "discord": {
    "command": "npx",
    "args": ["-y","@willuhmjs/discord-mcp"],
    "env": {
      "DISCORD_TOKEN": "",
      "DISCORD_GUILD_ID": "",
      "ENABLE_MEMBERS_INTENT": "",
      "MCP_TRANSPORT": "",
      "HOST": "",
      "PORT": "",
      "MCP_SOCKET": ""
    }
  }
}
```

**Requires environment variables:** `DISCORD_TOKEN`, `DISCORD_GUILD_ID`, `ENABLE_MEMBERS_INTENT`, `MCP_TRANSPORT`, `HOST`, `PORT`, `MCP_SOCKET` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Discord MCP server does

The Discord MCP server exposes Discord administration and communication operations to MCP-compatible clients. Its 168 tools cover messages, moderation, channels, roles, threads, events, invites, webhooks, and AutoMod. Message operations support embeds, Components V2, polls, files, and replies, with validation performed before requests are sent to Discord.

It also supports interactive role menus that persist across restarts and records which users selected them. Tool permissions and parameter definitions are documented in the project’s tool reference. Calls can use string IDs, JSON-string payloads, and an optional reason for Discord’s audit log, depending on the operation.

## How it works

The server authenticates to Discord as a bot using `DISCORD_TOKEN`. `DISCORD_GUILD_ID` can provide a default server when a tool call does not include a guild ID. The bot must be created in Discord’s developer portal, invited to the target server, and configured with the Message Content privileged intent. Member-list operations additionally require the Server Members intent when enabled through configuration and the portal.

For local MCP clients, stdio mode communicates over standard input and output. HTTP mode serves MCP at `POST /mcp`, maintains stateful sessions with `Mcp-Session-Id`, and exposes `/health` after the bot connects. The default HTTP bind address is `127.0.0.1` and the default port is `8085`.

## Setup and configuration

Install through `npx` with Node.js 22 or newer, then add the server to the client’s MCP configuration. The standard setup passes `DISCORD_TOKEN` and can also pass `DISCORD_GUILD_ID`. Use `--stdio` or set `MCP_TRANSPORT=stdio` for stdio operation. HTTP deployments can set `HOST`, `PORT`, or `MCP_SOCKET`; a Unix socket is available when the endpoint should not listen on a TCP port.

Docker runs the HTTP variant and maps port 8085. VS Code uses a `servers` configuration key instead of `mcpServers`. On Windows, a client that cannot locate `npx` can invoke it through `cmd /c`. Claude Code supports adding the server with its `claude mcp add` command.

## Limitations and notes

The Discord MCP server’s HTTP endpoint has no authentication. Anyone who can reach it can call the available tools with the bot’s access, so it should stay on loopback or a private network. The Docker image binds to `0.0.0.0`, making network isolation especially important. Stdio mode does not expose a network endpoint.

The server does not read the host filesystem. URLs fetched for assets such as emojis, stickers, files, and avatars are restricted to HTTP or HTTPS, checked against private and metadata addresses before requests and after redirects, and subject to size and time limits. Webhook tokens are treated as credentials: creation returns the URL once, while list and get operations do not expose it.

Discord permissions still determine whether individual tools can act. The bot token and required privileged intents must be configured correctly, and the bot must have the relevant permissions in the target server. The project is released under the MIT license.

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