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
Run: npx -y @smithery/cli@latest install @SaseQ/discord-mcp --client claude
Verify installation: claude mcp list
Test connection: claude mcp status discord
Claude Desktop
Install via Smithery CLI: npx -y @smithery/cli@latest install @SaseQ/discord-mcp --client claude
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.
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.
[](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).
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.
MCP server for Microsoft Teams channel workflows, including reading threads, posting new threads, replying to threads, mentioning members, and listing team members.
✓Use 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 notes
✓Discord 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