Skip to main content
mcpFirst-partyLow risk Safety Privacy
Discord logo

Discord MCP Server for Claude

Discord bot integration for community management, moderation, and server automation

by saseq·added 2025-09-20·
HarnessClaude CodeClaude Desktop

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Brand
Discord
Brand domain
discord.com
Brand asset source
brandfetch
Package URL
/downloads/mcp/discord-mcp-server.mcpb
Package SHA256
c533512b60c880469d414d1eb89751df1f7d9db580d53b73f22b5cbb0b696275
Safety notes
Use least-privilege bot permissions and test moderation or message-writing actions in a non-critical server first.
Privacy notes
Discord messages, channel names, user IDs, member metadata, and server configuration may be sent through model context.
Author
saseq
Claim status
unclaimed
Last verified
2025-09-20

Decision playbook

Ready to evaluate for your workflow

Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.

Compare context
Selected

0

Current score

96

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as first-party.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Complete

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    Package marked verified.

    Done
  • Checksum metadata

    SHA-256 hash is present.

    Done

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Package install

Copy-ready — paste the snippet to get started.

3 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

10 to clear

Platforms

2 listed

Difficulty

0/100

Adoption plan

Balanced adoption plan

Current risk score 0/100. Use staged verification before broader rollout.

Risk 0

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    Package verification/checksum metadata is available.

    Done

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (6/6 signals complete).

Risk 0

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Present

Package integrity metadata is present.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

6/6 steps complete with no blocking gaps for this preset.

Risk 0

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is available.

Done

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

10 prerequisites to line up before setup. Have accounts and credentials ready first.

0/10 ready
Account & credentials3Install & runtime2Configuration3Network & hosting23 minutes

Safety & privacy surface

Safety & privacy surface

1 safety and 1 privacy notes across 2 risk areas. Review closely: permissions & scopes.

2 areas
  • SafetyPermissions & scopesUse least-privilege bot permissions and test moderation or message-writing actions in a non-critical server first.
  • PrivacyGeneralDiscord messages, channel names, user IDs, member metadata, and server configuration may be sent through model context.

Safety notes

  • Use least-privilege bot permissions and test moderation or message-writing actions in a non-critical server first.

Privacy notes

  • Discord messages, channel names, user IDs, member metadata, and server configuration may be sent through model context.

