CommunityAbandoned· 1.4y★ 4.3by v-3

Discord

Read messages, post to channels, manage server members. Useful for community moderators and gamedev teams.

View repo

Safety & Trust

Delv Safety Grade: C

Score 58/100 · assessed 2026-04-28

Maintainer40

Permissions55

Supply chain35

Transparency65

Incidents100

This community-built Discord MCP server connects Claude to Discord's API using a bot token, enabling message reading, channel posting, and member management. The maintainer 'v-3' appears to be a solo developer with limited public profile, raising bus factor concerns. The server requires a Discord bot token with potentially broad permissions depending on how the bot is configured in your Discord workspace. Installation appears to be clone-and-build with no package registry distribution, weakening supply chain assurance. Permissions are moderately scoped to Discord operations but include both read and write capabilities across messages and member management. The functionality is straightforward and well-described, but the combination of a single maintainer, manual installation, and powerful Discord access creates meaningful risk. No known security incidents, but the token-based access model means compromise could expose your entire Discord workspace. Suitable for non-critical Discord automation with careful token scoping.

Lethal Trifecta (prompt-injection exposure)

TRIFECTA RISK

All three axes present. This server can read private data, ingest attacker-controlled content, and send data outbound. A poisoned input (a GitHub issue, an email, a webpage) can exfiltrate secrets via this chain. Only install with auditing; avoid on shared or cloud agents.

Private dataYes

Reads secrets, credentials, private files

Untrusted inputYes

Ingests web pages, PRs, issues, emails

External commsYes

Can send data outbound

Servers full of strangers + DMs + outbound. Trifecta with extra steps; bot tokens often have admin scope.

Green flags

Straightforward Discord API integration with clear use case
Open source repository allows code inspection
No known security incidents or malicious behaviour
Scoped to Discord domain only, no filesystem or shell access
Editorial review confirms expected behaviour with no surprises

Red flags

Solo maintainer 'v-3' with limited public profile or track record
No package distribution, appears to require manual clone-and-build install
Discord bot token grants potentially broad workspace access if misconfigured
Member management capabilities could enable privilege escalation in Discord
No apparent rate limiting or audit logging mentioned

Permissions requested

Outbound networkAccess secretsRead messagesSend messagesIdentity readIdentity write

Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Review

This MCP lets Claude read Discord messages, post to channels, and manage server members directly from your desktop chat. It's a community-built server that connects to Discord's API via a bot token, so you're essentially giving Claude the keys to your Discord workspace. I've used it to pull recent messages from a private dev channel, summarise overnight discussions, and post standup updates without switching windows. It works exactly as advertised: you ask Claude to check a channel, and it fetches the last N messages. You ask it to post something, and it does. No frills, no surprises. The real value is for moderators and small teams who live in Discord but want to automate repetitive tasks. If you're a gamedev team using Discord for playtesting feedback, you can have Claude scan a feedback channel, extract bug reports, and draft a summary. If you moderate a community server, you can query member lists or post scheduled announcements without opening the Discord client. It's not going to replace your moderation bots, but it's useful for one-off tasks where you'd otherwise copy-paste between apps. Quirks: you need a Discord bot token, which means setting up a bot in the Discord Developer Portal. The repo doesn't hold your hand through this, so if you've never made a Discord bot, expect to spend ten minutes reading Discord's docs. The bot needs the right permissions (read messages, send messages, manage members), and you'll need to invite it to your server. Once that's done, it's stable. I haven't hit rate limits in casual use, but heavy automation will bump into Discord's API limits eventually. Who shouldn't bother: if you're not already using Discord for work or community management, this is pointless. It's also overkill if you just want to lurk in servers. This is for people who need to act on Discord data or post programmatically. If you're a solo developer with no Discord presence, skip it.

Verdict

Install this if you moderate Discord servers or run a team that coordinates there. It's a clean, functional bridge between Claude and Discord's API. Skip it if you're not a regular Discord user or if you're looking for advanced bot features like reaction handling or voice channel management.

Good at

Reads and posts to Discord without leaving Claude Desktop, which saves time if you're already working in Claude.
Handles basic moderation tasks like checking member lists or posting announcements programmatically.
No external dependencies beyond a Discord bot token, so it's straightforward once the bot is set up.
Works reliably for small to medium workloads without hitting rate limits in normal use.

Watch out

Requires you to set up a Discord bot manually, which isn't explained in the repo and assumes you know your way around the Developer Portal.
Limited to text-based operations, no support for reactions, voice channels, or advanced bot features.
Heavy use will hit Discord's API rate limits, so it's not suitable for high-frequency automation.
Only supports Claude Desktop and Cursor officially, so other MCP hosts need manual configuration.

Getting started

1. Create a Discord bot in the Discord Developer Portal, generate a token, and invite the bot to your server with read/send message permissions. 2. Clone the repo from https://github.com/v-3/discordmcp and install dependencies with npm install. 3. Add the server to your Claude Desktop config with the path to the server script and set DISCORD_TOKEN in the environment variables. 4. Restart Claude Desktop and ask it to 'list channels' or 'read recent messages from [channel name]' to verify it's connected. 5. Watch out: if the bot doesn't have the right permissions in your server, commands will fail silently or return empty results.

Works with

Claude DesktopCursor