Discord MCP Server Setup for Cursor IDE (2026)

Connecting Discord to Cursor over MCP requires a Discord bot application (not your personal account), a bot token added to your mcp.json, and the bot invited into the server you want the AI to read from or post to. Once that's done, Cursor can pull recent messages, search channel history, and post updates without you copying anything out of the Discord app.

This is most useful for teams that run engineering or on-call coordination through Discord rather than Slack — release notes, incident threads, and support channels all become something the AI can query directly.

What the Discord MCP Server Can Do

Once connected, depending on the bot's permissions, Cursor can typically:

It cannot see anything in a server (or channel) the bot hasn't been explicitly invited into — Discord's permission model is scoped per-server, not account-wide, which is different from how a personal-access-token integration like GitHub or GitLab works.

When to Use This (and When Not To)

This is a good fit for read-mostly workflows: pulling incident context into a coding session, summarizing a support channel before triaging bugs, or checking whether a deploy announcement already went out. It's a worse fit as your only audit trail for anything sensitive — bot tokens are broad credentials, and if the token leaks, whoever has it can read and post in every channel the bot was added to. Don't add the bot to channels it doesn't need, and don't grant Administrator just to avoid thinking about permissions individually.

Prerequisites

Step 1: Create a Discord Application and Bot

1. Go to the Discord Developer Portal
2. Click New Application, give it a name like cursor-mcp-bot
3. In the left sidebar, go to Bot → click Add Bot (or Reset Token if a bot already exists)
4. Under Privileged Gateway Intents, enable Message Content Intent — without this, the bot can see that a message exists but not its text
5. Click Reset Token and copy the bot token immediately — Discord only shows it once

Step 2: Invite the Bot to Your Server

1. In the Developer Portal, go to OAuth2 → URL Generator
2. Under Scopes, check bot
3. Under Bot Permissions, select only what you need — at minimum Read Message History and View Channels; add Send Messages if you want the AI to post
4. Copy the generated URL, open it in a browser, and select the server to add the bot to

Avoid checking Administrator here. It's tempting because it "just works," but it also means a leaked token compromises the entire server, not just a few channels.

Step 3: Add the Bot Token to Your MCP Config

Open ~/.cursor/mcp.json (or Settings → MCP in Cursor):

{
  "mcpServers": {
    "discord": {
      "command": "npx",
      "args": ["-y", "discord-mcp-server"],
      "env": {
        "DISCORD_BOT_TOKEN": "your-bot-token-here",
        "DISCORD_DEFAULT_GUILD_ID": "your-server-id"
      }
    }
  }
}

DISCORD_DEFAULT_GUILD_ID is optional — it saves you from specifying which server you mean on every request if you're only connecting to one. As with other less-standardized integrations, search npm for discord-mcp or mcp-server-discord and check which package is actively maintained before locking it into a shared config — naming in this part of the ecosystem isn't as settled as it is for GitHub or Slack.

To find your server ID: enable Developer Mode in Discord (User Settings → Advanced), then right-click the server icon and choose Copy Server ID.

Restart Cursor completely after saving the config.

Step 4: Test the Connection

In Cursor chat, try:

List the channels in this Discord server

Then something that requires actual message content:

Summarize the last 20 messages in the #incidents channel

If real channel names and messages come back, the bot is connected and has the right intents enabled. If channels list but messages don't, the Message Content Intent from Step 1 is the most likely gap.

Practical Workflows

Incident triage

Summarize what's been posted in #incidents in the last hour and tell me if anyone identified a root cause yet

Pre-deploy check

Search #deploys for any mention of the payments-service in the last 2 days

Turning a thread into a ticket

Read the bug report thread in #support started by user @jsmith and turn it into a structured bug report I can paste into Jira

Posting a status update

Post a message in #engineering saying the database migration finished successfully and the app is back to normal

Only wire up posting if the bot's permissions include Send Messages in that channel — otherwise this fails silently or with a permission error, not a crash.

Troubleshooting

Bot appears offline in Discord
The MCP server needs to be actively running for the bot to show online — if you're not mid-Cursor-session, the bot may appear offline even though the config is correct. This is expected for most local MCP setups (the process only runs while your IDE needs it).

"Missing Access" or messages not returning
Check two things: the bot has actually been invited to that specific server (Step 2), and it has been given access to that specific channel if the channel has restricted permissions. Server-wide bot permissions don't override a channel that explicitly excludes the bot's role.

Messages list but content is empty or redacted
This is almost always the Message Content Intent not being enabled in the Developer Portal (Step 1). It's a common miss because the bot still connects successfully without it — it just can't read text.

"401 Unauthorized" on startup
The bot token is wrong, was regenerated since you copied it, or has stray whitespace. Regenerate the token in the Developer Portal and update mcp.json.

Server doesn't show in Cursor after config changes
Fully quit and reopen Cursor rather than just reloading the window. Check View → Output → MCP for the actual startup error if it still doesn't appear.

Frequently Asked Questions

Q: Do I need a paid Discord plan or Nitro to do this?
A: No. Creating a bot application and inviting it to a server is free and doesn't require any Discord subscription — Nitro is unrelated to bot/API access.

Q: Can the AI read direct messages, or only server channels?
A: By default, bots only see messages in servers they've been invited to and channels they can view — not personal DMs between other users. A bot can receive DMs sent directly to it, but that's a different, narrower capability than reading a server's channels.

Q: What happens if I add the bot to the wrong server by mistake?
A: Remove it from Server Settings → Members, or revoke and regenerate the bot token if you're worried about exposure — that immediately invalidates the old token everywhere it was used.

Q: Can one bot token be used across multiple Discord servers?
A: Yes — a single bot can be invited to multiple servers, and the same token authenticates it everywhere it's a member. Use DISCORD_DEFAULT_GUILD_ID (or specify the server by name in your prompt) to disambiguate which one you mean when the bot is in more than one.

Q: Is this the same as Discord's official API, or a workaround?
A: It's a thin MCP wrapper around Discord's standard bot API (the same one used by moderation bots, music bots, etc.) — not a special or unofficial access path. Anything the underlying bot permissions allow through Discord's normal API, the MCP server can expose to your AI.

Related Guides

---