@striderlabs/mcp-discord
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DISCORD_TOKEN | Yes | Your Discord bot token. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_serversA | List all Discord servers (guilds) the bot is a member of |
| get_channelsA | List all channels in a Discord server |
| get_messagesC | Get recent messages from a Discord channel |
| send_messageB | Send a message to a Discord channel |
| get_dmsB | Get recent direct message conversations the bot has had |
| search_messagesA | Search for messages containing specific text in a server's channels |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
The tools are mostly distinct: get_servers, get_channels, get_messages, send_message, get_dms, and search_messages each target a different resource. There is minor overlap between get_messages and search_messages, and get_dms could be confused with channel message retrieval, but descriptions clarify the intended use.
Most tools follow a consistent get_* pattern, with send_message and search_messages being logical action-based exceptions. The use of 'dms' instead of 'direct_messages' is a minor inconsistency but does not hurt readability.
Six tools is a well-scoped set for a Discord MCP server covering server discovery, channel listing, message reading, searching, sending, and DM access. No tool feels redundant or unnecessary.
The core read/send workflows for Discord are covered: list servers, list channels, fetch messages, search messages, send messages, and read DMs. Minor gaps exist such as no direct message sending or message editing/deletion, but the main use cases are supported.