Home / MCP registry index / Topics / Discord

Discord MCP servers, with their tools checked

Every server in the official MCP registry that mentions Discord, with a public endpoint, read the way an MCP client reads it and checked for tool poisoning. The list updates as the registry does, and each server is read again every week.

9 listed. We have read the tools of 1 so far; the others want credentials first, could not be reached, or are still waiting for their first read.

These servers act inside an account you own, usually with a token you give them. Prefer the narrowest access the tools need, and check which tools can send, post or delete.

DreamAgent
io.github.nivethaug/dreamagent
24 tools, nothing matched
2026-10-22
Qreate: Discord community management
io.github.qreate-gg/qreate-mcp
needs credentials to list tools
2026-10-21
cc.aiones/x-news-monitor
cc.aiones/x-news-monitor
not read yet
DiscordServers
com.discordservers/search
not read yet
Discord
io.github.mcp-dir/discord-mcp
not read yet
Discord
io.github.pipeworx-io/discord
not read yet
Discord snowflake id shape, value discarded
io.github.sadri-dridi/discord-id-ok
not read yet
Discord Webhook Shape
io.github.sadri-dridi/discord-webhook-shape
not read yet
Discord snowflake worker bits, id discarded
io.github.sadri-dridi/discord-worker
not read yet

Choosing one

Open a server's page to see the tools it advertises, whether it sets instructions for the model, and our latest read. Here, 1 of the servers shown matched none of our tool-poisoning rules on their last read. A clean read means our rules found nothing, not that a server is harmless; still check what access it asks for. To check one that is not listed, paste its URL into the free MCP server check.

Related: GitHub · GitLab · Notion · Slack · Email · Calendar · Google Workspace · Jira and Confluence · all topics