Install command
Provided
Discord bot integration for community management, moderation, and server automation
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.
0
96
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as first-party.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
Package marked verified.
Checksum metadata
SHA-256 hash is present.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Install command
Provided
Config snippet
Provided
Copy snippet
Provided
Prerequisites
10 to clear
Platforms
2 listed
Difficulty
0/100
Adoption plan
Current risk score 0/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
Package verification/checksum metadata is available.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (6/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is present.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
6/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is available.
rollout
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
10 prerequisites to line up before setup. Have accounts and credentials ready first.
Safety & privacy surface
1 safety and 1 privacy notes across 2 risk areas. Review closely: permissions & scopes.
{
"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"
}
}Enable your AI assistants to seamlessly interact with Discord servers through comprehensive bot functionality and automation capabilities.
{
"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"
}
}
Common usage pattern for this MCP server
Ask Claude: "Get server information and member count"
Common usage pattern for this MCP server
Ask Claude: "Create new text channels and categories"
Common usage pattern for this MCP server
Ask Claude: "Manage member roles and permissions"
Common usage pattern for this MCP server
Ask Claude: "Retrieve channel lists and configurations"
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,
},
],
});
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.
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.
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.
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).
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.
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.
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.
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.
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.
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 status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trustDiffers | Package verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| SubmitterDiffers | — | oktofeesh1 | oktofeesh1 | oktofeesh1 |
| Install risk | Low risk | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | ||
| Category | mcp | mcp | mcp | mcp |
| Source | first-party | source-backed | source-backed | source-backed |
| Author | saseq | LINE | Daniel Sticker | InditexTech |
| Added | 2025-09-20 | 2026-06-06 | 2026-06-05 | 2026-06-06 |
| Platforms | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓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 |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.