Discord MCP

An MCP (Model Context Protocol) server that exposes Discord bot actions as tools for LLM clients (e.g. Claude Desktop, Claude Code).

Requirements

• Python 3.10+

• uv for dependency management and running the server

• A Discord bot application with a bot token (Discord Developer Portal)

Installation

git clone https://github.com/EncryptMan/discord-mcp discord-mcp
cd discord-mcp
uv sync

Configuration

The server reads its Discord bot token from the DISCORD_BOT_TOKEN environment variable.

Add the server to your MCP client config (e.g. claude_desktop_config.json):

{
  "mcpServers": {
    "discord": {
      "command": "uv",
      "args": [
        "run",
        "--project",
        "/absolute/path/to/discord-mcp",
        "python",
        "/absolute/path/to/discord-mcp/main.py"
      ],
      "env": {
        "DISCORD_BOT_TOKEN": "your-bot-token-here"
      }
    }
  }
}

Restart your MCP client after editing the config so it picks up the new server.

Bot permissions

Make sure the bot is invited to your server with at least the following permissions/intents enabled in the Developer Portal, depending on which tools you use:

• bot scope + relevant OAuth2 permissions (Send Messages, Manage Roles, Manage Channels, Kick/Ban Members, etc.)

• Privileged Gateway Intents: SERVER MEMBERS INTENT (for member lookups/roles) and MESSAGE CONTENT INTENT (for reading message content)

Tools

Update this list to match what main.py actually implements.

Running standalone

uv run --project /absolute/path/to/discord-mcp python /absolute/path/to/discord-mcp/main.py

The server communicates over stdio, so it's meant to be launched by an MCP client rather than run interactively.

Security notes

• Never commit your DISCORD_BOT_TOKEN — keep it in your MCP client config or a local .env file that's gitignored.

• Scope the bot's server permissions to only what these tools need; avoid granting Administrator unless required.

License

Add a license of your choice (MIT, Apache-2.0, etc.).