Discord MCP Server: Setup Guide, Use Cases & Limitations

What Is Discord MCP Server?

Discord MCP Server (mcp-discord) is an MCP server that lets Claude read messages, list channels, and post to Discord servers. It is maintained by v-3 on GitHub.

Quick Facts

What You Can Do With It

• Read messages: Retrieve message history from specific Discord channels via Claude.
• List channels: Query available channels within a Discord server to surface structure and organization.
• Post messages: Send messages to a Discord channel directly through Claude prompts.
• Server monitoring: Watch channel activity and pull recent messages to track what’s happening in a server.
• Community management: Automate routine tasks like checking for messages that need responses or auditing channel content.

How to Set It Up

Prerequisites: You need a Discord bot token with appropriate permissions (read messages, send messages) and the bot added to your target server.

Step 1 — Install the package

npx mcp-discord
**Step 2 — Configure Claude Desktop**

Add the server to your `claude_desktop_config.json` (typically at `~/Library/Application Support/Claude/claude_desktop_config.json` on macOS):

```json
{
  "mcpServers": {
    "discord": {
      "command": "npx",
      "args": ["mcp-discord"],
      "env": {
        "DISCORD_TOKEN": "your-bot-token-here"
      }
    }
  }
}

Step 3 — Configure Claude Code

For Claude Code, add to .claude/mcp.json in your project root:

{
  "mcpServers": {
    "discord": {
      "command": "npx",
      "args": ["mcp-discord"],
      "env": {
        "DISCORD_TOKEN": "your-bot-token-here"
      }
    }
  }
}

Restart Claude Desktop or reload your Claude Code session after saving the config.

Works Best With

This server is compatible with both Claude Desktop and Claude Code. Claude Desktop is the more natural fit for interactive community management tasks — reading threads, drafting replies, and monitoring channels ad hoc. Claude Code is useful when Discord interactions are part of a larger automated workflow, such as posting build notifications or querying server state during a development session.

Known Limitations

• Bot token required: You must create a Discord application and bot via the Discord Developer Portal. The bot must be manually invited to any server you want to interact with, with the correct permission scopes granted.
• Permission scope matters: If the bot lacks Read Message History or Send Messages permissions in a specific channel, those operations will fail silently or return errors.
• Discord API rate limits apply: Discord enforces per-route rate limits. Heavy polling or bulk message reads may trigger throttling.
• No webhook support documented: The server works through bot authentication, not incoming webhooks — keep this in mind for one-way notification use cases.
• Server ID and channel ID required: Most operations require you to know your Discord server (guild) ID and channel IDs in advance; there is no built-in discovery flow beyond channel listing.

Community Resources

• GitHub repository: https://github.com/v-3/discordmcp
• Issues and bug reports: https://github.com/v-3/discordmcp/issues
• MCP community discussions: r/ClaudeAI on Reddit — search “Discord MCP” for community threads
• Anthropic MCP reference: https://modelcontextprotocol.io