mcp-discord

Provides an MCP server that exposes Discord bot capabilities (server/channel/member lookup, message read/send, reactions, and basic moderation/role management) to MCP clients such as Claude Desktop.

Evaluated Mar 30, 2026 (21d ago)

Repo ↗ Communication mcp discord agents moderation messaging python

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Uses a Discord bot token provided via environment variable (better than hardcoding). However, the provided materials do not describe MCP-side authentication/authorization, fine-grained tool scopes, secure transport guarantees for the MCP process, nor explicit guidance on logging/handling failures. Discord bot permissions/intents must be minimized to reduce blast radius for send/moderate/role actions.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You control the Discord bot permissions and want an agent to use MCP tools to perform Discord actions (read/act) in a specific server.

Avoid When

You need fully specified API/error/retry semantics for reliable automation, or you cannot limit bot intents/permissions to the minimum required.

Use Cases

• Let an AI agent inspect Discord servers, channels, members, and users
• Enable agents to send messages or add/remove reactions in a controlled Discord bot context
• Support agent workflows for moderating messages (delete/timeout) and managing roles
• Automate routine community operations by connecting MCP tooling to Discord

Not For

• Handling sensitive or regulated workflows without additional safeguards/auditing
• Production environments that require strong, documented operational guarantees (SLA, rate-limit contracts, idempotency semantics)
• Use-cases where least-privilege and scope-limited permissions can’t be ensured on the Discord bot

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: Discord bot token via DISCORD_TOKEN environment variable

OAuth: No Scopes: No

Authentication is implicit via the Discord bot token. The README instructs enabling Discord privileged intents and inviting the bot via OAuth2, but does not describe fine-grained MCP-side scopes.

Pricing

Free tier: No

Requires CC: No

Open-source MIT package; no usage-based pricing described in the provided materials.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Discord operations can be destructive (send/moderate/delete); agents should implement confirmation and safety checks
⚠ Privileged intents and permissions may be required; insufficient permissions will cause tool failures
⚠ Message history reading is limited to 'recent' messages; agents expecting full history may fail

Alternatives

Use a custom MCP server wrapping the Discord API directly with your own permission model Use Discord bots directly (discord.py) and implement agent interaction via function calling without MCP Other MCP Discord/community integrations (if available) with stronger documented contracts

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-discord.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-30.