Discord MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REQUEST_DELAY_MS | No | Delay between REST calls in ms. Lower = faster, higher = safer. | 5000 |
| DISCORD_USER_TOKEN | Yes | Your Discord user 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_meA | Get information about the connected Discord account |
| list_guildsA | List all Discord servers the account is in |
| get_guild_infoB | Get detailed information about a Discord server |
| list_channelsA | List all channels in a Discord server |
| get_channel_infoA | Get information about a specific channel |
| get_messagesB | Retrieve recent messages from a channel |
| send_messageC | Send a message to a channel |
| send_embedA | Send a rich embed message to a channel |
| edit_messageA | Edit one of your own messages |
| delete_messageB | Delete a message |
| pin_messageB | Pin or unpin a message |
| add_reactionA | Add an emoji reaction to a message |
| create_threadA | Create a thread from a message or a standalone thread in a channel |
| list_membersB | List members in a server |
| get_user_infoB | Get a user's profile in a server |
| search_messagesA | Search for messages containing a keyword in a channel (scans up to 500 recent messages) |
| get_pinned_messagesB | Get all pinned messages in a channel |
| get_dm_channelsA | List open DM conversations |
| send_dmA | Send a direct message to a user by their ID |
| get_mentionsA | Find recent messages that mention you (scans up to 20 channels across all servers) |
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 20 tools
Each tool targets a distinct resource and action: message retrieval (recent, pinned, search, mentions), sending (message, embed, DM), and management (edit, delete, pin, react), plus guild/channel/member info. No two tools overlap; even send_message and send_embed are clearly separated by format.
All tools follow a consistent verb_noun snake_case pattern (e.g., get_messages, send_dm, create_thread, list_guilds). Collection retrieval uses list_* while single-item retrieval uses get_*, creating a clear and predictable convention. No mixed casing or irregular verbs.
20 tools is slightly above the typical 3-15 range but justified by the breadth of Discord functionality covered: message actions, server/channel info, DMs, and threads. Each tool has a distinct purpose with no unnecessary redundancy, so the count feels appropriate for a feature-rich Discord MCP server.
The tool surface covers core messaging lifecycle (create, read, update, delete, pin, react), channel/guild/member inspection, and direct messaging. Minor gaps exist (e.g., no message-by-ID fetch, no file upload, no reaction removal), but agents can work around these with search and pin tools. The missing server management features are outside the apparent scope of this read/message-centric server.