zed-mcp-server-discord
Provides an MCP (Model Context Protocol) server integration for Zed that exposes Discord operations as tools (login, send/read messages, manage channels, manage forum posts, reactions, and webhook operations).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
No README details about TLS requirements, secret storage/handling, OAuth vs bot token, or permission scoping. Presence of login and destructive actions increases risk if credentials or tool usage controls are not implemented carefully. Rate-limit and error semantics are not documented, which can lead to accidental abuse or retry storms.
⚡ Reliability
Best When
You want an agent/IDE workflow to call Discord actions through a consistent MCP tool interface and you can configure Discord credentials/permissions safely.
Avoid When
You need thoroughly documented authentication, rate limiting, and idempotency/retry behavior, or you plan to run the integration in highly restricted security/compliance contexts without additional review.
Use Cases
- • ChatOps-style automations in Zed for Discord (send/read/update messages)
- • Bot-like workflows: create/delete channels and manage forum posts
- • Moderation and enrichment: read messages and add/remove reactions
- • Webhook-driven notifications and message dispatching from Zed
- • Building agent workflows that need structured Discord actions via MCP tools
Not For
- • General-purpose Discord client usage without MCP tooling
- • Use cases requiring strong guarantees of safety/permissions beyond Discord’s own model
- • High-assurance environments where auth scopes, rate limits, and error semantics are not documented
Interface
Authentication
README only lists a 'discord_login' tool; specific auth mechanism (token type, OAuth vs bot token), scopes, and permission model are not documented here.
Pricing
Agent Metadata
Known Gotchas
- ⚠ Discord APIs can have rate limits; without documented limits and headers, agents may retry too aggressively.
- ⚠ Login/session lifecycle is unclear from README; agents may fail if they don’t handle token refresh or session persistence.
- ⚠ Destructive operations (delete channel/message/forum post) may be irreversible; agents need explicit safeguards/confirmation logic.
- ⚠ Some tools (e.g., read messages, forum post retrieval) may require pagination/limits; pagination style is not documented here.
- ⚠ Forum/reaction/webhook behaviors can be permission-sensitive; ensure the Discord app/bot has the required intents/permissions.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for zed-mcp-server-discord.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
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
Scores are editorial opinions as of 2026-04-04.