Discord

Read and post in Discord servers and DMs.

Works with: Claude DesktopCursor
Quick install
npx -y discord-mcp

How to install the Discord MCP server

Add this to your Claude Desktop MCP configuration:

{
  "mcpServers": {
    "discord": {
      "command": "npx",
      "args": [
        "-y",
        "discord-mcp"
      ]
    }
  }
}

Add this to your Cursor MCP configuration:

{
  "mcpServers": {
    "discord": {
      "command": "npx",
      "args": [
        "-y",
        "discord-mcp"
      ]
    }
  }
}

The Discord MCP server gives Claude bot-based access to your Discord servers. Read channel history, search messages, post replies, manage threads. For anyone running a community on Discord, this turns moderation and content workflows into prompts.

The community servers all follow the same pattern: spin up a Discord bot, configure its permissions, point the MCP server at its token. The setup is more involved than other servers but the payoff is significant if Discord is where your community lives.

Why use it

Community management on Discord is mostly observation and response. Skim recent activity, spot what needs a reply, post something useful, repeat. The MCP server collapses the observation step. Claude can summarise the last 24 hours in any channel, surface unanswered questions, find threads that need a moderator response.

For founders running paid Discord communities or open-source projects with a Discord presence, this is the closest thing to having a community manager review the server every morning.

What it actually does

Channel ops: list channels, read recent messages, fetch thread history, search messages by query or user. Posting: send messages to channels, reply in threads, react with emoji. Member ops: list members, fetch user info. Server ops: list servers (guilds) the bot is in, manage roles (with the right permissions).

Practical patterns:

  • “Summarise the last 24 hours in #help. Highlight any unanswered questions.”
  • “Find every message in this server that mentions ‘pricing’ from the last week.”
  • “Post the weekly changelog to #announcements with these bullets.”

Gotchas

Bot tokens are sensitive. Store them as environment variables and don’t commit them. Discord auto-revokes tokens that get pushed to public repos but it can take hours.

Channel history is paginated and slow for large servers. Claude can fetch the most recent messages quickly but querying across months of history will take a while. For long-range queries, consider piping Discord exports to a Postgres or SQLite database and querying that instead.

Pair with Slack if you run a community on both. Claude can read both, summarise across them, and post relevant content to either. For founders running both customer support on Discord and team chat on Slack, this is a useful unification.

For a complete community-management stack, add Notion or Linear so Claude can promote useful Discord questions into a structured FAQ or issue tracker.

Discord MCP server: FAQs

Is the Discord MCP server official?

No. Discord hasn't shipped a first-party server. The community implementations are bot-based: you create a Discord bot, give it the right permissions, and the MCP server uses its token to interact with the API.

What permissions does the bot need?

At minimum, View Channels and Read Message History for the channels you want Claude to access. Add Send Messages if you want Claude to post. Avoid giving Administrator or Manage Roles unless you specifically need them.

Can it read DMs?

Bots can only read DMs they're explicitly involved in. The MCP server can read messages sent to the bot directly, but it cannot read DMs between two human users (Discord's API forbids this entirely).

Can it search across servers?

Yes, if the bot is a member of multiple servers. Claude can query each one and synthesise across them. Useful for moderators or community managers running multiple Discords.

Will Discord rate-limit the bot?

Yes, Discord has tight rate limits, especially for message reads. The server handles 429 responses gracefully but very heavy queries may time out. Don't expect to ingest a year of message history in one prompt.