discord-dm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DISCORD_DRY_RUN | No | Set to '1', 'true', or 'yes' to globally force dry-run mode. | |
| DISCORD_API_BASE | No | Override the Discord API base URL (default: https://discord.com/api/v10). | |
| DISCORD_USER_MAP | No | Inline JSON or file path mapping GitHub logins to Discord IDs, e.g. {"octocat":"123456789"}. | |
| DISCORD_BOT_TOKEN | No | Discord bot token required to send messages. Not needed for dry runs. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_discord_dmA | Send a direct message to a Discord user via a bot (REST only, no gateway). Provide either |
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 1 tool
Only one tool exists, so there is no ambiguity. An agent cannot confuse it with another tool.
The single tool name follows a clear verb_noun pattern (send_discord_dm), consistent with common MCP conventions.
A single tool for sending DMs is minimal but arguably appropriate if the server's sole purpose is to send DMs. However, it feels thin and could benefit from at least one more tool (e.g., to verify user availability).
The server only supports sending messages, lacking any way to check user opt-in status, retrieve conversation history, or handle errors like 50007. This leaves significant gaps for an agent.