Compared · discord
16 Discord MCP servers. Which one to use.
Every Discord server we index, with whether its source is still reachable and whether we hold a screening verdict. None currently carry a source-liveness flag.
Scope: 16 servers, mostly mirrored from the MCP registry as of 2026-10-23. Most servers whose authors never published to the registry are absent, so treat this as close to the registry's view rather than a complete census.
| Server | Publisher | Source | Screened | Quality | Install |
|---|---|---|---|---|---|
| GuildControl MCP | app.lasers.guildcontrol | no flag | REVIEW | 100 | npm guildctl |
| Discord MCP | io.github.cappyeo | no flag | REVIEW | 95 | npm @discord-mcp/cli |
| Discord RPC MCP | io.github.ver-1000000 | no flag | REVIEW | 95 | not published |
| Discord | io.github.willuhmjs | no flag | REVIEW | 95 | npm @willuhmjs/discord-mcp |
| Discord Webhook Shape | io.github.sadri-dridi | no flag | REVIEW | 89 | remote endpoint |
| Discord MCP | io.github.hypark5540 | no flag | REVIEW | 85 | npm @hypark5540/discord-mcp |
| io.github.mrfentmen/discord-mcp | io.github.mrfentmen | no flag | REVIEW | 85 | npm @mrfentmen/discord-mcp |
| Discord | io.github.pipeworx-io | no flag | REVIEW | 85 | remote endpoint |
| Discord snowflake worker bits, id discarded | io.github.sadri-dridi | no flag | REVIEW | 85 | remote endpoint |
| io.github.PaSympa/discord-mcp | io.github.PaSympa | no flag | REVIEW | 84 | npm @pasympa/discord-mcp |
| Discord snowflake id shape, value discarded | io.github.sadri-dridi | no flag | REVIEW | 84 | remote endpoint |
| Discord | io.github.mcp-dir | no flag | REVIEW | 83 | remote endpoint |
| io.github.jaimenbell/discord-mcp | io.github.jaimenbell | no flag | REVIEW | 77 | pypi jaimenbell-discord-mcp |
| io.github.Oratorian/discord-node-mcp | io.github.Oratorian | no flag | REVIEW | 67 | npm @mahesvara/discord-mcpserver |
| ai.smithery/Danushkumar-V-mcp-discord | ai.smithery | no flag | REVIEW | 60 | remote endpoint |
| TDA Discord Reader | io.github.targeteddesignagency-blip | no flag | not screened | 56 | not published |
“Repo unreachable” means the source returned a not-found from two vantage points, which can also happen when a repository is made private or moved - see source liveness. “Screened” is the advisory verdict on the listing text, never a safety clearance; the methodology spells out what each dimension does and does not test.