Prerequisites

  • Discord account with Developer Portal access (https://discord.com/developers/applications)
  • Discord bot application created in Discord Developer Portal
  • Discord bot token (obtained from Discord Developer Portal - Bot section)
  • Discord Guild ID (optional, for default server targeting - found in Discord server settings)
  • Java JDK 11 or higher installed (run java -version to verify)
  • Node.js and npm/npx available for running Smithery CLI installation
  • Internet connection for accessing Discord API (https://discord.com/api endpoints)
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • Rate limit awareness: 50 requests per second (most endpoints), implement request queuing (4 requests per 100ms = 40/second)
  • Understanding of Discord bot permissions and OAuth scopes (bot, send_messages, manage_channels, manage_roles) and absolute path to JAR file

Schema details

Install type
package
Reading time
1 min
Difficulty score
0
Troubleshooting
Yes
Breaking changes
No
Source repository stats
Scope
Source repo
Package metadata
Package verified
Yes
SHA-256
c533512b60c880469d414d1eb89751df1f7d9db580d53b73f22b5cbb0b696275
Collection metadata
Estimated setup
3 minutes
Difficulty
intermediate
Full copyable content
{
  "discord-mcp": {
    "env": {
      "DISCORD_TOKEN": "${DISCORD_TOKEN}",
      "DISCORD_GUILD_ID": "${DISCORD_GUILD_ID}"
    },
    "args": [
      "-jar",
      "/absolute/path/to/discord-mcp-0.0.1-SNAPSHOT.jar"
    ],
    "command": "java"
  }
}

About this resource

Content

Enable your AI assistants to seamlessly interact with Discord servers through comprehensive bot functionality and automation capabilities.

Features

  • Server information retrieval
  • Channel management and creation
  • Category organization
  • Message operations
  • Member management
  • Role administration
  • Advanced Discord server and channel management with message handling, user management, and bot integration features
  • Batch operations support for efficient bulk message operations, channel management, and user actions with automatic rate limit handling and retry logic
  • Real-time event synchronization capabilities with webhook integration support for monitoring Discord events and triggering automated workflows

Use Cases

  • Automated server moderation and management
  • Community engagement and member onboarding
  • Channel organization and content management
  • Bot-driven notifications and alerts
  • Member role management and permissions
  • Build automated Discord bot workflows that sync external systems with Discord servers for real-time communication and community management

Installation

Claude Code

  1. Run: npx -y @smithery/cli@latest install @SaseQ/discord-mcp --client claude
  2. Verify installation: claude mcp list
  3. Test connection: claude mcp status discord

Claude Desktop

  1. Install via Smithery CLI: npx -y @smithery/cli@latest install @SaseQ/discord-mcp --client claude
  2. Create a Discord bot application
  3. Get your Discord bot token
  4. Configure the MCP server with your bot token
  5. Restart Claude Desktop

Requirements

  • Discord account with Developer Portal access (https://discord.com/developers/applications)
  • Discord bot application created in Discord Developer Portal
  • Discord bot token (obtained from Discord Developer Portal - Bot section)
  • Discord Guild ID (optional, for default server targeting - found in Discord server settings)
  • Java JDK 11 or higher installed (run java -version to verify)
  • Node.js and npm/npx available for running Smithery CLI installation
  • Internet connection for accessing Discord API (https://discord.com/api endpoints)
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • Rate limit awareness: 50 requests per second (most endpoints), implement request queuing (4 requests per 100ms = 40/second)
  • Understanding of Discord bot permissions and OAuth scopes (bot, send_messages, manage_channels, manage_roles) and absolute path to JAR file

Configuration

{
  "discord-mcp": {
    "env": {
      "DISCORD_TOKEN": "${DISCORD_TOKEN}",
      "DISCORD_GUILD_ID": "${DISCORD_GUILD_ID}"
    },
    "args": ["-jar", "/absolute/path/to/discord-mcp-0.0.1-SNAPSHOT.jar"],
    "command": "java"
  }
}

Examples

Get server information and member count

Common usage pattern for this MCP server

Ask Claude: "Get server information and member count"

Create new text channels and categories

Common usage pattern for this MCP server

Ask Claude: "Create new text channels and categories"

Manage member roles and permissions

Common usage pattern for this MCP server

Ask Claude: "Manage member roles and permissions"

Retrieve channel lists and configurations

Common usage pattern for this MCP server

Ask Claude: "Retrieve channel lists and configurations"

Send Message to Channel

Send a message to a Discord channel with embed content

// Send message to Discord channel
const message = await discord.channels.createMessage({
  channel_id: "channel-id",
  content: "Hello from Claude!",
  embeds: [
    {
      title: "Notification",
      description: "This is a test message",
      color: 0x00ff00,
    },
  ],
});

Security

  • Bot token authentication required
  • Guild-specific permissions
  • Configurable access controls
  • Secure Discord API integration
  • Discord bot tokens and OAuth access tokens must be securely stored and never exposed in client-side code or public repositories - use environment variables and secure credential management
  • Discord bot tokens should be scoped with minimal required permissions following the principle of least privilege - regularly audit bot permissions and remove unused permissions
  • Discord server, channel, and user IDs may expose community structure and member information - ensure Discord resource IDs are kept private and not shared in public configurations
  • Rate limiting and API quota management are critical for Discord MCP servers - implement proper rate limit handling, retry logic, and quota monitoring to prevent service disruption
  • Discord webhook configurations and payloads may contain sensitive message content and user data - ensure webhook endpoints are properly secured with authentication and HTTPS encryption

Troubleshooting

HTTP 429 rate limit error when sending messages

Discord limits 50 requests per second most endpoints. Check X-RateLimit headers for specific bucket limits. Implement request queuing with 4 requests per 100ms (40/second) to avoid throttling.

Bot gets 24-hour IP ban for invalid requests

IP addresses making 10,000+ invalid HTTP requests per 10 minutes are banned for 24 hours. Fix 401/403 errors in your code, implement proper error handling, validate requests before sending.

Bot token authentication fails with 401 error

Regenerate bot token from Discord Developer Portal. Verify DISCORD_TOKEN environment variable is set correctly. Ensure token includes Bot prefix in Authorization header: Bot YOUR_TOKEN.

Cannot access guild channels or members

Verify bot has required permissions in Discord server settings. Check DISCORD_GUILD_ID matches target server. Ensure bot has been invited with correct OAuth scopes (bot, send_messages, manage_channels, manage_roles).

Java runtime error or MCP server won't start

Install Java JDK 11 or higher. Run java -version to verify installation. Check JAR file path is absolute and file exists. Verify execute permissions on JAR file.

Discord MCP server authentication errors with bot tokens

Verify bot token is valid and not expired. Check bot permissions match required operations. Ensure token format is correct (Bot token prefix). For OAuth integrations, verify token refresh logic is working correctly.

Discord rate limit errors when sending multiple messages

Implement exponential backoff retry logic with jitter. Use Discord API rate limit headers to monitor usage. Reduce concurrent requests. Cache frequently accessed channel data. Discord allows 5 requests per 5 seconds per route.

Discord channel or server access denied errors

Verify bot has access to the server and channels. Check bot permissions and server membership. Ensure bot has required permissions (Send Messages, Read Message History, etc.) for target operations.

Discord MCP server connection timeouts or network errors

Check network connectivity and firewall settings. Verify Discord API endpoints are accessible. Increase request timeout values. Implement connection pooling and retry mechanisms with exponential backoff.

Source citations

Add this badge to your README

Show that Discord MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/discord-mcp-server.svg)](https://heyclau.de/entry/mcp/discord-mcp-server)

How it compares

Discord MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

2 trust signals differ across this comparison (Package trust, Submitter).

Field

Discord bot integration for community management, moderation, and server automation

Open dossier

Official LINE MCP server that connects Claude and other AI agents to the LINE Messaging API for push messages, broadcasts, profile lookup, quotas, follower IDs, and rich-menu management.

Open dossier

MCP server that lets Claude use an authenticated LinkedIn browser session to inspect profiles, companies, jobs, feeds, inboxes, and conversations.

Open dossier

MCP server for Microsoft Teams channel workflows, including reading threads, posting new threads, replying to threads, mentioning members, and listing team members.

Open dossier
Next steps
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustDiffersPackage verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffersoktofeesh1oktofeesh1oktofeesh1
Install riskLow riskReview firstReview firstReview first
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
BrandDiscord logoDiscordLINE Bot MCP Server logoLINE Bot MCP Server
Categorymcpmcpmcpmcp
Sourcefirst-partysource-backedsource-backedsource-backed
AuthorsaseqLINEDaniel StickerInditexTech
Added2025-09-202026-06-062026-06-052026-06-06
Platforms
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo
Safety notesUse least-privilege bot permissions and test moderation or message-writing actions in a non-critical server first.LINE Bot MCP Server can push text and flex messages to users, broadcast messages to all followers, retrieve follower IDs, inspect profiles, check message quotas, create rich menus, set default rich menus, cancel defaults, and delete rich menus. Broadcast and rich-menu tools can affect every user following the connected LINE Official Account, so require human approval before running them in production. Push-message tools can contact individual users directly; confirm the target `userId`, message body, and account context before sending. Rich-menu tools can upload generated menu images and change user-facing navigation for the account. Use least-privilege channel tokens where possible, keep test and production LINE accounts separate, and monitor quota consumption. The upstream README marks the project as a preview version for experimental use with potentially incomplete functionality or support.LinkedIn MCP Server uses browser automation against an authenticated LinkedIn account. Tools can read profile, company, job, feed, inbox, and conversation data available to the authenticated session. Some tools can initiate social or messaging actions, such as sending messages or connection requests, so require explicit human confirmation before any account-write action. The server stores browser profile state locally and provides logout/profile management options that can clear authentication state. Respect LinkedIn account rules, rate limits, consent boundaries, and workplace policies before scraping, messaging, or automating professional-network workflows.MCP Teams Server can start new channel threads, reply to existing threads, mention members, read thread replies, list channel threads, look up members by name, and list team members. Posting or replying in Microsoft Teams can notify real teammates and create persistent workplace records. Mentioning a member can trigger direct notifications, so require human review before allowing model-generated mentions. Channel read tools can expose existing conversations, replies, message IDs, pagination cursors, and team member context to the model. The required Microsoft Graph permission includes ChannelMessage.Read.All resource-specific consent, and Teams app permissions include message send/read and member read scopes. Use a dedicated bot application, scoped Team ID, scoped Channel ID, least-privilege permissions, and explicit approval for every write operation. Launch with `uvx --from git+https://github.com/InditexTech/mcp-teams-server mcp-teams-server` or from a verified checkout; do not use plain `uv run mcp-teams-server` from untrusted workspaces because local projects, virtual environments, or PATH entries can hijack the executable while receiving Teams secrets.
Privacy notesDiscord messages, channel names, user IDs, member metadata, and server configuration may be sent through model context.Channel access tokens, destination user IDs, follower IDs, profile display names, profile picture URLs, status messages, language, message contents, flex-message JSON, and rich-menu IDs can be exposed to the MCP client. Broadcast prompts, generated messages, user IDs, and profile results may be retained in MCP client logs, terminal history, model context, or chat transcripts. Treat LINE Official Account credentials and recipient identifiers as secrets, and avoid pasting real tokens or user IDs into shared logs. Review LINE platform policies and internal consent requirements before retrieving follower IDs or using AI-generated outbound messages.LinkedIn profile data, search queries, company data, job details, inbox metadata, conversation text, feed posts, messages, connection notes, browser cookies, prompts, and tool outputs may be visible to the MCP client and model provider. LinkedIn data can include personal information, employment history, contact details, recruiting plans, sales targets, private messages, and relationship context. Treat the persisted browser profile as sensitive account state and avoid exposing it through logs, screenshots, shared volumes, or untrusted containers.Teams channels can contain customer data, employee names, emails, incident details, roadmap discussions, support conversations, credentials, links, and confidential attachments or references. Tool calls and logs can expose TEAMS_APP_ID, tenant IDs, team IDs, channel IDs, thread IDs, message IDs, member names, member emails, message bodies, replies, mentions, and pagination cursors. TEAMS_APP_PASSWORD, client secrets, tenant IDs, bot configuration, and `.env` files should stay out of prompts, issues, logs, screenshots, and committed files. Claude-generated messages may become discoverable records under organization retention, compliance, and eDiscovery policies.
Prerequisites
  • Discord account with Developer Portal access (https://discord.com/developers/applications)
  • Discord bot application created in Discord Developer Portal
  • Discord bot token (obtained from Discord Developer Portal - Bot section)
  • Discord Guild ID (optional, for default server targeting - found in Discord server settings)
  • Node.js 22 or newer for the published npm package.
  • A LINE Official Account with the Messaging API enabled.
  • A LINE channel access token with the permissions needed for the intended tools.
  • A destination user ID when using the default recipient flow for push-message tools.
  • Python 3.12 through 3.14 available to the MCP client runtime.
  • uvx available for package execution.
  • LinkedIn account access for the workflows you want Claude to perform.
  • One-time browser login, including any LinkedIn two-factor, mobile confirmation, or captcha challenge.
  • Python 3.10 and uv/uvx available to the MCP client runtime.
  • Microsoft Teams account and a Team/Channel where the bot app is installed.
  • Microsoft Entra ID application registration with client secret credentials.
  • Azure Bot registration connected to the Microsoft Teams channel.
Install
npx -y @smithery/cli@latest install @SaseQ/discord-mcp --client claude && claude mcp list
npx -y @line/line-bot-mcp-server
uvx linkedin-scraper-mcp@latest
uvx --from git+https://github.com/InditexTech/mcp-teams-server mcp-teams-server
Config
Manual-only setup:
{
  "discord-mcp": {
    "env": {
      "DISCORD_TOKEN": "${DISCORD_TOKEN}",
      "DISCORD_GUILD_ID": "${DISCORD_GUILD_ID}"
    },
    "args": [
      "-jar",
      "/absolute/path/to/discord-mcp-0.0.1-SNAPSHOT.jar"
    ],
    "command": "java"
  }
}
Manual-only setup:
claude mcp add line-bot --env CHANNEL_ACCESS_TOKEN=YOUR_CHANNEL_ACCESS_TOKEN -- npx -y @line/line-bot-mcp-server
{
  "mcpServers": {
    "linkedin": {
      "command": "uvx",
      "args": ["linkedin-scraper-mcp@latest"],
      "env": {
        "UV_HTTP_TIMEOUT": "300"
      }
    }
  }
}
{
  "mcpServers": {
    "msteams": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/InditexTech/mcp-teams-server", "mcp-teams-server"],
      "env": {
        "TEAMS_APP_ID": "<entra-app-id>",
        "TEAMS_APP_PASSWORD": "<client-secret>",
        "TEAMS_APP_TYPE": "SingleTenant",
        "TEAMS_APP_TENANT_ID": "<tenant-id>",
        "TEAM_ID": "<team-id>",
        "TEAMS_CHANNEL_ID": "<channel-id>"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.