Why this one?

• 95+ tools: messages, channels, roles, permissions, moderation, forums, webhooks, scheduled events, invites, DMs, embeds, and more
• Multi-guild: works across multiple servers, no GUILD_ID lock-in
• Lightweight: TypeScript + Node.js, ~70kB package, ~73MB Docker image (vs 400MB+ for Java alternatives)
• Modular: clean architecture, easy to extend with new tools
• Two install methods: npm or Docker, your choice

Quick Start

Add this to your MCP client config and replace YOUR_TOKEN_HERE with your bot token:

{
  "mcpServers": {
    "discord": {
      "command": "npx",
      "args": ["-y", "@pasympa/discord-mcp"],
      "env": {
        "DISCORD_TOKEN": "YOUR_TOKEN_HERE"
      }
    }
  }
}

No install needed, npx handles everything.

Don't have a bot yet? See Creating Your Discord Bot.

Configuration

claude mcp add discord -e DISCORD_TOKEN=YOUR_TOKEN_HERE -- npx -y @pasympa/discord-mcp

{
  "inputs": [
    {
      "type": "promptString",
      "id": "discord-token",
      "description": "Discord Bot Token",
      "password": true
    }
  ],
  "servers": {
    "discord": {
      "command": "npx",
      "args": ["-y", "@pasympa/discord-mcp"],
      "env": {
        "DISCORD_TOKEN": "${input:discord-token}"
      }
    }
  }
}

{
  "mcpServers": {
    "discord": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "DISCORD_TOKEN=YOUR_TOKEN_HERE",
        "pasympa/discord-mcp:latest"
      ]
    }
  }
}

git clone https://github.com/PaSympa/discord-mcp
cd discord-mcp
npm install && npm run build

{
  "mcpServers": {
    "discord": {
      "command": "node",
      "args": ["/absolute/path/to/discord-mcp/dist/index.js"],
      "env": {
        "DISCORD_TOKEN": "YOUR_TOKEN_HERE"
      }
    }
  }
}

DISCORD_TOKEN=YOUR_TOKEN_HERE

Environment variables

Since 2.1.1 the server no longer requests the GuildMessages intent at all: nothing here subscribes to message events, and every message this server returns is fetched over REST, which connection intents do not gate. That intent used to make discord.js cache every message flowing through every channel, together with its author, which grew unbounded on a long-running server. Cache sweepers now bound what remains. DISCORD_MESSAGE_CONTENT therefore only affects whether the Message Content intent is requested at connect time; it does not change what any tool returns.

These flags only control which gateway intents the server requests when identifying. Requesting a privileged intent that is not enabled in the Developer Portal makes the connection fail at the first tool call (close code 4014); set the flag to false to connect anyway.

Data access is governed by the portal toggles, not by these flags: this server reads everything over the REST API, which Discord gates on the portal setting alone. So with the portal toggles on, setting these flags to false loses nothing. With a portal toggle off, the corresponding data is restricted regardless of the flags: message bodies come back empty (content, embeds, attachments; except the bot's own messages, DMs, and messages that mention the bot) and member listing fails; enable the toggle in the portal to restore it.

Toolsets (DISCORD_MCP_TOOLSETS): discovery, messages, channels, permissions, members, roles, moderation, screening, stats, forums, webhooks, scheduled_events, invites, dm. Example; DISCORD_MCP_TOOLSETS=discovery,messages,members exposes only the discovery, message, and member tools. Note: a toolset ships its whole module, including its destructive tools (messages includes bulk delete; members includes kick/ban); use DISCORD_ALLOWED_GUILDS and the dry-run defaults to bound them. Only the listed toolsets' tools are advertised and callable. Unknown names make the server fail at startup instead of silently exposing everything (an empty value counts as unset and exposes all).

Creating Your Discord Bot

1. Go to discord.com/developers/applications

2. New Application > give it a name

3. Bot tab > Reset Token > copy the token

4. Enable Privileged Gateway Intents (this server requests both by default, but new Discord apps have the portal toggles OFF):

   • Server Members Intent
   • Message Content Intent

   Important: if the bot requests a privileged intent that is not enabled here, Discord closes the connection with code 4014 and every tool call fails. Enable both, or stop requesting the ones you don't need via the environment variables above.

5. OAuth2 > URL Generator:

   • Scopes: bot
   • Permissions: Send Messages, Read Message History, Manage Channels, Manage Roles, Kick Members, Ban Members, Moderate Members, View Audit Log, Manage Messages, Manage Threads, Add Reactions, Manage Guild, Manage Webhooks, Manage Events, Create Events, Create Instant Invite, Manage Nicknames, Pin Messages, Embed Links, Create Public Threads, Send Messages in Threads

6. Copy the generated URL and invite the bot to your server

Available Tools (99)

Discovery & Navigation (4 tools)

Messages (20 tools)

Channels (8 tools)

Channel Permissions (6 tools)

Members (11 tools)

Roles (9 tools)

Forums (10 tools)

Webhooks (8 tools)

Scheduled Events (7 tools)

Direct Messages (7 tools)

Invites (5 tools)

Moderation & Screening (3 tools)

Stats (1 tool)

Usage Examples

"List all servers the bot is in"
"Read the last 10 messages in #general"
"Send 'Hello everyone!' to the announcements channel"
"Create a forum channel called 'feedback' with tags Bug, Feature, Question"
"Show the full permission audit for the server"
"Create a webhook on #notifications and send a test message"
"Ban user 112233445566778899 and delete their messages from the last 3 days"
"Create an event called 'Game Night' for next Friday at 8pm"
"List all upcoming events in the server"
"Create a permanent invite for #general"
"List all active invites and delete expired ones"
"Send a DM to user 112233445566778899 saying 'Your build passed!'"
"Search for members named 'john'"
"List all banned users in the server"
"Show all pinned messages in #general"
"Forward that message to #announcements"

Finding Discord IDs

Enable Developer Mode in Discord: Settings > Advanced > Developer Mode

Then right-click on a server, channel, or user > Copy ID.

Project Structure

discord-mcp/
├── src/
│   ├── index.ts             ← Entry point (MCP server + transport)
│   ├── client.ts            ← Discord client + shared helpers
│   ├── constants.ts         ← Shared constants (limits, defaults)
│   ├── embeds.ts            ← Shared embed schema + builder
│   └── tools/
│       ├── index.ts         ← Tool registry (toolset gating, dispatch)
│       ├── define.ts        ← defineTool/defineModule + shared zod fields
│       ├── types.ts         ← Shared TypeScript interfaces
│       ├── discovery.ts     ← Guild/channel discovery
│       ├── messages.ts      ← Message CRUD, reactions, threads, embeds
│       ├── channels.ts      ← Channel management
│       ├── permissions.ts   ← Permission overwrites
│       ├── members.ts       ← Member management
│       ├── roles.ts         ← Role CRUD and assignment
│       ├── moderation.ts    ← Audit log
│       ├── screening.ts     ← Membership screening
│       ├── stats.ts         ← Server statistics
│       ├── forums.ts        ← Forum channels, posts, tags
│       ├── webhooks.ts      ← Webhook management
│       ├── scheduledEvents.ts ← Scheduled events
│       ├── invites.ts        ← Invite management
│       └── dm.ts             ← Direct messages
├── test/                     ← node:test suite (schemas, gating, allow-list)
├── scripts/                  ← sync-version.js (npm version hook)
├── .github/workflows/        ← CI/CD (build check + auto release)
├── Dockerfile
├── .dockerignore
├── .env.example
├── package.json
├── tsconfig.json
├── CHANGELOG.md
├── CONTRIBUTING.md
├── SECURITY.md
└── README.md

Adding a new tool

1. Create a new file in src/tools/ (e.g. events.ts)
2. Declare each tool with defineTool({ name, description, annotations, schema, handle }) and export defineModule([...]) as the default
3. Import it and add it to allToolsets in src/tools/index.ts (the key is its DISCORD_MCP_TOOLSETS name)

Security

• Never commit your Discord token to Git
• Use environment variables or a .env file (not versioned)
• Give the bot only the permissions it needs
• Restrict the server to specific servers with DISCORD_ALLOWED_GUILDS
• Irreversible mass actions (bulk_ban, prune_members, bulk_delete_messages, delete_channel) default to a dry_run preview; pass dry_run:false to apply

Contributing

Contributions are welcome!

1. Fork the repository
2. Create a feature branch (git checkout -b feature/my-feature)
3. Follow the modular structure, see Adding a new tool
4. Commit your changes and open a pull request

License

MIT, see LICENSE for details.